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:,


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 DefaultCC Plugin

Cc: added

comment:2 Changed 9 years ago by Twan Goosen

Milestone: VLO-3.2
Priority: majorminor

comment:3 Changed 9 years ago by Twan Goosen

Milestone: VLO-3.2VLO-3.3

Moved a number of existing VLO tickets to 3.3 milestone

comment:4 Changed 9 years ago by Twan Goosen

Owner: set to Twan Goosen
Status: newassigned

comment:5 Changed 9 years ago by Twan Goosen

Resolution: fixed
Status: assignedclosed

Fixed in [6408:6409]

Note: See TracTickets for help on using tickets.