My hippo instance repository is backed by a mysql db. When making changes to FTL files in repository-data/webfiles, and redeploying the cms.war with cargo, the binary webfiles are not changed in the repository. The cms.war however, contains a jar called “myproject-repository-data-webfiles-0.1.0-SNAPSHOT.jar” which has the updated contents.
What am I overlooking here? How does hippo sync these binaries with the repository? What is the mechanism behind it.
Thanks
When you are developing locally, any change made to the webfiles get instantly synched with your local repo. Do you not see the updated webfiles in cms/console? If these webfiles are large files, you need to change the webfile module settings to allow it to synch larger files perhaps. See the configuration at /hippo:configuration/hippo:modules/webfiles/hippo:moduleconfig
I am deploying cms.war to a docker container, so this would be the same as deploying to a remote server.
How does it work when you for example deploy to a remote environment? How does Hippo sync those binary webfiles to the repository?
File size is below 256kb
Joeri https://community.bloomreach.com/u/joeri
July 17My hippo instance repository is backed by a mysql db. When making changes
to FTL files in repository-data/webfiles, and redeploying the cms.war with
cargo, the binary webfiles are not changed in the repository. The cms.war
however, contains a jar called “myproject-repository-data-webfiles-0.1.0-SNAPSHOT.jar”
which has the updated contents.
What am I overlooking here? How does hippo sync these binaries with the
repository? What is the mechanism behind it.
you are overlooking documentation which is located here:
cheers
/m
Changes in repository-data are packaged into a jar which is declared as dependency in cms webapp. On deployment of cms.war to tomcat, this jar is read and repository is bootstrapped with the files in this repository-data jar. Are you sure that the changes you make end up in reposioty-data jar?
yes, the repository-data-webfiles-0.1.0-SNAPSHOT.jar is up to date in folder cms\target\cms\WEB-INF\lib
I do run with “REP_OPTS=”-Drepo.bootstrap=false" does that influence this?
Possibly although I didn’t test it. Here’s from documentation: Bootstrapping - Bloomreach Experience Manager (PaaS/Self-Hosted) - The Fast and Flexible Headless CMS
Blockquote
If data has been bootstrapped into the repository before the current startup, the repo.bootstrap system property controls the bootstrapping. The following values are supported:
false
No bootstrapping is attempted. Incoming repository data changes are not processed, and the repository data is not changed.
Yes, in v12+ the webfiles bundle is bootstrapped by the config management system, which is disabled when you use repo.bootstrap=false. This would explain why your updated webfiles contents are not being used.
Thanks for the valuable input. It’s working.
I switched the bootstrap to false initially because I thought it would not be OK to run it enabled in a production-like system.
But I guess that the mechanisms in Hippo are smart enough then, not to interfere with user generated content by switching this on.
The new configuration management system in v12 is much, much more sophisticated than older versions. It is designed to be safe for production use cases, though of course there may still be undiscovered bugs. At the very least, you’ll need to enable it when deploying new config or webfiles. If you want to set repo.bootstrap=false for other times, that is also supported.