This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ofbiz-tools.git
The following commit(s) were added to refs/heads/master by this push:
new 0297c7e The new VM is vm1 (not vm4)
0297c7e is described below
commit 0297c7ee293ed428e519598df145a177699fd0dd
Author: Jacques Le Roux <jacques.le.r...@les7arts.com>
AuthorDate: Thu Mar 24 17:52:15 2022 +0100
The new VM is vm1 (not vm4)
---
demo-backup/README.md | 38 +++++++++++++++++++-------------------
1 file changed, 19 insertions(+), 19 deletions(-)
diff --git a/demo-backup/README.md b/demo-backup/README.md
index b16a359..29619c9 100644
--- a/demo-backup/README.md
+++ b/demo-backup/README.md
@@ -1,12 +1,12 @@
# General description
-Three instances of OFBiz run on the OFBiz demo VM3 at
https://ofbiz-vm3.apache.org.
+Three instances of OFBiz run on the OFBiz demo VM at
https://ofbiz-vm1.apache.org.
* trunk: the trunk version
* stable: the last stable version (currently 18.12)
* next: the next stable version (currently 22.01)
-
+
This is the 3rd instance of VM we use hence the 3 in its domain name.
-The root of https://ofbiz-vm3.apache.org is the so called bigfiles directory
which is actually at /var/www/ofbiz/big-files.
+The root of https://ofbiz-vm1.apache.org is the so called bigfiles directory
which is actually at /var/www/ofbiz/big-files.
We own 3 Apache sub domains
@@ -14,23 +14,23 @@ We own 3 Apache sub domains
* https://demo-stable.ofbiz.apache.org
* https://demo-next.ofbiz.apache.org
-The Puppet configuration is at
-https://github.com/apache/infrastructure-p6/blob/production/data/nodes/ofbiz-vm3.apache.org.yaml
+The Puppet configuration is at
+https://github.com/apache/infrastructure-p6/blob/production/data/nodes/ofbiz-vm1.apache.org.yaml
It's currently impossible to directly modify, it's a private Github repo.
Just create an Infra Jira asking for the wanted change...and be patient ;)
# Actions on demos
-SSH to *ofbiz-vm3.apache.org* server (a VM actualy), then follow the below
procedure.
+SSH to *ofbiz-vm1.apache.org* server (a VM actualy), then follow the below
procedure.
You will need to use OTP (One Time Password). For documentation on how to use
OPIE (One time Passwords In Everything), see [this
page](https://cwiki.apache.org/confluence/display/INFRA/OPIE "OTP doc").
->_Note_: **Only run the ofbiz demos using the 'ofbizDemo' user, never run as
root.**
-
+>_Note_: **Only run the ofbiz demos using the 'ofbizDemo' user, never run as
root.**
+
You need to be registered as a sudoer (ask Infra).
-
+
Then sudo to the ofbizDemo user:
sudo -s -u ofbizDemo -H
-
+
Sudo uses OTP. Use a tool like https://selfserve.apache.org/otp-md5.html
to generate the OTP
You can then start/stop as required.
@@ -49,14 +49,14 @@ Also note that the demos are usually updated and
started/stopped automatically u
You need first to create a branchAA.mm directory under the ofbizDemo directory
and to clone the related releaseAA.mm in this new directory. Then to copy and
apply the patches contained in the next-manual.sh and stable-manual.sh files,
read the comments in these files for details.
-Looking at the Puppet configuration (see above) you will see that you only
need to change the next-manual.sh and stable-manual.sh files to upgrade stable
and next demos. Because they are defined in the Puppet configuration by
respectively
+Looking at the Puppet configuration (see above) you will see that you only
need to change the next-manual.sh and stable-manual.sh files to upgrade stable
and next demos. Because they are defined in the Puppet configuration by
respectively
+
+ stable: ProxyPass / ajp://localhost:18009/
+ next : ProxyPass / ajp://localhost:28009/
- stable: ProxyPass / ajp://localhost:18009/
- next : ProxyPass / ajp://localhost:28009/
-
-Finally you need to kill the current stable and next processes before running
again the demos using
+Finally you need to kill the current stable and next processes before running
again the demos using
- ./all-manual-nicely.sh
+ ./all-manual-nicely.sh
## Letsencrypt certificate update
@@ -66,18 +66,18 @@ It was a time when every 3 months we needed to manually
update our Letsencrypt c
I got this message today (2020-04-17):
- Processing /etc/letsencrypt/renewal/ofbiz-vm3.apache.org.conf
+ Processing /etc/letsencrypt/renewal/ofbiz-vm1.apache.org.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
Cert not yet due for renewal
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
The following certs are not due for renewal yet:
- /etc/letsencrypt/live/ofbiz-vm3.apache.org/fullchain.pem expires on
2020-06-08 (skipped)
+ /etc/letsencrypt/live/ofbiz-vm1.apache.org/fullchain.pem expires on
2020-06-08 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - -
and always since: it's OK. Nothing to do, it's automated. :)
-# Current restriction
+# Current restriction
~~If you want to restart only a single instance you can respectively use
trunk-manual-nicely.sh
stable-manual-nicely.sh
