summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Add TODO.md with known limitationsClawd17 hours1-0/+41
| | | | | - Docker container port hardcoded to 80 - ship host init doesn't create local state.json
* Fix Docker port mapping: map host port to container port 80Clawd17 hours1-1/+1
| | | | | Most Docker web containers (nginx, etc.) listen on port 80 internally. The previous mapping assumed the container listened on the allocated port.
* Add --domain flag to v2 CLI flagsClawd17 hours2-0/+1
|
* Add --domain flag support to v2 deployClawd17 hours2-2/+9
| | | | | Allows specifying a custom domain instead of using the auto-generated subdomain pattern. Usage: ship . --domain bdw.to
* Add source link to website footerClawd21 hours1-0/+1
|
* Remove .claude from tracking, update .gitignoreClawd21 hours2-18/+3
|
* Add website/ directory with landing pageClawd21 hours2-0/+220
|
* feat: auto-generate SSH key and guide auth setup in host initClawd36 hours1-2/+82
| | | | | | - ensureSSHKey() generates ed25519 key if none exists - If SSH auth fails, returns JSON with pubkey and setup instructions - Provides ssh-copy-id command for easy key deployment
* fix: set ownership before rsync for Docker deployClawd39 hours1-0/+7
|
* fix: split sudo commands to fix ownership for rsync uploadClawd39 hours1-2/+8
|
* fix: Caddy install permission issue with gpg dearmorClawd39 hours1-3/+4
|
* fix: make ErrorResponse implement error interface for v1 compatClawd39 hours1-0/+3
|
* fix: resolve build errors with v1 codeClawd39 hours2-13/+10
| | | | | | | - Rename validateName to validateNameV2 to avoid conflict - Fix host status to print JSON directly (remove unused resp) Builds successfully now
* docs: update progress with all commit hashesClawd39 hours1-0/+4
|
* feat(v2): wire up v2 as default interfaceClawd39 hours2-4/+20
| | | | | | | | - main.go: v2 JSON interface is now default - Set SHIP_V1=1 to use legacy human-formatted output - initV2() called before rootV2Cmd.Execute() v2 rebuild complete - ready for testing
* feat(v2): implement list, status, logs, remove commandsClawd39 hours3-48/+351
| | | | | | | | | | | - commands_v2.go: all subcommand implementations - list: enumerates deploys from /etc/ship/ports and /var/www - status: shows deploy details (type, port, running, TTL) - logs: fetches journalctl logs (or Caddy logs for static) - remove: full cleanup of all artifacts (service, caddy, files, docker) - All commands output JSON with proper error codes All core v2 commands now implemented
* feat(v2): implement ship host init with JSON outputClawd39 hours4-27/+380
| | | | | | | | | | | | - host_v2.go: full host initialization with JSON responses - Installs Caddy, Docker on Ubuntu/Debian - Creates /etc/ship/{env,ports,ttl} directories - Installs TTL cleanup timer (hourly systemd timer) - Cleanup script removes expired deploys completely - Preserves git deploy setup functionality (optional) - Added ErrInvalidArgs error code Critical 'host init' functionality preserved for v2
* feat(v2): implement deploy flowsClawd39 hours3-52/+376
| | | | | | | | | | | | - deploy_impl_v2.go: full implementations for static, docker, binary deploys - Static: rsync + Caddyfile generation + reload - Docker: rsync + build + systemd unit + env file + Caddyfile - Binary: scp + systemd unit + service user + env file + Caddyfile - Port allocation: server-side in /etc/ship/ports/ - TTL: server-side in /etc/ship/ttl/ - Health checks: HTTP GET with 30s retry loop All deploy types now functional (pending Go compilation test)
* feat(v2): add CLI structure and deploy orchestrationClawd39 hours3-10/+419
| | | | | | | | | | | - cmd/ship/root_v2.go: new CLI with ship [PATH] as primary command - cmd/ship/deploy_v2.go: deploy orchestration with context struct - Placeholder implementations for static/docker/binary deploys - Placeholder subcommands (list, status, logs, remove, host) - Support for --name, --health, --ttl, --env flags - SHIP_PRETTY env var support Next: implement actual deploy flows
* feat(v2): add output and detect packagesClawd39 hours3-0/+358
| | | | | | | | - internal/output: JSON response types, error codes, exit codes, pretty output - internal/detect: auto-detection of project type (static/docker/binary) - PROGRESS.md: track rebuild progress Foundation for agent-first JSON interface per SPEC.md
* docs: add comprehensive technical specificationClawd40 hours1-0/+499
|
* docs: rewrite as agent-first tool, humans are afterthoughtClawd40 hours1-172/+147
|
* docs: rename to SHIP_V2.md, JSON output is default not a flagClawd40 hours2-34/+46
|
* docs: add agent mode design documentClawd40 hours1-0/+271
|
* fix: use project directory for static site .ship/ folderClawd40 hours1-4/+7
| | | | | | | | | | Previously, deployStatic() checked for .ship/Caddyfile in the current working directory instead of the project directory (opts.Dir). This caused stale Caddyfiles from previous deployments to be reused when deploying multiple static sites from the same working directory. Now .ship/ is created inside the project directory, so each site maintains its own configuration.
* gitignorebndw41 hours1-0/+1
|
* random design filesbndw41 hours2-0/+586
|
* Add backwards compatibility for existing binary deploymentsbndw3 days1-7/+11
| | | | | | Check if .ship files exist before reading them. If they don't exist, generate them even on updates. This provides automatic migration for deployments created before the .ship/ directory change.
* Store deployment configs locally for binary deploymentsbndw3 days2-36/+94
| | | | | | | | | | | | | | For binary and static deployments, .ship/service and .ship/Caddyfile are now written to the local working directory (similar to git deployments) instead of being regenerated on every deployment. - On initial deployment, create local .ship/ directory with generated configs - On subsequent deployments, upload from local .ship/ files - Caddyfile is never regenerated, preserving custom routes - Systemd service is regenerated only when --memory, --cpu, or --args change This prevents custom Caddyfile routes from being overwritten and makes binary deployment workflow consistent with git deployment workflow.
* Add cgit web interface for browsing reposbndw3 days4-168/+151
| | | | | | | | | | | | 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
* Rewrite README and add SECURITY.mdbndw7 days2-143/+262
| | | | | | Document both deployment modes (git push and direct), all commands, architecture, VPS file layout, and vanity imports. Add SECURITY.md covering threat model, mitigations, and known gaps.
* Remove --module flag, add --public, make hooks smarterbndw7 days3-55/+96
| | | | | | | | | 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.
* Harden security: name validation, scoped sudoers, safe.directorybndw7 days12-7/+84
| | | | | | | | | | - Add ValidateName() enforcing ^[a-z][a-z0-9-]{0,62}$ on all entry points - Tighten sudoers to restrict cp sources/destinations and chown targets - Scope git safe.directory to www-data user only (preserves CVE-2022-24765) - Add www-data to git group and caddy to www-data group for fcgiwrap - Fix vanity import template to use orig_uri placeholder - Restart (not reload) services after group changes - Add name validation to env subcommands and deploy_cmd
* Fix Docker apt source write permission in host initbndw9 days1-1/+1
| | | | | The pipe caused only echo to run as sudo while tee had no privileges. Wrap in sh -c so the redirect runs as root.
* Add git-centric deployment with Docker builds and vanity importsbndw9 days12-35/+750
| | | | | | | | | | | | | | | 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
* Move deploy implementation to deploy.gobndw2026-01-253-679/+682
| | | | | | | Restructure CLI files to follow idiomatic cobra layout: - main.go: minimal entry point - root.go: command definition, flags, and subcommand wiring - deploy.go: all deploy implementation
* Preserve existing config when updating apps and static sitesbndw2026-01-251-180/+215
| | | | | | | | | | | | | | | Previously, updating an app or static site without specifying all flags would clear existing configuration (e.g., custom domains would be lost if --domain wasn't provided on update). Now all config is merged in runDeploy before calling deploy functions: - Load state once instead of 2-3 times - Check for existing app once to determine create vs update - Build merged DeployOptions with existing config + CLI overrides - Deploy functions receive fully-merged config and just execute This ensures existing configuration is preserved unless explicitly overridden by CLI flags.
* Refactor deploy functions to use DeployOptions structbndw2026-01-251-84/+107
|
* Add examples to help textbndw2026-01-251-1/+18
|
* Add CPU and memory limits for appsbndw2026-01-254-9/+149
| | | | | | | | | | | | 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.
* Add auto-generated subdomain featurebndw2026-01-247-21/+144
| | | | | | | | | | | | | When a base domain is configured on a host (e.g., apps.example.com), deployments automatically get a subdomain ({name}.apps.example.com). Custom --domain can still be provided to route both domains. - Add BaseDomain field to Host state - Add --base-domain flag to host init - Add 'ship host set-domain' command to update base domain - Update deploy flow to auto-generate subdomains - Fix error display (errors were being silently swallowed) - Remove placeholder email from Caddyfile template
* Add ASCII art banner and improve help textbndw2026-01-241-3/+22
| | | | | Show a ship logo in CLI help and explain how ship works - SSH-only deployment with no agents or containers required.
* remove old design specbndw2026-01-241-586/+0
|
* Rename project from deploy to shipbndw2026-01-2425-87/+87
| | | | | | | | | - Rename module to github.com/bdw/ship - Rename cmd/deploy to cmd/ship - Update all import paths - Update config path from ~/.config/deploy to ~/.config/ship - Update VPS env path from /etc/deploy to /etc/ship - Update README, Makefile, and docs
* Update README for new command structurebndw2026-01-241-34/+33
| | | | | | | - Commands now use host subcommand (deploy host init, update, ssh, status) - Remove --host flag from examples (default host set on init) - Update env commands to new subcommand syntax - Simplify configuration section
* Add reboot prompt to host update commandbndw2026-01-241-4/+17
| | | | | Prompts user to reboot when required after apt upgrade completes. Both prompts now default to yes for a more turnkey experience.
* Restructure CLI with Cobrabndw2026-01-2325-1485/+1469
| | | | | | | | | | | | | Replace custom switch-based routing with Cobra for cleaner command hierarchy. Reorganize commands into logical groups: - Root command handles deployment (--binary, --static, --domain, etc.) - App management at top level: list, logs, status, restart, remove - env subcommand group: list, set, unset - host subcommand group: init, status, update, ssh - Standalone: ui (renamed from webui), version Add version command with ldflags support for build info.
* Add VPS management commands: vps, vps-update, vps-sshbndw2026-01-232-0/+244
| | | | | | - vps: Show server health (uptime, load, memory, disk, services) - vps-update: Run apt update && upgrade with streaming output - vps-ssh: Open interactive SSH session to default/specified host
* Make deploy the default action and require --binarybndw2026-01-232-35/+20
| | | | | | | - Remove "deploy" subcommand, deploy is now the default action - Require --binary flag explicitly (no auto-discovery) - Add "rm" as alias for "remove" - Update help text
* Move default host from config file to state.jsonbndw2026-01-237-172/+84
| | | | | | | | | Instead of a separate ~/.config/deploy/config file, the default host is now stored as default_host in state.json. This simplifies the config and keeps all state in one place. The init command now automatically sets the default host if none is configured.
generated by cgit v1.2.3 (git 2.39.1) at 2026-02-17 18:12:29 +0000