Support for production docker image #20
Closed
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.
As I have commented 7 days ago and didn't found a proposal from the repository owner to the request, took the time today to do it myself. Now willing to share with others following the creation of this pull request.
Also updated README.md with details to build and execute the production image, without needing to clone the repo, adding those here as well.
An initial image (tiagorvmartins/wapy.dev) has been built and pushed to docker hub such that others can start spinning up and use it.
Production App Settings
Docker image
To build the production docker image use the following commannd:
Compose
Replace production environment file with your settings
Run the following command to get VAPID public and private keys:
Replace them accordingly on the .env.production
Choose/create the secret keys for the following environment variables
Replace your RESEND_API_KEY
Configure your domain on your RESEND account and adapt the following env vars
Configure SITE_URL environment with your domain
Optionally set the following env vars, for logging in with github and/or google.
Execute the stack