hogsend deploy

Usage

hogsend deploy

Triggers a redeploy of both the API and Worker services on Railway using the credentials stored in .hogsend.yaml.

What it does

Loads the Railway token, project ID, environment ID, and service IDs from .hogsend.yaml
Calls the Railway API to redeploy the API service
Calls the Railway API to redeploy the Worker service
Prints the Railway dashboard link so you can track build progress

Both services are redeployed using their latest committed code and current environment variables.

When to use it

Scenario	Use `hogsend deploy`	Use `git push`
Changed env vars via `hogsend init` or `hogsend journeys`	Automatic -- those commands redeploy for you	--
Changed env vars manually on Railway dashboard	Yes	No
Pushed new code to `main`	No -- auto-deploy handles it	Yes
Need to restart services without code changes	Yes	No
Debugging a stuck deployment	Yes	No

The deploy command is most useful when you need to restart services after a manual configuration change, or when you want to force a fresh deployment without pushing code.

Example output

HOGSEND DEPLOY
Deploying ACME Corp

  Redeploying API...      done
  Redeploying Worker...   done

  Deploy triggered
  Track progress: https://railway.com/project/abc-123

Requirements

.hogsend.yaml must exist with valid Railway credentials
The Railway token must have access to the configured project