Repository navigation
Releases
Godfather v2.4.0
Godfather 2.4.0 opens web apps on a pod in your browser and sets up member folders.
Changes
godfather connect <pod-id> --forward 8080forwards http://localhost:8080 on your laptop to port 8080 on the pod, for a llama.cpp chat UI, Jupyter or any server bound to127.0.0.1on the pod.--forward 9000:8081uses a different local port. Repeat the option for more ports.- Pod image 2.4.0: member setup. Officers give a pod a public repo URL and a setup script on the Platform dashboard (New pod or Member setup in the pod menu). Each member gets the repo cloned and the script run in their folder on their next connection, and again after a change. Output goes to
~/godfather-setup.log. Off unless set. - Pod image 2.4.1: a member shell with a terminal has job control (Ctrl-Z,
bg,fg). A failed clone says that the repo must be public.
Upgrade steps
- Members run
pip install -U godfather-cli. - Officers recreate pods on
ghcr.io/theaisocietyasu/godfather-base:latestfor member setup and job control.
Godfather v2.3.0
Godfather 2.3.0 lets members open a pod in VS Code.
Changes
godfather vscode [pod-id]sets up the VS Code Remote - SSH extension for a pod. It saves a 12-hour certificate for that pod, writes agodfather-<pod-id>entry to your SSH config, and opens VS Code on your workspace if thecodecommand is installed. Run it again to renew the certificate. The menu has the same step as Set up VS Code.- Pod image 2.3.0: a command that an SSH client sends (VS Code,
scp,sftp) runs as your pod account in your workspace. Before, a member login always opened an interactive shell and ignored the command. - Members can open local port forwards (
ssh -L), which VS Code needs. Remote forwards stay off. The image tests now check this the way Platform signs member certificates.
Upgrade steps
- Members run
pip install -U godfather-cli, thengodfather vscode. - Officers recreate each pod on
ghcr.io/theaisocietyasu/godfather-base:2.3.0. On a 2.2.0 pod, VS Code cannot install its server. - Services that a member starts on
127.0.0.1on a shared pod are reachable by the other members of that pod, as they were before from a shell. Bind them to a Unix socket in your workspace, or protect them with a password or token.
Godfather v2.2.0
Godfather 2.2.0 signs you in through the browser and makes each member's files on a pod private.
Changes
godfather authsigns in through the browser. After the Discord sign-in, the browser hands the login back to the CLI, so you do not paste a token. If that is not possible (no browser on this computer, an older server, or no sign-in in 5 minutes), the CLI asks for the token as before.godfather auth --pastegoes straight to the paste step.godfather sessionslists the upcoming sessions on your pods in local time. When none of your pods is running,godfather connectshows the next session.godfather connect --adminasks for a root shell. Officers get it only on a pod whose owner turned on pod admin.- Pod image 2.2.0: your workspace and home folder are private to you, new files are private (umask 077), other members cannot list
/workspace/users, the image has no sudo, and members cannot open port forwards. Banners show the image version. - Python 3.8 to 3.13 are tested on every change.
Upgrade steps
- Members run
pip install -U godfather-cli. The saved login still works. Rungodfather authonly if the CLI asks. - Files in
/workspace/sharedstay readable. Other files are private. To share a file, copy it to/workspace/sharedand runchmod o+ron it. - Officers recreate each pod on the new image after the announced time.
Needs
- Platform with asusoda/platform#468 for the browser sign-in, sessions, pod admin and the image check. With an older Platform, the CLI uses the paste sign-in and says that the server does not list sessions.
Godfather v2.1.0
Godfather 2.1.0 makes the CLI menus interactive and shows more detail about pods, login and errors.
Changes
godfatherwith no arguments opens an arrow-key menu: Connect to a pod, List pods, Status, Log out (or Log in), Exit. Enter chooses. Ctrl-C quits.- The pod picker uses the arrow keys and shows each pod's name, status, access (public or shared with you) and pod ID. A pod that is not running shows with the reason and cannot be chosen. With only one pod to connect to, the CLI asks for a yes instead.
godfather listshows the full pod ID and the command to connect to it.godfather statusshows the server, org, login state, the saved token, about when the token expires, the number of pods you can use, and whether a newer CLI is on PyPI.- Errors say what to do next: server not reachable, token expired (the CLI offers to log in again), pod not running, pod not shared with you, and no pods.
- A spinner shows during each server call.
- When input is not a terminal, the CLI keeps the numbered prompts. All commands and flags work as before.
- New dependency:
questionary.
Upgrade steps
- Members run
pip install -U godfather-cli. The saved login still works.
Godfather v2.0.1
Godfather 2.0.1 points the CLI at the new AI Society platform server.
Changes
- The default server is now
https://zs6k5wi0boaaax-8000.proxy.runpod.net. The old pod no longer exists. - A login saved against the old server is ignored, and the CLI uses the new default.
Upgrade steps
- Members run
pip install -U godfather-cliand thengodfather auth.
Godfather v2.0.0
Godfather 2.0.0 moves pod management to the AI Society platform. The CLI now signs in and connects through the platform's compute module. The old backend and portal are removed.
Changes
godfather authopens the platform sign-in page for the org (/api/compute/<org>/cli/login), and the member pastes the token it shows. Tokens start withplat_and last 90 days.godfather listandgodfather connectuse/api/compute/<org>/me/pods.- New
--orgflag andGODFATHER_ORGenv var. The default org isais. The server and org from the last login are remembered. - Removed
backend/,frontend/,nginx/,docker-compose.yml,DEPLOYMENT.md, and their CI and image workflows. They remain in the history up to v1.1.0.
Upgrade steps
- Members run
pip install -U godfather-cliand thengodfather auth. Tokens from 1.x no longer work. - Officers move pods to the platform: create them under Compute in the platform web app, then terminate the old ones.
Godfather v1.1.0
Godfather gives ASU students free compute on machines the AI Society at ASU pays for. This is a security and handover release. Upgrading needs a few manual steps; see "Upgrading from 1.0.x to 1.1.0" in DEPLOYMENT.md.
Security
- API requests are authenticated with signed tokens issued by the portal. The backend no longer trusts a Discord user ID sent in a header, which let anyone act as an admin.
- The shared organization SSH key is no longer handed out. The CLI makes its own key and gets a 12-hour certificate valid for one pod. Members are forced into their restricted account; admins get root.
- The pod image no longer writes login scripts to predictable paths in /tmp as root.
Fixes
- CPU pods can be created.
- The web file manager works with paramiko 4 and later.
- The backend image includes ssh-keygen.
- Backend CI runs lint and tests; CLI CI runs tests.
Upgrade steps
- Add GODFATHER_TOKEN_SECRET to .env. ADMIN_ROLE_ID is now required.
- Publish the new godfather-base image, then recreate existing pods.
- Members run
pip install -U godfather-cli(1.1.0) and log in again from /cli-auth.
Docs
- README explains how access works and which file to edit for common changes. DEPLOYMENT.md covers deploys, upgrades, releases and CI secrets.
- Releases are automatic: bump the CLI version, add docs/releases/v.md, and merge to main.
godfather-cli security patch
Full Changelog: https://github.com/theaisocietyasu/godfather/commits/cli-v1.0.11