[DOCU-569] Production release Created: 24/Jun/15 Updated: 16/Oct/15 Resolved: 16/Oct/15 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | documentation-examples, hello-magnolia |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Gediminas Zalys | Assignee: | Antti Hietala |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
I have been searching around and can not find a clear example that would explain how would the production release work. Any links and suggestions will be appreciated! |
| Comments |
| Comment by Antti Hietala [ 24/Jun/15 ] |
Issue the Maven command mvn clean install. Maven builds your project and creates a war file in the target directory. See Creating a custom bundle.
Take advantage of the WAR file with multiple configurations mechanism. Create two magnolia.properties files - one for the author instance and another for the public. In the author instance file, set magnolia.bootstrap.authorInstance=true and define a bootstrap directory that contains the exported subscriber configuration XML.
See Matteo's blog post Ultimate Magnolia Website Launch Checklist. |
| Comment by Gediminas Zalys [ 26/Jun/15 ] |
|
Thanks Antti, great help once again! |