Feat: added volume, network and port to docker compose #814
Conversation
|
@djpiper28 is attempting to deploy a commit to the evroon's projects Team on Vercel. A member of the Team first needs to authorize it. |
djpiper28
changed the title
|
oh yeah I have some helm charts (Kubernetes for Bracket) should I make a PR to add them? |
|
@evroon are you able to review this when you have time please? |
| NEXT_PUBLIC_API_BASE_URL: "https://bracket.mywebsite.com" | ||
| # Go to https://dashboard.hcaptcha.com/signup, create a site and put the site key here | ||
| NEXT_PUBLIC_HCAPTCHA_SITE_KEY: "xxxxx" | ||
| NODE_ENV: "production" |
There was a problem hiding this comment.
We still want to keep the NODE_ENV: "production" right?
| NEXT_PUBLIC_HCAPTCHA_SITE_KEY: "xxxxx" | ||
| NODE_ENV: "production" | ||
| NEXT_PUBLIC_API_BASE_URL: "http://your-site.com:8400" | ||
| NEXT_PUBLIC_HCAPTCHA_SITE_KEY: "10000000-ffff-ffff-ffff-000000000001" # Public test key |
There was a problem hiding this comment.
I would prefer to keep the instruction # Go to https://dashboard.hcaptcha.com/signup, create a site and put the site key here here, since it is more clear what the value here should be. Putting a test key here would probably result in users just copy/pasting and accidentally using the test key in production without noticing I think
|
This PR is stale because it has been open for 45 days with no activity. Remove the |
|
I'll resolve my comments in a separate PR |
Fixes issue where containers cannot to talk to each other where the default docker network is isolated.