Is "FRAPPE_SITE_NAME_HEADER" in compose.yml / pwd.yml the same as "host_name"?
See original GitHub issueMy PDF header and footer were not showing up and added it with these instruction and adding
"host_name":"YOURSERVERIP:PORTNUMBER",
to the file.
If I want to rebuild the docker, can I just add my serveripto FRAPPE_SITE_NAME_HEADER and is this the same as host_name ?
Issue Analytics
- State:
- Created 9 months ago
- Comments:5
Top Results From Across the Web
docker-compose.yml container_name and hostname
It has no effect on anything outside, and there's usually no point in setting it. (It has basically the same effect as hostname(1):...
Read more >Networking in Compose - Docker Documentation
Each container for a service joins the default network and is both reachable by other containers on that network, and discoverable by them...
Read more >Inconsistent value of $PWD variable · Issue #7848 - GitHub
My intention is to have shared volume between two containers (while also being directory on my local machine) - while I was testing...
Read more >Defining multiple similar services with Docker Compose
We only define the things that can't be inherited (like depends_on ), or that are specific to the actual service (host name).
Read more >Create multi-container apps with MySQL & Docker Compose
Add your text after the app definition, at the same level of indentation. YAML Copy. version: "3.7 ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Check nginx config, it is only used there. It is the site name by which the directory to serve site files are resolved. It is also passed to socketio and gunicorn as header to identify which site to serve
No. It needs to be the directory name from which site will be served or it will result in 404 site not found. You can set it to
$host
in nginx config and it will pick up the site from Host header.check the create-site service in pwd.yml it is run once container that runs a bash script to create site. use command
bench --site {site-name} set-config host_name "https://erp.example.com"
Thanks! Three last questions: