Installation for production¶
An installation use these services, which are deployed using docker containers:
- a php-fpm image, which run the Php and Symfony code for Chill;
- a nginx image, which serves the assets, and usually proxy the php requests to the fpm image;
- a redis server, which stores the cache, sessions (this is currently hardcoded in the php image), and some useful keys (like wopi locks);
- a postgresql database. The use of postgresql is mandatory;
- a relatorio service, which transform odt templates to full documents (replacing the placeholders);
Some external services:
- (required) an openstack object store, configured with temporary url <https://docs.openstack.org/swift/latest/api/temporary_url_middleware.html> configured (no openstack users is required). This is currently the only way to store documents from chill;
- a mailer service (SMTP)
- (optional) a service for verifying phone number. Currently, only Twilio is possible;
- (optional) a service for sending Short Messages (SMS). Currently, only Ovh is possible;
The docker-compose.yaml file of chill app is a basis for a production install. The environment variable in the
`.env.prod` should be overriden by environment variables, or
This should be adapted to your needs:
The image for php and nginx apps are pre-compiled images, with the default configuration and bundle. If they do not fullfill your needs, you should compile your own images.
Think about how you will backup your database. Some adminsys find easier to store database outside of docker, which might be easier to administrate or replicate.
chill:cron-job:execute should be executed every 15 minutes (more or less).
This command should never be executed concurrently. It should be not have more than one process for a single instance.
Tweak symfony messenger¶
Calendar sync is processed using symfony messenger.
You can tweak the configuration
- Configure the saml login and synchronisation with Outlook api