Mattermost application Cloud Foundry manifest (#278)
This commit is contained in:
parent
8e9facbece
commit
8c6b058e72
20
README.md
20
README.md
@ -73,6 +73,26 @@ If you choose to use MySQL instead of PostgreSQL, you should set a different dat
|
||||
* `MM_SQLSETTINGS_DATASOURCE` : `MM_USERNAME:MM_PASSWORD@tcp(DB_HOST:DB_PORT_NUMBER)/MM_DBNAME?charset=utf8mb4,utf8&readTimeout=30s&writeTimeout=30s`
|
||||
Don't forget to replace all entries (beginning by `MM_` and `DB_`) in `MM_SQLSETTINGS_DATASOURCE` with the real variables values.
|
||||
|
||||
If you want to push Mattermost application to **Cloud Foundry**, use a `manifest.yml` like this one (with external PostgreSQL service):
|
||||
|
||||
```
|
||||
---
|
||||
applications:
|
||||
- name: mattermost
|
||||
docker:
|
||||
image: mattermost/mattermost-prod-app
|
||||
instances: 1
|
||||
memory: 1G
|
||||
disk_quota: 256M
|
||||
env:
|
||||
DB_HOST: database host address
|
||||
DB_PORT_NUMBER: database port
|
||||
MM_DBNAME: database name
|
||||
MM_USERNAME: database username
|
||||
MM_PASSWORD: database password
|
||||
|
||||
```
|
||||
|
||||
### Web server container
|
||||
This image is optional, you should **not** use it when you have your own reverse-proxy. It is a simple front Web server for the Mattermost app container. If you use the provided `docker-compose.yml` file, you don't have to configure anything. But if your application container is reachable on custom host and/or port (eg. if you use a container provider), you should add those two environment variables :
|
||||
* `APP_HOST`: application host address
|
||||
|
Reference in New Issue
Block a user