-Drepo.bootstrap=true not working

87 views
Skip to first unread message

Rafa Osudio

unread,
Jul 28, 2015, 8:49:30 AM7/28/15
to Hippo Community
We have a Hippo 10 project using MySQL.

To bootstrap a local repo with new content:

- Turned Autoexport off
- Stop server
- Checked out changes from source control system
- Start Hippo with -Drepo.bootstrap=true (or -Dcargo.jvm.args="-Drepo.bootstrap=true")

Expect the new content to be in place, but nothing has changed in the repository.

The only way to get the bootstrap process to work is by dropping the DB and creating it again.

William Borg Barthet

unread,
Jul 28, 2015, 8:54:21 AM7/28/15
to hippo-c...@googlegroups.com
Hi Rafa,

just to be sure, do you have new index entries in your hippoecm-extension.xml? Or reloadonstartup flags on some entries?

Please see [1] for details.

[1] - http://www.onehippo.org/library/development/reload-on-startup-initialize-items.html

--
Hippo Community Group: The place for all discussions and announcements about Hippo CMS (and HST, repository etc. etc.)
 
To post to this group, send email to hippo-c...@googlegroups.com
RSS: https://groups.google.com/group/hippo-community/feed/rss_v2_0_msgs.xml?num=50
---
You received this message because you are subscribed to the Google Groups "Hippo Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hippo-communi...@googlegroups.com.
Visit this group at http://groups.google.com/group/hippo-community.
For more options, visit https://groups.google.com/d/optout.



--
Amsterdam - Oosteinde 11, 1017 WT Amsterdam
Boston - 745 Atlantic Avenue, Boston, MA 02111
 
US +1 877 414 4776 (toll free)
Europe +31(0)20 522 4466
www.onehippo.com

Rafa Osudio

unread,
Jul 28, 2015, 9:51:33 AM7/28/15
to hippo-c...@googlegroups.com
Hi William,
we don't usually have changes in hippoecm-extension.xml. 
The changes are in the XML files referenced in "hippo:contentresource".
So when a developer creates a page (e.g. a new page under hst:workspace/hst:pages), should he set the hippo:reloadonstartup and hippo:version ?
What will happen next time when another node is added/modified/removed?

Cheers

You received this message because you are subscribed to a topic in the Google Groups "Hippo Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/hippo-community/hBHf0lgw1RA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to hippo-communi...@googlegroups.com.

William Borg Barthet

unread,
Jul 28, 2015, 1:51:28 PM7/28/15
to hippo-c...@googlegroups.com
Hi Rafa,

all the entries in the hippoecm-extension files will be used to bootstrap a new repository.

If you have an existing repository (as you do), no existing entries (present under /hippo:configuration/hippo:initialize/...) will be bootstrapped unless they are explicitly marked with a reloadonstartup flag.

When a developer creates a new page, he should mark the changed configuration files in the index with a reloadonstartup flag, or just bump the version if one is already present. If the version is lower than the Maven project version, it will not be reloaded (this prevents multiple reloads over several releases).

Please also note that your developers should not be creating all the pages in the workspace. That space is for prototype page instances, which are typically one-off landing pages created by end users. Developers should create pages in the rest of the HST configuration under /hst:hst/hst:pages.

Hope this helps,

William

Rafa Osudio

unread,
Jul 29, 2015, 3:48:55 AM7/29/15
to Hippo Community, w.borg...@onehippo.com
Thanks for the explanation William.
Will try to follow those guidelines.

Rafa
Reply all
Reply to author
Forward
0 new messages