-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add initial deploy static site guide for Railway #12317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for astro-docs-2 ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Lunaria Status Overview🌕 This pull request will trigger status changes. Learn moreBy default, every PR changing files present in the Lunaria configuration's You can change this by adding one of the keywords present in the Tracked Files
Warnings reference
|
|
While writing this guide, Railway have deprecated Nixpacks, and set Railpack as the default builder. This means Astro websites deployed to Railway with no adapter are automatically deployed as static sites. I have updated this guide in the latest commit to remove the unnecessary |
sarah11918
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, @jacksmithxyz ! I appreciate the clarity and brevity!
I made a commit to just add periods to the end of all the numbered list items (it was easier than multiple suggestions), and I just have one question for you below! Looking forward to getting this updated guide merged really soon! 🙌
|
|
||
| [Railway](https://railway.com) is a deployment platform built to simplify your infrastructure stack from servers to observability with a single, scalable platform. | ||
|
|
||
| This guide is for deploying an Astro static site to Railway using either the web interface or Railway CLI tool. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we say that Railway can also deploy on-demand rendered sites, can we have a sentence here like:
To deploy an on-demand rendered site with a server adapter to Railway...
and then whatever brief guidance we'd give? "... see the Railway SSR deploy guide."
This would just make it seem less strange to come from the main page that has both badges, but see no mention of server rendered apps.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes complete sense to me. I'll get this updated.
Co-authored-by: Sarah Rainsberger <[email protected]>
|
Just waiting so I can check the deploy preview visually here and make sure it all looks correct, but I think we might have a winner! 😄 |
sarah11918
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do this thing! 🎉
Description
This PR is to convert the Railway deploy guide stub into a full guide for deploying an Astro static site on Railway, as per discussions with @sarah11918.
I've tried to keep inline with your notes and link to specific parts of the Railway docs where relevant, as opposed to saying "click here on the UI" in order to make the guide more applicable and resilient to UI changes.
This first version of the draft PR includes a single version: focusing solely on static site deployment and Railway's web UI.
I think ideally it would be good to expand this guide and/or PR to include project creation with the Railway CLI, deploying from templates, and also provide options for SSR deployment as well as static sites.
Looking forward to any feedback!
Jack