-
Notifications
You must be signed in to change notification settings - Fork 152
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
docs: Add deployment docs for automatic deployment #1544
Comments
Also happy to jump on a call if we want to discuss where this could live. |
Thanks for opening this up @mtwichel! In talking with the team this is for sure on the radar but we don't have it prioritized right now so I'm giving it a P2. That being said if you have content for this already and want to contribute it back (like the Railway docs) feel free to open the PR so we can get it reviewed and merged. It would be greatly appreciated. |
I'm more than happy to contribute - I mainly opened this up for some guidance on where to add the docs. I'm thinking
|
Any idea on what the |
I realize we don't have a general doc on "this is how you build a project". I'm not even sure if As for automatic, originally I thought that it would be a good place for explaining how to auto-deploy in a general sense But, now that I think about it, it's basically the same as the manual deployment just in whatever spec your CI/CD supports. Maybe we could have a section on "Autodeploy with Github" or something like that? It would be GitHub specific but I think that's by far the most common platform. The actual deploy step varies by platform, but not by much so we could just tell them to fill in the blank. |
Description
Currently, all of the docs for deploying Dart Frog are for manual deployment to their systems. However, which my PR adding docs for Railway deployment, I wrote instructions for automatic deployment from Github because that seemed the most natural for that platform.
This got me wondering if we should have docs specifically for doing automatic deployment onto different services. I'm envisioning something simple to start, like Google Cloud Build -> Cloud Run, or maybe Github Actions to AWS?
Obviously it could be different for everyone's systems and we can't (and shouldn't) cover every possible case. However, I think a really simple start would be nice for people new to backend in general.
Additionally, maybe it would even be cool to add something like this GitHub workflow for auto-deploying from GitHub, either to Very Good Workflows or this repository. I can open a separate ticket for that if you're into the idea.
LMK you thoughts! :blue_h
Requirements
Additional Context
No response
The text was updated successfully, but these errors were encountered: