[DOCU-170] propertyfiles parameter in restoring a backup Created: 14/Jul/11 Updated: 14/Jul/11 Resolved: 14/Jul/11 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Antti Hietala |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
Document the use of propertyfiles parameter when restoring a backup. See Nils' comment on the Backup module page. This is the list of default locations where the initializer will try to find a magnolia.properties configuration file:
The default location can be overridden using the magnolia.initialization.file context parameter in web.xml. So AbstractBasicExecutable will look for the location of your properties in web.xml next. If you put the properties file in a custom location and didn't say so in web.xml, you need to pass the location with propertyfiles parameter or the restore script won't find it. |
| Comments |
| Comment by Magnolia International [ 14/Jul/11 ] |
|
Oh my bad. I didn't remember the tools actually DID parse the web.xml. In short, I wouldn't go further than mentioning the command-line argument, saying you can pass whatever locations there, in case they can't be resolved via web.xml, or if you simply want to use different properties. ... and better, if the tool itself isn't self-explicit, then let's improve it. There is (should be?) an --help flag, and the description should be there. |
| Comment by Antti Hietala [ 14/Jul/11 ] |
|
Documented parameters in the article. |