Nginx configuration to handle two SPA
I have two different SPA (serving by two node server on different ports) behind Nginx reverse proxy. The problem is that both apps serve their static files from /static/files/
How can I config Nginx to serve the files from the right node server without changing the static folder name?
node.js nginx reverse-proxy
add a comment |
I have two different SPA (serving by two node server on different ports) behind Nginx reverse proxy. The problem is that both apps serve their static files from /static/files/
How can I config Nginx to serve the files from the right node server without changing the static folder name?
node.js nginx reverse-proxy
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add anpath_variable
in the url itself and decide based on that. Likehttps://example.com/nodejs1/
andhttps://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
Well in that case you have to go with the 2nd approach and set the path of static files during build process.nodejs1/static/files/
andnodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.
– front_end_dev
Nov 14 '18 at 15:05
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52
add a comment |
I have two different SPA (serving by two node server on different ports) behind Nginx reverse proxy. The problem is that both apps serve their static files from /static/files/
How can I config Nginx to serve the files from the right node server without changing the static folder name?
node.js nginx reverse-proxy
I have two different SPA (serving by two node server on different ports) behind Nginx reverse proxy. The problem is that both apps serve their static files from /static/files/
How can I config Nginx to serve the files from the right node server without changing the static folder name?
node.js nginx reverse-proxy
node.js nginx reverse-proxy
asked Nov 14 '18 at 9:13
Hadi RanjbarHadi Ranjbar
403413
403413
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add anpath_variable
in the url itself and decide based on that. Likehttps://example.com/nodejs1/
andhttps://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
Well in that case you have to go with the 2nd approach and set the path of static files during build process.nodejs1/static/files/
andnodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.
– front_end_dev
Nov 14 '18 at 15:05
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52
add a comment |
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add anpath_variable
in the url itself and decide based on that. Likehttps://example.com/nodejs1/
andhttps://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
Well in that case you have to go with the 2nd approach and set the path of static files during build process.nodejs1/static/files/
andnodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.
– front_end_dev
Nov 14 '18 at 15:05
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add an
path_variable
in the url itself and decide based on that. Like https://example.com/nodejs1/
and https://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add an
path_variable
in the url itself and decide based on that. Like https://example.com/nodejs1/
and https://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
Well in that case you have to go with the 2nd approach and set the path of static files during build process.
nodejs1/static/files/
and nodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.– front_end_dev
Nov 14 '18 at 15:05
Well in that case you have to go with the 2nd approach and set the path of static files during build process.
nodejs1/static/files/
and nodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.– front_end_dev
Nov 14 '18 at 15:05
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53296576%2fnginx-configuration-to-handle-two-spa%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53296576%2fnginx-configuration-to-handle-two-spa%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
1st Approach - Set a cookie value from backend and based on that value redirect to respective node server. 2nd Approach - add an
path_variable
in the url itself and decide based on that. Likehttps://example.com/nodejs1/
andhttps://example.com/nodejs2/
– front_end_dev
Nov 14 '18 at 9:43
The 1st approach seems good, but what if a user opens two tabs from each server? The cookie will override by one of the tabs and the solution won't work.
– Hadi Ranjbar
Nov 14 '18 at 10:53
Well in that case you have to go with the 2nd approach and set the path of static files during build process.
nodejs1/static/files/
andnodejs2/static/files/
. Did you use module bundler ( webpack etc ) for manage client side.– front_end_dev
Nov 14 '18 at 15:05
Yes, I have tried that. But I want to handle it without any change in Webpack building configuration. It is against "Convention over configuration" concept that 'CreateReactApp' is based on it. (I use ReactJs based on CreateReactApp)
– Hadi Ranjbar
Nov 14 '18 at 19:52