User Tools

Site Tools


computing:ente

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
computing:ente [2026/09/21 02:55] oemb1905computing:ente [2026/09/21 03:13] (current) oemb1905
Line 34: Line 34:
   * legacy.gnulinux.pics   * legacy.gnulinux.pics
  
-## 1. Base system  
 Setup base system,  Setup base system, 
  
Line 48: Line 47:
 </code> </code>
  
-## 2. Go, Rust, Node+Now, Go, Rust, and Node setup: 
 <code> <code>
 sudo apt install -y golang-go rustup nodejs npm sudo apt install -y golang-go rustup nodejs npm
Line 58: Line 58:
 </code> </code>
  
-### 3. PostgreSQL +Setup PostgreSQL and create the db with ''sudo -u postgres psql'' and something like:
- +
-Create the db with ''sudo -u postgres psql'' and something like:+
      
 <code> <code>
Line 69: Line 67:
 </code> </code>
  
-Next, lock access:+Next, lock access to db:
  
 <code> <code>
Line 78: Line 76:
 </code> </code>
  
-## 4Museum binary + yaml config +Edit museum.yaml and configure it, build its web apps, start it, and create unit:
-Run the go setup bits and migrate the example yaml config to production so we can edit params:+
  
 <code> <code>
Line 89: Line 86:
 </code> </code>
  
-Edit ''/root/ente/server/museum.yaml'' (keys from the generatorDB, then S3 after Garage). Do not regenerate keys on a live database. Create systemd unit.+Edit ''/root/ente/server/museum.yaml'' using keys from second to last step above. Nowcreate systemd unit.
  
 <code> <code>
Line 112: Line 109:
 </code> </code>
  
-## 5. Web app building and migrating content from repo+Build the Web apps and migrating content from repo
  
 <code> <code>
Line 139: Line 136:
 </code> </code>
  
-## 6. Caddy reverse proxy, acme certs, load balancing, vhosts, etc. +Setup Caddy reverse proxy / load balancer, acme certs, and vhosts with ''nano /etc/caddy/Caddyfile'' and enter the following:
- +
-  nano ''/etc/caddy/Caddyfile''+
- +
-Then, setup caddy's reverse proxies and server blocks as follows:+
  
 <code> <code>
Line 231: Line 224:
 </code> </code>
  
-End point works now, go to url in browser+End point works now, go to url in browser and create first user then use the id# to lock it as admin.
  
-## 7. First user +  - Open https://gnulinux.pics and sign up. 
-1. Open https://gnulinux.pics and sign up. +  OTP: ''journalctl -u ente-museum -n 200 --no-pager'' 
-2. OTP: ''journalctl -u ente-museum -n 200 --no-pager'' +  User id: 34982349839489320843
-3. User id: 34982349839489320843+
  
 You need to locate the id# by searching logs for your email in close proximity as per above. Or, alternately, make a one-liner: You need to locate the id# by searching logs for your email in close proximity as per above. Or, alternately, make a one-liner:
Line 273: Line 265:
 </code> </code>
  
-Create config .toml file and start garage service:+Create config .toml file and start garage service:
  
 <code> <code>
Line 345: Line 337:
   sudo systemctl restart ente-museum   sudo systemctl restart ente-museum
  
-### Draft Upgrade Garage Steps +Draft Upgrade Garage Steps 
  
 <code> <code>
Line 368: Line 360:
 </code> </code>
  
-Do not layout/bucket/key on upgrade - it will hose current bucket. +Do not layout/bucket/key on upgrade - it will hose current bucket. Example museum.yaml example config layout for base setup
- +
-## 9. museum.yaml example config layout for base setup+
  
 <code> <code>
Line 415: Line 405:
 </code> </code>
  
-## 10. Draft update sequence+Draft update sequence
  
 <code> <code>
computing/ente.1789959340.txt.gz · Last modified: by oemb1905