Daniel Watford created OFBIZ-12786:
--------------------------------------
Summary: Use container image for demo-trunk site
Key: OFBIZ-12786
URL: https://issues.apache.org/jira/browse/OFBIZ-12786
Project: OFBiz
Issue Type: Improvement
Affects Versions: Upcoming Branch
Reporter: Daniel Watford
Assignee: Daniel Watford
Fix For: Upcoming Branch
Mailing list thread:
[https://lists.apache.org/thread/jlvjztq0xd7kkytx16ngnlrjnhb2obhz]
OFBIZ-12781 introduced functionality to build and publish container images for
the ofbiz-framework trunk branch in response to new commits. Published
container images can be viewed here:
[https://github.com/apache/ofbiz-framework/pkgs/container/ofbiz]
While experimenting with docker containers on host ofbiz-vm1.apache.org, under
OFBIZ-12757, 3 new hostnames were served using containers -
[https://exp1.ofbiz.apache.org/partymgr,]
[https://exp2.ofbiz.apache.org/partymgr|https://exp1.ofbiz.apache.org/partymgr]
and [https://exp3.ofbiz.apache.org/partymgr.] Scripts deployed to
ofbiz-vm1.apache.org are successfully recreating the containers that serve
these demo sites daily.
The demo-trunk ([http://demo-trunk.ofbiz.apache.org/partymgr)] site is
currently deployed by rebuilding from sources on ofbiz-vm1.apache.org daily.
This ticket is to change the deployment approach used for demo-trunk to pull
and use the pre-built container images rather that rebuilding from sources.
An expected benefit of this approach is that the daily refresh of the
demo-trunk site will be faster since the software build phase will be avoided.
Further, we will encapsulate the JDK version needed for demo-trunk in the
container image, avoiding the need to modify settings on the host when OFBiz
moves to a different JDK version in future.
Some items to overcome to ensure a like-for-like replacement of demo-trunk are:
* Ensure the birt plugin is disabled. (Handled in OFBIZ-12783)
* Replicate footer information inserted during build by the gitInfoFooter
gradle task. (Handled in OFBIZ-12785)
* Set content URL properties in url.properties. (Addressed by environment
variables passed to the docker container)
* Set fop.xconf properties. (This should be handled through scripts executed
in the container's after-config-applied.d hook)
* Set solr.config.
** The patch currently applied to demo-trunk adds a new property to
solr.config and modifies file
plugins/solr/src/main/java/org/apache/ofbiz/solr/SolrUtil.java to read that new
property as a full Solr URL.
** Given the standard properties already read by the SolrUtil class, it does
not appear that the new property is needed. The desired URL should be
constructable using existing properties.
** Therefore the settings properties within the container should be sufficient
to replicate current demo-trunk deployment behaviour.
** A test will be needed to prove Solr continues to function as needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
