officerdev/platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

scripts/setup is the initial install, nothing else

Browse Source 
Two of the eight did not belong. cleanup-desktop.sh is the teardown — the inverse of an install, not part
of one. provision-user-dirs.ts runs per account at invite time, on a machine that is already set up.
Both are back at the top level, with their `../` derivations and usage strings put back.

What is left is what a fresh machine runs once: the two installers (setup.sh, setup_mac_light.sh), the
two things setup.sh calls (setup-dockers.sh, setup-desktop.sh), and the two files they deploy —
starship.toml, copied to ~/.config, and officer-set-display.sh, which setup-desktop.sh installs to
~/.local/bin as a login-time mode setter. The last one is not a setup script and does not read like one;
it is here because it is install payload, same as the toml, and setup-desktop.sh loads it by
`$(dirname $0)`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
pastilhas
2026-08-12 04:05:06 +00:00
co-authored by Claude Opus 5
parent 9c353f5f0d
commit f5f509a99d
4 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/setup/cleanup-desktop.sh → scripts/cleanup-desktop.sh
+4 -4
View File
@@ -26,7 +26,7 @@ set -euo pipefail
# their profile in it. Opt in rather than surprise someone.
#
# Usage:
# bash scripts/setup/cleanup-desktop.sh [--purge-brave]
# bash scripts/cleanup-desktop.sh [--purge-brave]
#
# Reboot afterwards: the GDM and GRUB changes are both boot-time.
@@ -131,9 +131,9 @@ fi
# --- Step 7: .env ---
echo "[7/7] Cleaning .env..."
# ../.. — this lives in scripts/setup/. A wrong level here is quiet in the other direction: the sed
# below simply finds no file, reports "No .env" and leaves the real VNC_PASSWORD in place.
ENV_FILE="$(cd "$(dirname "$0")/../.." && pwd)/.env"
# A wrong level here is quiet: the sed below simply finds no file, reports "No .env" and leaves the real
# VNC_PASSWORD in place. Keep this in step with wherever this script lives.
ENV_FILE="$(cd "$(dirname "$0")/.." && pwd)/.env"
if [ -f "$ENV_FILE" ]; then
sed -i '/^VNC_PASSWORD=/d; /^VNC_PORT=/d' "$ENV_FILE"
echo " Removed VNC entries."
scripts/setup/provision-user-dirs.ts → scripts/provision-user-dirs.ts
+4 -4
View File
@@ -1,7 +1,7 @@
// Create the per-user root under DATA_PATH for the given accounts.
//
// bun scripts/setup/provision-user-dirs.ts a@b.com c@d.com
// DRY_RUN=1 bun scripts/setup/provision-user-dirs.ts a@b.com
// bun scripts/provision-user-dirs.ts a@b.com c@d.com
// DRY_RUN=1 bun scripts/provision-user-dirs.ts a@b.com
//
// Takes emails as arguments rather than reading the user table: the directory layout does not depend
// on the database, and keeping the DB out means this runs with nothing else up. At invite time the
@@ -19,13 +19,13 @@ import { join } from 'node:path';
// The list and DATA_PATH itself come from the platform rather than being restated here. The owner's
// create-account handler provisions the same skeleton, and a script that drifted from it would produce
// accounts that differ by how they were made. Importing data-path.ts pulls in no database and no server.
import { DATA_PATH, USER_DIRS } from '../../src/servers/data-path';
import { DATA_PATH, USER_DIRS } from '../src/servers/data-path';
const DRY_RUN = process.env.DRY_RUN === '1';
const emails = process.argv.slice(2).filter(Boolean);
if (!emails.length) {
console.error('Usage: bun scripts/setup/provision-user-dirs.ts <email> [email...]');
console.error('Usage: bun scripts/provision-user-dirs.ts <email> [email...]');
process.exit(2);
}