Hypernode offers a staging environment so it can be used as a sandbox for your Akeneo PIM project.
Please keep in mind that your staging environment for Akeneo shares resources (disk, CPU, mem) with your production environment. It’s also possible to order a development plan instead, so your production environment will not be affected. Once again a big thank you to our partner Experius for contributing to this article!

Update managed_vhosts

Update the current managed_vhost with staging port

Split the nginx configuration for production and staging

Edit staging.akeneo.conf and change to:

Setup the staging environment and web symlink

Duplicate the akeneo_pim database to staging_akeneo_pim

Change the staging Akeneo parameters

Edit ~/akeneo-staging/akeneo/pim-community-standard/app/config/parameters.yml and change the following:
– change database_name from akeneo_pim to staging_akeneo_pim
– update the Elasticsearch index names by adding a staging prefix for example: akeneo_pim_product > staging_akeneo_pim_product

Don’t forget configs like the temp upload directory, please update accordingly.

Reindex Elasticsearch

Configure a cronjob for staging

Tada! The staging is now up and running on https://akeneo.example.hypernode.io:8443