| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Most Docker web containers (nginx, etc.) listen on port 80 internally.
The previous mapping assumed the container listened on the allocated port.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Adds cgit as a web frontend for browsing git repositories. Visiting the
base domain now shows a cgit repo index with trees, commits, diffs, and
blame views. Public repos (marked with git-daemon-export-ok) are browsable
and cloneable over HTTPS.
- Install cgit during host init
- Configure cgit with dark theme and base domain integration
- Add cgit CGI handler to base domain Caddyfile
- Update README to emphasize git-centric workflow with cgit frontend
|
| |
|
|
|
|
|
|
|
| |
Drop git-module type — the post-receive hook now checks for a Dockerfile
before building, so repos without one simply skip deploy on push. This
covers Go modules and libraries that only need vanity imports.
Add --public flag to ship init for per-repo HTTPS clone visibility.
Show visibility column in ship list.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
New deployment model where projects start with a git remote on the VPS.
Pushing to the remote triggers automatic docker build and deploy via
post-receive hooks. The base domain serves Go vanity imports and git
HTTPS cloning via Caddy + fcgiwrap.
- Add `ship init <name>` command to create bare repos and .ship/ config
- Add `ship deploy <name>` command for manual rebuilds
- Extend `ship host init --base-domain` to set up Docker, git user,
fcgiwrap, sudoers, and vanity import infrastructure
- Add git-app and git-static types alongside existing app and static
- Update remove, status, logs, restart, list, and config-update to
handle new types
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Adds --memory and --cpu flags to set systemd resource limits:
ship --binary ./app --memory 512M --cpu 100%
Also adds config update mode - use --name without --binary to
update an existing app's config without redeploying the binary:
ship --name myapp --cpu 50%
ship --name myapp --memory 256M --env DEBUG=true
Limits are stored in state and preserved on redeploy.
|
| | |
|
| |
|
