1. ssh $user@server-ip-address
2. Install these things to build from source (I added these individually as I saw errors, but compiled them together here in the beginning)
   1. doas pkg_add gmake node go
   2. doas pkg_add git
   3. doas pkg_add bash
   4. doas npm install -g pnpm
3. Build from source
   1. git clone https://github.com/filebrowser/filebrowser
   2. cd filebrowser
   3. gmake build
   4. See error:

Error: Your current platform "openbsd" and architecture "x64" combination is not yet supported by the native Rollup build. Please use the WASM build "@rollup/wasm-node" instead.

...

Node.js v20.18.2
 ELIFECYCLE  Command failed with exit code 1.
gmake: *** [Makefile:13: build-frontend] Error 1

4. Address the error by installing the WASM build
   1. cd ~/filebrowser/frontend
   2. pnpm add -D @rollup/wasm-node
5. Add override to package.json (I did this via SFTP because I didn't want to do edits via command line anymore)
   1. SFTP into server with WinSCP
   2. Right-click and duplicate /filebrowser/frontend/package.json to save a backup copy
   3. Right-click and edit package.json
   4. Add "pnpm" override between "engines" section and "scripts" section:

  "engines": {
    ...
  },
  "pnpm": {
    "overrides": {
    "rollup": "npm:@rollup/wasm-node"
    }
  },
  "scripts": {
    ...
  },

6. Add override to pnpm-lock.yaml
   1. Right-click and duplicate /filebrowser/frontend/pnpm-lock.yaml to save a backup copy
   2. cd ~/filebrowser/frontend
   3. pnpm install --no-frozen-lockfile
7. Try to build again
   1. cd ~/filebrowser
   2. gmake build
   3. See new error:

✓ 1140 modules transformed.

<--- Last few GCs --->

[44534:0x4326d372000]    42338 ms: Mark-Compact 494.1 (515.4) -> 490.2 (515.7) MB, 1121.35 / 0.00 ms  (average mu = 0.095, current mu = 0.037) allocation failure; scavenge might not succeed
[44534:0x4326d372000]    43487 ms: Mark-Compact 494.1 (515.7) -> 490.2 (515.7) MB, 1131.97 / 0.00 ms  (average mu = 0.059, current mu = 0.014) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----

...

Abort trap (core dumped)
 ELIFECYCLE  Command failed with exit code 134.
gmake: *** [Makefile:13: build-frontend] Error 134

8. Spend way too long trying to address the memory error in various ways but ultimately accept that 1 GB memory is not enough to build this thing

Create new server with 4 GB memory

I wanted to temporarily upgrade my server's memory and then downgrade it later, but that wasn't a possibility. So spinning up a second $20/mo server it is. I'll destroy it after I'm done. If we throw enough money at the problem, it'll get solved, right? (The 4 GB server costed $2.71 at the time of destruction, since I ran it only for a couple days.)

1. Log into Vultr.com
2. Go to Products > Compute > Deploy +
3. Select Shared CPU > Select the same city as other server
4. Select 4 GB memory for $20/mo
5. Disable Automatic Backups and confirm that yes, I understand the risks and really don't want it
6. Select Configure Software
7. Select OpenBSD 7.6 x64 (the blowfish again)
8. Under SSH Keys, select mykey
9. Leave server hostname and server label blank
10. Select Deploy

SSH into root & run Tech Independence script again

I just wanted to use the script to set up SSH access & disable root account. One day I'll learn how to do this on my own.

1. ssh root@4gb-server-ip
2. yes
3. ftp https://sive.rs/ti.sh
4. sh ti.sh
5. Enter my domain name
6. Enter a username
7. y
8. Enter a full name
9. Enter a password
10. Retype password
11. Open a new PowerShell window
    1. ssh $user@4gb-server-ip
    2. And then again per the instructions, ssh $user@4gb-server-ip
12. Close out of both PowerShell windows

Mirror files from original server to new server

I ended up doing this because I set up the 4gb-server the next night, and one of the node modules updated 14 hours before my second install. That module update caused new errors that I didn't want to spend time troubleshooting. Since I knew my first install was building just fine, I decided to clone it over.

1. Open FreeFileSync (because I didn't know how to use Rsync yet)
2. On the left, add 1gb-server's SFTP login info
3. On the right, add 4gb-server's SFTP login info
4. Select the green gear icon
5. Go to Comparison tab and Performance improvements on the right
   • Update Parallel file operations to 4 for each server (requires donation edition of app; I didn't know about this setting when I started my sync and things were painfully slow since there were so many tiny files — I ran the sync overnight)
6. Go to Synchronization tab
   • Under Delete and overwrite:, select Permanent (because there is no Recycle Bin on the server)
7. Use FreeFileSync to mirror /filebrowser directory from original server to new server
   1. Under Drag & drop for both sides, ensure the path is /home/$user/filebrowser
   2. Select Synchronize
   3. Wait for it to complete

Build File Browser on new server (and succeed)

1. ssh $user@4gb-server-ip
2. Install these things to build from source (same as before)
   • doas pkg_add gmake node go
   • doas pkg_add git
   • doas pkg_add bash
   • doas npm install -g pnpm
3. cd filebrowser
4. gmake build
5. See new error:

failed to load config from /home/$user/filebrowser/frontend/vite.config.ts
error during build:
Error: The service was stopped: spawn /home/$user/filebrowser/frontend/node_modules/.pnpm/@esbuild+openbsd-x64@0.24.2/node_modules/@esbuild/openbsd-x64/bin/esbuild EACCES
    at /home/$user/filebrowser/frontend/node_modules/.pnpm/esbuild@0.24.2/node_modules/esbuild/lib/main.js:968:34
    at responseCallbacks.<computed> (/home/$user/filebrowser/frontend/node_modules/.pnpm/esbuild@0.24.2/node_modules/esbuild/lib/main.js:622:9)
    at ChildProcess.afterClose (/home/$user/filebrowser/frontend/node_modules/.pnpm/esbuild@0.24.2/node_modules/esbuild/lib/main.js:613:28)
    at ChildProcess.emit (node:events:518:28)
    at ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
 ELIFECYCLE  Command failed with exit code 1.
gmake: *** [Makefile:13: build-frontend] Error 1

6. Apparently a permission issue. Grant it permission to execute:
   • chmod +x /home/$user/filebrowser/frontend/node_modules/.pnpm/@esbuild+openbsd-x64@0.24.2/node_modules/@esbuild/openbsd-x64/bin/esbuild
7. gmake build
8. See new error:

✓ 1140 modules transformed.
rendering chunks (1)...Segmentation fault
 ELIFECYCLE  Command failed with exit code 139.
gmake: *** [Makefile:13: build-frontend] Error 139

9. Okay, so error 139 is another memory issue. Check my user's memory limits:
   1. ulimit -a
   2. See that data(kbytes) is set to 1572864 KB (1.5 GB)
   3. Increase to 3 GB
      • ulimit -d 3145728
10. gmake build
11. IT'S BUILT! I never thought I'd get here

Temporarily run File Browser

1. ~/filebrowser/filebrowser -r ~/files
2. It's running on local host: Listening on 127.0.0.1:8080
3. Leave this window open (closing it will stop running File Browser)
4. Open a new PowerShell window and SSH into 4gb-server
   • Confirm that it's running
     1. netstat -an | grep 8080
     2. Should see:

tcp   0   0   127.0.0.1.8080   *.*   LISTEN

5. Since it's running on localhost (127.0.0.1:8080) and I want to access it from my local computer
   1. Open a new PowerShell window
   2. ssh -L 8080:127.0.0.1:8080 $user@4gb-server-ip
   3. Open my Firefox browser
   4. Go to http://127.0.0.1:8080
   5. IT WORKS! happy dance
6. Close all the windows

Now I just need to get this back to my 1 GB server.

Set up Rsync & copy the binary back to original server

1. PowerShell window 1: Generate a new SSH key for 4gb-server
   1. ssh-keygen -t ed25519 -C "your-email@example.com"
   2. enter
   3. enter
   4. Confirm key was generated
      • ls -la ~/.ssh/id_*
   5. View SSH key
      • cat ~/.ssh/id_ed25519.pub
2. New PowerShell window 2: Give 4gb-server access to 1gb-server
   1. ssh $user@1gb-server-ip
   2. doas mg ~/.ssh/authorized_keys
   3. Copy the public key from PowerShell window 1
      • Starts with ssh-ed25519
   4. Paste it it into the authorized_keys file and save the file
3. PowerShell window 1: Log into 1gb-server from 4gb-server
   1. ssh $user@1gb-server-ip
   2. yes
   3. We're in!
   4. exit
   5. Copy the binary from 4gb-server to 1gb-server
      • rsync -avz ~/filebrowser/filebrowser $user@1gb-server-ip:/home/$user/filebrowser/
4. PowerShell window 2: Remove 4gb-server's access
   1. doas mg ~/.ssh/authorized_keys
   2. Delete the key we added earlier and save the file
5. Close window 1; done with the 4gb-server now and no longer need to log into it again

1. Destroy 4gb-server on Vultr.com
2. Remove all those things I installed to build from source on 1gb-server
   1. doas pkg_delete gmake node go git bash
   2. See note:

--- -git-2.46.1 -------------------
You should also run /usr/sbin/userdel _gitdaemon
You should also run /usr/sbin/groupdel _gitdaemon
--- -node-20.18.2v0 -------------------
You may wish to remove /usr/local/lib/node_modules/npm/man from man.conf
Error deleting directory /usr/local/lib/node_modules: Directory not empty

3. Remove lingering files
   1. doas /usr/sbin/userdel _gitdaemon
   2. doas /usr/sbin/groupdel _gitdaemon
   3. doas rm -rf /usr/local/lib/node_modules
   4. rm -rf ~/.npm
   5. rm -rf ~/.cache/pnpm
   6. doas rm -rf ~/go
   7. rm -rf ~/.local/share/pnpm
   8. rm -rf ~/.local/state/pnpm
   9. rm -rf ~/.cache/pnpm
   10. rm -rf ~/.cache/go-build
   11. rm -rf ~/filebrowser