Add fly.io deployment config and instructions #36
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
guidanoli
reviewed
Feb 29, 2024
guidanoli
reviewed
Feb 29, 2024
claudioantonio
approved these changes
Mar 1, 2024
guidanoli
approved these changes
Mar 1, 2024
There was a problem hiding this comment.
@endersonmaia Don't worry about doing git rebase --autosquash.
We can squash the commits via the GitHub web interface.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will build and deploy a bug-less-validator with rollups-node:1.3.0 and PostgreSQL.
We still need to figure it out how/where to deploy the frontend.
If we can build a static version of the frontend code, I can deploy it together with this bug-less-validator fly.io app.
If it needs a nodejs runtime to serve the frontend, I can add it to the app image and serve both processes and create another fly.io application to serve the nodejs runtime for the frontend.
We could even embbed the PostgreSQL to use a single fly machine with everything inside (nodejs, rollups-node and PostgreSQL) to reduce costs.