SnapshotProfiles.properties

Open /etc/escenic/engine/common/com/escenic/snapshot/SnapshotProfiles.properties for editing and set the following properties:

profile.default.sections

This property defines the content of the default Snapshot repo. It is a comma-separated list of section unique names. The listed sections (that is, templates) and all their subsections will be stored in the default Snapshot repo. The default value of ece_frontpage selects the entire contents of the blueprint:

profile.default.sections=ece_frontpage

profile.default.repository

This property specifies the URL of the remote (shared) git repo in which the blueprint is to be stored. If you have set up a repo on BitBucket, for example, you might specify:

profile.default.repository=https://my-user@bitbucket.org/my-user/blueprints.git

profile.default.snapshot-path

This property specifies location in which the blueprint is to be stored within the git repo. It must be a relative path, but other than that can be anything you like, for example:

profile.default.snapshot-path=snapshot/src/main

profile.default.username

The user name defined for this profile on the remote git server

profile.default.username=user-name

profile.default.password

The password defined for this profile on the remote git server

profile.default.password=password

profile.default.author-name

The author name defined for this profile on the remote git server

profile.default.author-name=author-name

profile.default.author-email

The email address defined for this profile on the remote git server

profile.default.author-email=author-email

Together, these properties form a Snapshot profile called default. One profile corresponds to one remote repo. If you only have one blueprint to manage, then you will only need one repo, and you can just set the three properties listed above. If you have several blueprints that you want to manage, then you can choose either to keep them all in the default repo or to create a separate repo for each blueprint. If you choose to put each blueprint in its own repo, then you will need to define additional profiles by adding similar sets of properties to the file, one set for each profile. You could create a magazine profile, for example, by adding the properties profile.magazine.sections, profile.magazine.repository, profile.magazine.snapshot-path, profile.magazine.username, profile.magazine.password, profile.magazine.author-name and profile.magazine.author-email.

Once you have created the profiles you want, you must assign them to your blueprints. See Configuring the Blueprints for details.