updated README
This commit is contained in:
@@ -37,7 +37,7 @@ docker stack deploy \
|
|||||||
# Implementation details
|
# Implementation details
|
||||||
## Issues with HOSTNAME
|
## Issues with HOSTNAME
|
||||||
When deplyed via docker and published via Cloudflare there's an issue with `HOSTNAME` env variable:
|
When deplyed via docker and published via Cloudflare there's an issue with `HOSTNAME` env variable:
|
||||||
* if left unset, the server will use IP address assigned to container by Docker and **will not accept connections from outside**
|
* if left unset, the server will use IP address assigned to container by Docker (i.e. 10.0.20.3) and **will not accept connections from outside**
|
||||||
* if set to "0.0.0.0" the server will serve static pages, but will *reject API calls when submitting form*
|
* if set to "0.0.0.0" the server will serve static pages, but will *reject API calls when submitting form*
|
||||||
* if set to "rezije.app" the server will not start since the IP address it resolves with the given FQDN does not match any of the IP addresses assigned to the container
|
* if set to "rezije.app" the server will not start since the IP address it resolves with the given FQDN does not match any of the IP addresses assigned to the container
|
||||||
|
|
||||||
@@ -46,3 +46,5 @@ So there are the following issues:
|
|||||||
* server rejects API requests - can be fixed by adding `serverActions.allowedOrigins` option to `nextjs.config.js` file
|
* server rejects API requests - can be fixed by adding `serverActions.allowedOrigins` option to `nextjs.config.js` file
|
||||||
|
|
||||||
So these are the fixes which were implemented in order to be able to run server in production.
|
So these are the fixes which were implemented in order to be able to run server in production.
|
||||||
|
|
||||||
|
This is a hack indicating that I don't understand how the damn thing should be configured!
|
||||||
Reference in New Issue
Block a user