Opened 9 years ago
Closed 9 years ago
#746 closed enhancement (fixed)
Use property filtering to prepare configuration for specific environments
| Reported by: | Twan Goosen | Owned by: | Twan Goosen |
|---|---|---|---|
| Priority: | minor | Milestone: | VLO-3.3 |
| Component: | VLO web app | Version: | |
| Keywords: | Cc: | eric.auer@mpi.nl, teckart@informatik.uni-leipzig.de |
Description
The admins at MPI that perform the VLO deployments complained that the packaged VloConfig.xml has values that are not correct for the production or staging environment and therefore need to be adjusted on each deploy.
We could make the deployment process easier and less error-prone by applying Maven resource filtering to this file and define build profiles for the various environments (local development, alpha, beta, production, ...).
Some properties that may differ per environment:
- dataRoots
- solrUrl
- homeUrl
- helpUrl
- maxDaysInSolr
- deleteAllFirst
Change History (5)
comment:1 Changed 9 years ago by
| Cc: | teckart@informatik.uni-leipzig.de added |
|---|
comment:2 Changed 9 years ago by
| Milestone: | → VLO-3.2 |
|---|---|
| Priority: | major → minor |
comment:3 Changed 9 years ago by
| Milestone: | VLO-3.2 → VLO-3.3 |
|---|
comment:4 Changed 9 years ago by
| Owner: | set to Twan Goosen |
|---|---|
| Status: | new → assigned |
Note: See
TracTickets for help on using
tickets.
Moved a number of existing VLO tickets to 3.3 milestone