How to set up multiple Tomcat instances?
Is there a proper way to run more than one tomcat instance on an Ubuntu server?
I've done some searching and found two options:
- Download a zipped tomcat and manually deploy it. The obvious con is that it won't be upgraded using
apt-get
. - Use some advanced scripting, which is dangerous in a production server.
Any other ideas to cleanly run another instance?
Thanks in advance,
Adam
server tomcat multiple-instances
add a comment |
Is there a proper way to run more than one tomcat instance on an Ubuntu server?
I've done some searching and found two options:
- Download a zipped tomcat and manually deploy it. The obvious con is that it won't be upgraded using
apt-get
. - Use some advanced scripting, which is dangerous in a production server.
Any other ideas to cleanly run another instance?
Thanks in advance,
Adam
server tomcat multiple-instances
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56
add a comment |
Is there a proper way to run more than one tomcat instance on an Ubuntu server?
I've done some searching and found two options:
- Download a zipped tomcat and manually deploy it. The obvious con is that it won't be upgraded using
apt-get
. - Use some advanced scripting, which is dangerous in a production server.
Any other ideas to cleanly run another instance?
Thanks in advance,
Adam
server tomcat multiple-instances
Is there a proper way to run more than one tomcat instance on an Ubuntu server?
I've done some searching and found two options:
- Download a zipped tomcat and manually deploy it. The obvious con is that it won't be upgraded using
apt-get
. - Use some advanced scripting, which is dangerous in a production server.
Any other ideas to cleanly run another instance?
Thanks in advance,
Adam
server tomcat multiple-instances
server tomcat multiple-instances
edited Aug 11 '16 at 14:38
Reinier Post
15113
15113
asked Nov 14 '10 at 10:31
Adam MatanAdam Matan
4,734195786
4,734195786
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56
add a comment |
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56
add a comment |
3 Answers
3
active
oldest
votes
I am setting this up on Ubuntu 14.04.3 LTS.
I am using the Tomcat 7 provided by the tomcat7
package.
It installs Tomcat as a system service by providing a standard init script:
/etc/init.d/tomcat7
and configuration file:
/etc/default/tomcat7
Tomcat supports running multiple instances with the same server software.
The server software is located in $CATALINA_HOME
, the files for the instance are located in $CATALINA_BASE
. They are defined as follows in /etc/init.d/tomcat7
:
NAME=tomcat7
CATALINA_HOME=/usr/share/$NAME
CATALINA_BASE=/var/lib/$NAME
(Caveat: when editing files in the latter, be aware that it has some symlinks into the former.)
The tomcat7-user
package provides the utility tomcat7-instance-create
that can be used to create a directory tree for an additional Tomcat instance, including a bin/
directory with scripts for starting and stopping the instance manually.
What I haven't found is support for turning such an additional instance into a system service. Therefore, it must be done manually, e.g. as follows:
- Pick a value for the service name; it will be
$NAME
in the new init script. - Create a new user with that name that will own the files for the Tomcat instance and as which Tomcat will run. It can be a system user, its properties should be the same as for the
tomcat7
user. - Run
tomcat7-instance-create
as that user to create a Tomcat instance. - Configure it and install the web application(s) you want to run with it. Test them using its
bin/startup.sh
andbin/shutdown.sh
scripts. - Move the logs to
/var/log/$NAME
and symlink them back tologs/
of the new Tomcat instance. - Write
/etc/init.d/$NAME
, e.g. by copying and modifying/etc/init.d/tomcat7
and modifying the assignment to$NAME
. (It would be nicer if you didn't need to copy the whole script but could just create a link to it.) - Write
/etc/default/$NAME
to point at your Tomcat instance and user. - Use
upstart-rc.d
to install the new service.
I gleaned some of the details from Kodjo-Kuma Djomeda.
add a comment |
Have you considered configuring several webapps directories instead of running multiple tomcat instances?
Of course there are cases where you really need multiple instances but in case of serving same application separately for multiple hosts, you may do it by adding multiple declarations in server.xml:
<Host name="host1.example.com" appBase="host1"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
<Host name="host2.example.com" appBase="host2"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
Now you may create "/var/lib/tomcat6/host1" and "/var/lib/tomcat6/host2" directories and deploy WAR files to them.
add a comment |
I did the following:
run the following command with the dir where tomcat should be created:
tomcat8-instance-create staging
than changed the ports to something unique (if you have other tomcat8 running:
nano conf/server.xml
i use the same user as the original tomcat8 so i make sure all files are owned by tomcat8
chown -R tomcat8:tomcat8 *
i copied the script tomcat8 script in /etc/init.d/
cp /etc/init.d/tomcat8 /etc/init.d/tomcat8_staging
and edited the script to make it work with my new staging env:
nano /etc/init.d/tomcat8_staging
i had to edit the following lines to:
NAME=tomcat8_staging
DEFAULT=/etc/default/tomcat8
CATALINA_BASE=/app/tomcat8/staging
CATALINA_HOME=/usr/share/tomcat8
and finally i enabled the server like this:
systemctl enable tomcat8_staging
when starting it with:
service tomcat8_staging start
i got an error about missing policy files so i created a link for that in the conf dir:
ln -s /etc/tomcat8/policy.d policy.d
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f13172%2fhow-to-set-up-multiple-tomcat-instances%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I am setting this up on Ubuntu 14.04.3 LTS.
I am using the Tomcat 7 provided by the tomcat7
package.
It installs Tomcat as a system service by providing a standard init script:
/etc/init.d/tomcat7
and configuration file:
/etc/default/tomcat7
Tomcat supports running multiple instances with the same server software.
The server software is located in $CATALINA_HOME
, the files for the instance are located in $CATALINA_BASE
. They are defined as follows in /etc/init.d/tomcat7
:
NAME=tomcat7
CATALINA_HOME=/usr/share/$NAME
CATALINA_BASE=/var/lib/$NAME
(Caveat: when editing files in the latter, be aware that it has some symlinks into the former.)
The tomcat7-user
package provides the utility tomcat7-instance-create
that can be used to create a directory tree for an additional Tomcat instance, including a bin/
directory with scripts for starting and stopping the instance manually.
What I haven't found is support for turning such an additional instance into a system service. Therefore, it must be done manually, e.g. as follows:
- Pick a value for the service name; it will be
$NAME
in the new init script. - Create a new user with that name that will own the files for the Tomcat instance and as which Tomcat will run. It can be a system user, its properties should be the same as for the
tomcat7
user. - Run
tomcat7-instance-create
as that user to create a Tomcat instance. - Configure it and install the web application(s) you want to run with it. Test them using its
bin/startup.sh
andbin/shutdown.sh
scripts. - Move the logs to
/var/log/$NAME
and symlink them back tologs/
of the new Tomcat instance. - Write
/etc/init.d/$NAME
, e.g. by copying and modifying/etc/init.d/tomcat7
and modifying the assignment to$NAME
. (It would be nicer if you didn't need to copy the whole script but could just create a link to it.) - Write
/etc/default/$NAME
to point at your Tomcat instance and user. - Use
upstart-rc.d
to install the new service.
I gleaned some of the details from Kodjo-Kuma Djomeda.
add a comment |
I am setting this up on Ubuntu 14.04.3 LTS.
I am using the Tomcat 7 provided by the tomcat7
package.
It installs Tomcat as a system service by providing a standard init script:
/etc/init.d/tomcat7
and configuration file:
/etc/default/tomcat7
Tomcat supports running multiple instances with the same server software.
The server software is located in $CATALINA_HOME
, the files for the instance are located in $CATALINA_BASE
. They are defined as follows in /etc/init.d/tomcat7
:
NAME=tomcat7
CATALINA_HOME=/usr/share/$NAME
CATALINA_BASE=/var/lib/$NAME
(Caveat: when editing files in the latter, be aware that it has some symlinks into the former.)
The tomcat7-user
package provides the utility tomcat7-instance-create
that can be used to create a directory tree for an additional Tomcat instance, including a bin/
directory with scripts for starting and stopping the instance manually.
What I haven't found is support for turning such an additional instance into a system service. Therefore, it must be done manually, e.g. as follows:
- Pick a value for the service name; it will be
$NAME
in the new init script. - Create a new user with that name that will own the files for the Tomcat instance and as which Tomcat will run. It can be a system user, its properties should be the same as for the
tomcat7
user. - Run
tomcat7-instance-create
as that user to create a Tomcat instance. - Configure it and install the web application(s) you want to run with it. Test them using its
bin/startup.sh
andbin/shutdown.sh
scripts. - Move the logs to
/var/log/$NAME
and symlink them back tologs/
of the new Tomcat instance. - Write
/etc/init.d/$NAME
, e.g. by copying and modifying/etc/init.d/tomcat7
and modifying the assignment to$NAME
. (It would be nicer if you didn't need to copy the whole script but could just create a link to it.) - Write
/etc/default/$NAME
to point at your Tomcat instance and user. - Use
upstart-rc.d
to install the new service.
I gleaned some of the details from Kodjo-Kuma Djomeda.
add a comment |
I am setting this up on Ubuntu 14.04.3 LTS.
I am using the Tomcat 7 provided by the tomcat7
package.
It installs Tomcat as a system service by providing a standard init script:
/etc/init.d/tomcat7
and configuration file:
/etc/default/tomcat7
Tomcat supports running multiple instances with the same server software.
The server software is located in $CATALINA_HOME
, the files for the instance are located in $CATALINA_BASE
. They are defined as follows in /etc/init.d/tomcat7
:
NAME=tomcat7
CATALINA_HOME=/usr/share/$NAME
CATALINA_BASE=/var/lib/$NAME
(Caveat: when editing files in the latter, be aware that it has some symlinks into the former.)
The tomcat7-user
package provides the utility tomcat7-instance-create
that can be used to create a directory tree for an additional Tomcat instance, including a bin/
directory with scripts for starting and stopping the instance manually.
What I haven't found is support for turning such an additional instance into a system service. Therefore, it must be done manually, e.g. as follows:
- Pick a value for the service name; it will be
$NAME
in the new init script. - Create a new user with that name that will own the files for the Tomcat instance and as which Tomcat will run. It can be a system user, its properties should be the same as for the
tomcat7
user. - Run
tomcat7-instance-create
as that user to create a Tomcat instance. - Configure it and install the web application(s) you want to run with it. Test them using its
bin/startup.sh
andbin/shutdown.sh
scripts. - Move the logs to
/var/log/$NAME
and symlink them back tologs/
of the new Tomcat instance. - Write
/etc/init.d/$NAME
, e.g. by copying and modifying/etc/init.d/tomcat7
and modifying the assignment to$NAME
. (It would be nicer if you didn't need to copy the whole script but could just create a link to it.) - Write
/etc/default/$NAME
to point at your Tomcat instance and user. - Use
upstart-rc.d
to install the new service.
I gleaned some of the details from Kodjo-Kuma Djomeda.
I am setting this up on Ubuntu 14.04.3 LTS.
I am using the Tomcat 7 provided by the tomcat7
package.
It installs Tomcat as a system service by providing a standard init script:
/etc/init.d/tomcat7
and configuration file:
/etc/default/tomcat7
Tomcat supports running multiple instances with the same server software.
The server software is located in $CATALINA_HOME
, the files for the instance are located in $CATALINA_BASE
. They are defined as follows in /etc/init.d/tomcat7
:
NAME=tomcat7
CATALINA_HOME=/usr/share/$NAME
CATALINA_BASE=/var/lib/$NAME
(Caveat: when editing files in the latter, be aware that it has some symlinks into the former.)
The tomcat7-user
package provides the utility tomcat7-instance-create
that can be used to create a directory tree for an additional Tomcat instance, including a bin/
directory with scripts for starting and stopping the instance manually.
What I haven't found is support for turning such an additional instance into a system service. Therefore, it must be done manually, e.g. as follows:
- Pick a value for the service name; it will be
$NAME
in the new init script. - Create a new user with that name that will own the files for the Tomcat instance and as which Tomcat will run. It can be a system user, its properties should be the same as for the
tomcat7
user. - Run
tomcat7-instance-create
as that user to create a Tomcat instance. - Configure it and install the web application(s) you want to run with it. Test them using its
bin/startup.sh
andbin/shutdown.sh
scripts. - Move the logs to
/var/log/$NAME
and symlink them back tologs/
of the new Tomcat instance. - Write
/etc/init.d/$NAME
, e.g. by copying and modifying/etc/init.d/tomcat7
and modifying the assignment to$NAME
. (It would be nicer if you didn't need to copy the whole script but could just create a link to it.) - Write
/etc/default/$NAME
to point at your Tomcat instance and user. - Use
upstart-rc.d
to install the new service.
I gleaned some of the details from Kodjo-Kuma Djomeda.
edited Sep 17 '16 at 20:06
answered Feb 5 '16 at 11:08
Reinier PostReinier Post
15113
15113
add a comment |
add a comment |
Have you considered configuring several webapps directories instead of running multiple tomcat instances?
Of course there are cases where you really need multiple instances but in case of serving same application separately for multiple hosts, you may do it by adding multiple declarations in server.xml:
<Host name="host1.example.com" appBase="host1"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
<Host name="host2.example.com" appBase="host2"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
Now you may create "/var/lib/tomcat6/host1" and "/var/lib/tomcat6/host2" directories and deploy WAR files to them.
add a comment |
Have you considered configuring several webapps directories instead of running multiple tomcat instances?
Of course there are cases where you really need multiple instances but in case of serving same application separately for multiple hosts, you may do it by adding multiple declarations in server.xml:
<Host name="host1.example.com" appBase="host1"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
<Host name="host2.example.com" appBase="host2"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
Now you may create "/var/lib/tomcat6/host1" and "/var/lib/tomcat6/host2" directories and deploy WAR files to them.
add a comment |
Have you considered configuring several webapps directories instead of running multiple tomcat instances?
Of course there are cases where you really need multiple instances but in case of serving same application separately for multiple hosts, you may do it by adding multiple declarations in server.xml:
<Host name="host1.example.com" appBase="host1"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
<Host name="host2.example.com" appBase="host2"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
Now you may create "/var/lib/tomcat6/host1" and "/var/lib/tomcat6/host2" directories and deploy WAR files to them.
Have you considered configuring several webapps directories instead of running multiple tomcat instances?
Of course there are cases where you really need multiple instances but in case of serving same application separately for multiple hosts, you may do it by adding multiple declarations in server.xml:
<Host name="host1.example.com" appBase="host1"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
<Host name="host2.example.com" appBase="host2"
unpackWARs="true" autoDeploy="true"
xmlValidation="false" xmlNamespaceAware="false" />
Now you may create "/var/lib/tomcat6/host1" and "/var/lib/tomcat6/host2" directories and deploy WAR files to them.
answered May 13 '11 at 10:53
Vilmantas BaranauskasVilmantas Baranauskas
943614
943614
add a comment |
add a comment |
I did the following:
run the following command with the dir where tomcat should be created:
tomcat8-instance-create staging
than changed the ports to something unique (if you have other tomcat8 running:
nano conf/server.xml
i use the same user as the original tomcat8 so i make sure all files are owned by tomcat8
chown -R tomcat8:tomcat8 *
i copied the script tomcat8 script in /etc/init.d/
cp /etc/init.d/tomcat8 /etc/init.d/tomcat8_staging
and edited the script to make it work with my new staging env:
nano /etc/init.d/tomcat8_staging
i had to edit the following lines to:
NAME=tomcat8_staging
DEFAULT=/etc/default/tomcat8
CATALINA_BASE=/app/tomcat8/staging
CATALINA_HOME=/usr/share/tomcat8
and finally i enabled the server like this:
systemctl enable tomcat8_staging
when starting it with:
service tomcat8_staging start
i got an error about missing policy files so i created a link for that in the conf dir:
ln -s /etc/tomcat8/policy.d policy.d
add a comment |
I did the following:
run the following command with the dir where tomcat should be created:
tomcat8-instance-create staging
than changed the ports to something unique (if you have other tomcat8 running:
nano conf/server.xml
i use the same user as the original tomcat8 so i make sure all files are owned by tomcat8
chown -R tomcat8:tomcat8 *
i copied the script tomcat8 script in /etc/init.d/
cp /etc/init.d/tomcat8 /etc/init.d/tomcat8_staging
and edited the script to make it work with my new staging env:
nano /etc/init.d/tomcat8_staging
i had to edit the following lines to:
NAME=tomcat8_staging
DEFAULT=/etc/default/tomcat8
CATALINA_BASE=/app/tomcat8/staging
CATALINA_HOME=/usr/share/tomcat8
and finally i enabled the server like this:
systemctl enable tomcat8_staging
when starting it with:
service tomcat8_staging start
i got an error about missing policy files so i created a link for that in the conf dir:
ln -s /etc/tomcat8/policy.d policy.d
add a comment |
I did the following:
run the following command with the dir where tomcat should be created:
tomcat8-instance-create staging
than changed the ports to something unique (if you have other tomcat8 running:
nano conf/server.xml
i use the same user as the original tomcat8 so i make sure all files are owned by tomcat8
chown -R tomcat8:tomcat8 *
i copied the script tomcat8 script in /etc/init.d/
cp /etc/init.d/tomcat8 /etc/init.d/tomcat8_staging
and edited the script to make it work with my new staging env:
nano /etc/init.d/tomcat8_staging
i had to edit the following lines to:
NAME=tomcat8_staging
DEFAULT=/etc/default/tomcat8
CATALINA_BASE=/app/tomcat8/staging
CATALINA_HOME=/usr/share/tomcat8
and finally i enabled the server like this:
systemctl enable tomcat8_staging
when starting it with:
service tomcat8_staging start
i got an error about missing policy files so i created a link for that in the conf dir:
ln -s /etc/tomcat8/policy.d policy.d
I did the following:
run the following command with the dir where tomcat should be created:
tomcat8-instance-create staging
than changed the ports to something unique (if you have other tomcat8 running:
nano conf/server.xml
i use the same user as the original tomcat8 so i make sure all files are owned by tomcat8
chown -R tomcat8:tomcat8 *
i copied the script tomcat8 script in /etc/init.d/
cp /etc/init.d/tomcat8 /etc/init.d/tomcat8_staging
and edited the script to make it work with my new staging env:
nano /etc/init.d/tomcat8_staging
i had to edit the following lines to:
NAME=tomcat8_staging
DEFAULT=/etc/default/tomcat8
CATALINA_BASE=/app/tomcat8/staging
CATALINA_HOME=/usr/share/tomcat8
and finally i enabled the server like this:
systemctl enable tomcat8_staging
when starting it with:
service tomcat8_staging start
i got an error about missing policy files so i created a link for that in the conf dir:
ln -s /etc/tomcat8/policy.d policy.d
answered Jan 9 at 16:14
tibitibi
1012
1012
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f13172%2fhow-to-set-up-multiple-tomcat-instances%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
why do you need more than one instance?
– cupakob
Nov 14 '10 at 10:57
You need more than one instance if the deployment and runtime management for different web applications must be independent (e.g. executed at different times or by different people).
– Reinier Post
Feb 5 '16 at 10:27
See also superuser.com/questions/142791/…
– Reinier Post
Feb 5 '16 at 11:56