Skip to content

feat: Railway API deployment and GitHub Pages dashboard - #15

Merged
castroquiles merged 1 commit into
mainfrom
feat/railway-pages-deployment
Jun 6, 2026
Merged

feat: Railway API deployment and GitHub Pages dashboard#15
castroquiles merged 1 commit into
mainfrom
feat/railway-pages-deployment

Conversation

@castroquiles

Copy link
Copy Markdown
Owner

Summary

Configures public deployment for the GLAPAGOS platform.

Changes

  • railway.toml — nixpacks build config, uvicorn start with dynamic PORT
  • Procfile — Railway process definition
  • requirements.txt — pinned production dependencies
  • src/dashboard/index.html — runtime API_BASE detection via meta tag,
    falls back to same origin in production or localhost in dev
  • .github/workflows/pages.yml — deploys src/dashboard to GitHub Pages
    on every push to main

After merge

  1. Enable GitHub Pages in repo Settings > Pages > Source: GitHub Actions
  2. Connect repo to Railway and deploy
  3. Set GLAPAGOS_API_BASE environment variable in Railway if needed

Result

- railway.toml: nixpacks build, uvicorn start command with dynamic PORT
- Procfile: Railway process definition
- requirements.txt: pinned production dependencies
- src/dashboard/index.html: runtime API_BASE detection via meta tag,
  falls back to same origin in production or localhost in dev
- .github/workflows/pages.yml: deploys src/dashboard to GitHub Pages
  on every push to main
@castroquiles
castroquiles merged commit 3e3b327 into main Jun 6, 2026
3 of 7 checks passed
@castroquiles
castroquiles deleted the feat/railway-pages-deployment branch June 6, 2026 23:18
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