Attention
You can now run different PHP versions per project:
Release v3.0.0-beta-0.1
Customize all virtual hosts globally¶
Table of Contents
Prerequisite¶
Ensure you have read and understood how vhost-gen templates work and where to find them
See also
Apply templates globally to all vhosts¶
When applying those templates, you do it globally for all projects. The only exception is if you have already a specific vhost template for a project in place.
See also
In order for template files to be picked up by the web server they must be copied to their correct filename.
Web server | Example template | Template name |
---|---|---|
Apache 2.2 | apache22.yml-example-vhost |
apache22.yml |
Apache 2.4 | apache24.yml-example-vhost |
apache24.yml |
Nginx stable | nginx.yml-example-vhost |
nginx.yml |
Nginx mainline | nginx.yml-example-vhost |
nginx.yml |
Important
Do not use *.yml-example-rproxy
templates for global configuration. These are only
intended to be used on a per project base.
Note
If you simply copy the files to their corresponding template file name, nothing will change as those templates reflect the same values the web servers are using.
Apache 2.2¶
- Navigate to
cfg/vhost-gen/
inside the Devilbox directory - Copy
apache22.yml-example-vhost
toapache22.yml
and restart the Devilbox - Whenever you adjust
apache22.yml
, you need to restart the Devilbox
Apache 2.4¶
- Navigate to
cfg/vhost-gen/
inside the Devilbox directory - Copy
apache24.yml-example-vhost
toapache24.yml
and restart the Devilbox - Whenever you adjust
apache24.yml
, you need to restart the Devilbox
Nginx stable and Nginx mainline¶
- Navigate to
cfg/vhost-gen/
inside the Devilbox directory - Copy
nginx.yml-example-vhost
tonginx.yml
and restart the Devilbox - Whenever you adjust
nginx.yml
, you need to restart the Devilbox