Skip to content

chore: Railway deployment — connect TryLapse repo and verify demo dashboard #27

Description

@0sparsh2

Context

Dockerfile, docker-entrypoint.sh, and docker-compose.yml are merged on main. The image seeds enterprise + argyle demo artifacts on first boot.

Railway free-tier deploys to us-west2 are unavailable during peak hours (8 AM–8 PM PT). Try off-peak.

Steps

  1. railway login (interactive terminal required)
  2. cd /path/to/TryLapse && railway init → empty project, name it "TryLapse"
  3. Set env vars in Railway dashboard: DEEPSEEK_API_KEY, REHEARSE_EMAIL, REHEARSE_PASSWORD
  4. Railway detects Dockerfile automatically → deploy
  5. Verify /api/health returns 200 on the Railway URL
  6. Open the *.up.railway.app URL → confirm enterprise + argyle runs visible in dashboard
  7. Update DESIGN_PARTNER_OUTREACH.md with the public URL for async partner links

Notes

  • Free tier has no persistent disk — demo artifacts are baked into the image via docker-entrypoint.sh
  • Screenshots will show camera placeholder (not in git — too large)
  • rehearse run not available on deployed image (no Playwright)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/docsSpecs and markdown

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions