a month ago
We are evaluating Railway for hosting an existing hospital website. The application stack consists of Angular with TypeScript for the frontend, Java 25 with Spring Boot 4 for the backend, PostgreSQL 18 for the database, and S3-compatible object storage for résumé PDF uploads. The website includes public hospital pages, appointment request booking, careers, and staff, admin, and HR dashboards. We plan to use a custom domain with Cloudflare for DNS and CDN, GitHub for source control, and GitHub Actions for CI/CD. Please confirm the current compatibility and recommended deployment configuration for Java 25, Spring Boot 4, and PostgreSQL 18. Explain how to configure frontend and backend services, environment variables and secrets, private database connectivity, custom domains, HTTPS, persistent and object storage, and automated deployments. Please also clarify the available deployment regions, PostgreSQL backup and point-in-time recovery options, independent backup and restoration procedures, monitoring and alerting capabilities, and the recommended approach for securely validating and malware-scanning uploaded résumé files. Identify any platform limitations, additional services, or configuration changes that would be necessary for a secure, reliable production deployment. We have not deployed the application on Railway yet, so please distinguish documented platform capabilities from features that require implementation or verification.
1 Reply
a month ago
Any application that builds into a container runs on our platform, so an Angular frontend and a Java/Spring Boot backend deploy as separate services; verify Java 25 and Spring Boot 4 specifics in a test deployment. PostgreSQL runs as a service in your own project from our Postgres image, and you choose the version through the image tag you pin (our HA clusters support major versions 14 through 18). It is unmanaged: configuration, extensions and upgrades are yours.
GitHub integration deploys automatically on push, with rollbacks, multiple environments and PR environments; GitHub Actions works through the CLI and API. Variables can be sealed so values are never readable in the UI or API. Custom domains get automatically issued and renewed Let's Encrypt certificates.
Buckets are private-only, so serve résumés through presigned URLs or proxy them through your backend. Validating and malware-scanning uploads is something you implement in your application.
Regions are US West (California), US East (Virginia), EU West (Amsterdam) and Southeast Asia (Singapore) (docs). Logs are stored in US West regardless of region; volume backups and PITR data follow the deploy region.
Volume backups (manual or daily/weekly/monthly schedules) and restores require the Pro plan, and you turn them on yourself. Point-in-time recovery is enabled per Postgres service and restores to a timestamp into a new service. HA with automatic failover and PgBouncer pooling are available.
Logs and metrics are in the dashboard. Compliance reports, including HIPAA, are at trust.railway.com; a BAA requires Enterprise.
Status changed to Awaiting User Response Railway • about 1 month ago
24 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 24 days ago