-
Notifications
You must be signed in to change notification settings - Fork 12
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
What cloud provider to use for production? #25
Comments
Just an edit I changed the IP for it to http://54.145.137.3/ , for anyone that wants to access it. Also note, it's an old build and the final app hasn't been merged yet. To see it use the current open PR #31 |
A quick search pointed me to this resource https://github.com/cloudcommunity/Cloud-Free-Tier-Comparison. |
One more suggestion, we can host the frontend via github pages( see https://ashirrwad.github.io/playground/) and dedicate the cloud vm just for our flask api. This way we will just have to maintain the backend as github pages will take care of our react build. |
@ashirrwad I like that idea, that makes one less server process needed to run on the VM (better for the CPU budget on the free tier), and easier to maintain. I'll then set up play-api.fortran-lang.org subdomain to point to the Python backend, and we can then update the API URL in the frontend to point to play-api.fortran-lang.org rather than hardcoding the IP address. |
Yes, we should host as much as possible using static pages. |
Currently using AWS EC2 for the Python backend and GitHub Pages for the frontend. Please re-open this issue you want to discuss it further. |
@ashirrwad set it up on a free EC2 (AWS) instance (see http://34.235.154.182).
For long-term production, is there a preference for any other cloud provider? I have (mostly great) experience with DigitalOcean, but they don't have a free tier, so I recommend going with a provider that has a free tier and AWS seems fine to me.
Once we agree on the provider, the admins should create a dedicated fortran-lang account with that provider.
The text was updated successfully, but these errors were encountered: