Deploy a portal to production

Note

For all commands in this section, $INFRA_DIR must point to the proper infrastructure directory you want to deploy.

Initializing infrastructure

If the infrastructure was never deployed before, you must initialize it. To do that, you must clone search.d and vhosts.d in customer-infra/prod/:

  1. Ask your system administrator to create the relevant bare repositories. Point it to the correct section of the system administrator documentation if needed.
  2. Use in geo-infra:
  • manuel init-prod-repo search
  • manuel init-prod-repo vhosts.d
  1. Generate and deploy the global search configuration: manuel deploy-global-search-conf. At this point, the restart will fail on the server.

Deploying a new portal

  1. Generate the vhost for this portal: manuel vhost prod <portal>
  2. Deploy the vhosts on the server: manuel deploy-vhost
  3. Ask your system administrator to create the bare repository for the new portal. Point to the correct section of the system administrator documentation if needed.
  4. Create to proper symlink to MapServer at the location defined by vhost.ows_path
  5. Initialize this repository with manuel init-prod-repo <portal>
  6. Build and deploy the portal: manuel deploy <portal>

Deploying existing portals

Use manuel deploy PORTAL1 PORTAL2 .

If the vhosts require an update:

  1. Generate them for the concerned portals: manuel vhost prod PORTAL1 PORTAL2
  2. Deploy them to the server: manuel deploy-vhost

API

If the API need to be updated on production, ask your system administrator to do it. You can send the link the relevant section of the documentation.

Revert

If you have a problem after a deploy on a portal, you can revert to the previous version with manuel revert PORTAL.