I’m currently evaluating if we should use Neos as CMS for a project.
But I’m currently sceptical on the deployment/installation process.
Maybe someone could provide further details and insights on the best practices.
I wan’t to package a certain installation and promote it from QA to PROD by adapting configuration.
(without having to perform any external calls)
This would also enable a fast recovery in case of an outage --> as we can quickly provision the server based on a known state.
- Is there a way to install Neos without composer?
- How can I package a installation done with composer and how can I adapt the configuration?
- In order to achieve high availability is there any best practice how I can run two Neos installations behind a load balancer --> do I need to care about the session management or is it sufficient to have a shared DB?
- Does Neos store any data on the local disc if the users maintain the site content or is everything stored in the DB?
Thanks for the input