Skip to content

docs: prepare full Railway deployment template - #478

Draft
maxffarrell wants to merge 2 commits into
mainfrom
dot/railway-full-deploy
Draft

maxffarrell wants to merge 2 commits into
mainfrom
dot/railway-full-deploy

Conversation

@maxffarrell

Copy link
Copy Markdown
Owner

Scope

Prepare the exact app + PostgreSQL template specification needed to restore the Railway button. This is documentation/preparation, not a working deploy button yet.

  • persistent PostgreSQL 18 service, private database reference, generated credentials
  • generated app domain and origin, Docker migration/start command, health checks
  • fresh-install, auth, migration and persistence acceptance checks
  • no placeholder template IDs or misleading README badge

Blocker

Creating the actual Railway template needs authenticated Railway account access. No accessible session was available. No hosted template or live deployment was created, and no cloud charges were incurred.

Validation

Compared specification with current Railway primary documentation and repository Dockerfile, migration/server scripts and environment declarations. Standalone Markdown Prettier passed. Application check/lint/test/build and live Railway acceptance checks were not run; this change only adds documentation.

This branch has not been deployed

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant