Can I add a directory as prefix for my configuration files in Nginx?
Clash Royale CLAN TAG#URR8PPP
I have a development environment with a simple Debian image whilst I also use a Jetware EC2 optimised Debian image for my staging environment.
The Jetware filesystem is mounted under the /jet, hence I have slight changes between my nginx.conf et vhost files, ex:
pid /run/nginx/nginx.pid;
vspid /jet/run/nginx/nginx.pid;
Or also include /jet/etc/nginx/mime.types; vs include /jet/etc/nginx/mime.types;
Is there a server_root directive of sort that I could add to my nginx.conf configuration, to keep the changes between files minimal ?
debian nginx
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
add a comment |
I have a development environment with a simple Debian image whilst I also use a Jetware EC2 optimised Debian image for my staging environment.
The Jetware filesystem is mounted under the /jet, hence I have slight changes between my nginx.conf et vhost files, ex:
pid /run/nginx/nginx.pid;
vspid /jet/run/nginx/nginx.pid;
Or also include /jet/etc/nginx/mime.types; vs include /jet/etc/nginx/mime.types;
Is there a server_root directive of sort that I could add to my nginx.conf configuration, to keep the changes between files minimal ?
debian nginx
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
add a comment |
I have a development environment with a simple Debian image whilst I also use a Jetware EC2 optimised Debian image for my staging environment.
The Jetware filesystem is mounted under the /jet, hence I have slight changes between my nginx.conf et vhost files, ex:
pid /run/nginx/nginx.pid;
vspid /jet/run/nginx/nginx.pid;
Or also include /jet/etc/nginx/mime.types; vs include /jet/etc/nginx/mime.types;
Is there a server_root directive of sort that I could add to my nginx.conf configuration, to keep the changes between files minimal ?
debian nginx
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
I have a development environment with a simple Debian image whilst I also use a Jetware EC2 optimised Debian image for my staging environment.
The Jetware filesystem is mounted under the /jet, hence I have slight changes between my nginx.conf et vhost files, ex:
pid /run/nginx/nginx.pid;
vspid /jet/run/nginx/nginx.pid;
Or also include /jet/etc/nginx/mime.types; vs include /jet/etc/nginx/mime.types;
Is there a server_root directive of sort that I could add to my nginx.conf configuration, to keep the changes between files minimal ?
debian nginx
debian nginx
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
edited Jan 4 at 1:29
Rui F Ribeiro
39.5k1479132
39.5k1479132
asked Jan 4 at 0:51
obaxobax
61
asked Jan 4 at 0:51
obaxobax
61
asked Jan 4 at 0:51
obaxobax
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It turns out that the approach (initiating a "$filesystem_root_dir" variable at the top of the file and assigning it one value per configuration) is:
- Not allowed (it throws the fatal:
nginx: [emerg] "set" directive is not allowed here in /etc/nginx/nginx.conf:1) - discouraged by the Nginx team:
Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism.
http://nginx.org/en/docs/faq/variables_in_config.html
I thought about a template generator but the cost way outweight the gains, so I'll either keep the files slighlty different moving forward.
answered Jan 8 at 18:47
obaxobax
61
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492356%2fcan-i-add-a-directory-as-prefix-for-my-configuration-files-in-nginx%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It turns out that the approach (initiating a "$filesystem_root_dir" variable at the top of the file and assigning it one value per configuration) is:
- Not allowed (it throws the fatal:
nginx: [emerg] "set" directive is not allowed here in /etc/nginx/nginx.conf:1) - discouraged by the Nginx team:
Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism.
http://nginx.org/en/docs/faq/variables_in_config.html
I thought about a template generator but the cost way outweight the gains, so I'll either keep the files slighlty different moving forward.
answered Jan 8 at 18:47
obaxobax
61
add a comment |
It turns out that the approach (initiating a "$filesystem_root_dir" variable at the top of the file and assigning it one value per configuration) is:
- Not allowed (it throws the fatal:
nginx: [emerg] "set" directive is not allowed here in /etc/nginx/nginx.conf:1) - discouraged by the Nginx team:
Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism.
http://nginx.org/en/docs/faq/variables_in_config.html
I thought about a template generator but the cost way outweight the gains, so I'll either keep the files slighlty different moving forward.
answered Jan 8 at 18:47
obaxobax
61
add a comment |
It turns out that the approach (initiating a "$filesystem_root_dir" variable at the top of the file and assigning it one value per configuration) is:
- Not allowed (it throws the fatal:
nginx: [emerg] "set" directive is not allowed here in /etc/nginx/nginx.conf:1) - discouraged by the Nginx team:
Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism.
http://nginx.org/en/docs/faq/variables_in_config.html
I thought about a template generator but the cost way outweight the gains, so I'll either keep the files slighlty different moving forward.
answered Jan 8 at 18:47
obaxobax
61
It turns out that the approach (initiating a "$filesystem_root_dir" variable at the top of the file and assigning it one value per configuration) is:
- Not allowed (it throws the fatal:
nginx: [emerg] "set" directive is not allowed here in /etc/nginx/nginx.conf:1) - discouraged by the Nginx team:
Variables should not be used as template macros. Variables are evaluated in the run-time during the processing of each request, so they are rather costly compared to plain static configuration. Using variables to store static strings is also a bad idea. Instead, a macro expansion and "include" directives should be used to generate configs more easily and it can be done with the external tools, e.g. sed + make or any other common template mechanism.
http://nginx.org/en/docs/faq/variables_in_config.html
I thought about a template generator but the cost way outweight the gains, so I'll either keep the files slighlty different moving forward.
answered Jan 8 at 18:47
obaxobax
61
answered Jan 8 at 18:47
obaxobax
61
answered Jan 8 at 18:47
obaxobax
61
answered Jan 8 at 18:47
obaxobax
61
61
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492356%2fcan-i-add-a-directory-as-prefix-for-my-configuration-files-in-nginx%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
