Swapnil Mane commented on OFBIZ-11472:

Hello team,
Here is the PR to update the deployment scripts to set up the demo instance for 
OFBiz 17.12 release and obsolete 13.07 demo.


After updating the deployment script, the following steps should be executed on 
OFBiz VM at ofbiz-vm3.apache.org :

 # {color:#0e101a}Clone the 17.12 release branch on VM{color}

{color:#0e101a}git clone -b release17.12 

 # {color:#0e101a}Update the deployment scripts on VM as per the PR
 # {color:#0e101a}Shut down all the instances manually by commands to free old 
ports, like port 20000 was occupied by 13.7

 # {color:#0e101a}Run the ./all-manual-nicely.sh script to redeploy all the 

Please have a look and let me know your kind feedback.

Thank you so much [~jleroux] for your inputs and guidance in this.{color}


> Demo instance setup for OFBiz 17.12 release and obsolete 13.07 demo
> -------------------------------------------------------------------
>                 Key: OFBIZ-11472
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11472
>             Project: OFBiz
>          Issue Type: Task
>          Components: Demo
>            Reporter: Swapnil Mane
>            Assignee: Swapnil Mane
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
> As discussed at [https://s.apache.org/kn1f9] thread,
> We will setup new demo instance for 17.12 and obsolete 13.07. 
> The OFBiz demos are hosted at ofbiz-vm3.apache.org VM
> Currently, OFBiz has three demo instance:
> -- Previous Stable Release 13.07 - Demo
> https://demo-old.ofbiz.apache.org/ordermgr/control/main
> -- Current Stable Release 16.11 - Demo
> https://demo-stable.ofbiz.apache.org/ordermgr/control/main
> -- Developer Trunk - Demo
> https://demo-trunk.ofbiz.apache.org/ordermgr/control/main
> So, as per new plan.
> https://demo-old.ofbiz.apache.org will point to 16.11 (which is currently 
> pointed at https://demo-stable.ofbiz.apache.org)
> And the newly setup 17.12 will be served at 
> https://demo-stable.ofbiz.apache.org
> For this, we will need to make changes in the deployment scripts.

This message was sent by Atlassian Jira

Reply via email to