mattermost

[vigeeking]

I am trying to communicate with people via different messaging platforms. I would like to have built in slack functionality to handle communication, and also be able to integrate it into the smart house. This is done when I have a slack/mattermost platform integrated into the pipeline and have gotten my first other person added to the server.

[vigeeking]

I am starting this project using azure. This will be a point of disconnect between online identities, as this uses an old account. From here on out I will use new, but be aware.

[vigeeking]

Going to set it up using these instructions: https://docs.mattermost.com/install/prod-docker.html?src=dl, specifically: sudo apt-get install git git clone https://github.com/mattermost/mattermost-docker.git cd mattermost-docker docker-compose build mkdir -pv ./volumes/app/mattermost/{data,logs,config,plugins,client-plugins} sudo chown -R 2000:2000 ./volumes/app/mattermost/ docker-compose up -d

[vigeeking]

Note to self: I started working on using docker-compose to run this, and made some good headway with the shell scripting, so plan to link back up with that in the feature/mattermost branch. But to start I'm going to go 100% their method.

[vigeeking]

ran into a problem with the permissions, here is the link with the solution: https://github.com/docker/compose/issues/2781

the solution likely lies here: mkdir -p ./volumes/app/mattermost/{data,logs,config,plugins} chown -R 2000:2000 ./volumes/app/mattermost/ docker-compose start

[vigeeking]

note to self, next time check docker hub: https://hub.docker.com/r/mattermost/mattermost-team-edition

[vigeeking]

I believe docker-compose can be effectively "overloaded" you just need to keep the path relative to the first instance of docker-compose: https://docs.docker.com/compose/extends/#/understanding-multiple-compose-files

[vigeeking]

Issue above was because the db, web, and app directories had not been created. I should have known this, and I now understand more about volumes.

[vigeeking]

Ran into an issue with docker-compose not being created. It seems likely that it is related to the context path now being nested. I started to change multiple context entries in the docker-compose.yaml file, before realizing this would be better handled as templates. This led to a long discussion, but ultimately resulted in this from Justin: " You should be able to use a .env file to define environment variables: https://docs.docker.com/compose/env-file/ Those you can use as variables in your compose file: https://docs.docker.com/compose/environment-variables/#substitute-environment-variables-in-compose-files Depending on how you want to use them."

[vigeeking]

Was able to get docker compose to run after starting in a greenfield deployment. The containers built, but kept crashing. This may be a fix Hi,

Found this for solving the chmod issue: http://stackoverflow.com/questions/24288616/permission-denied-on-accessing-host-directory-in-docker

Check here too for the selinux security issue : https://docs.docker.com/engine/tutorials/dockervolumes/#/volume-labels

I fixed my docker-compose file by adding a :z at the end of the volume command volumes: - /media/dataDemo/db:/var/lib/postgresql/data:z

Hope it will help.

from: https://github.com/docker-library/postgres/issues/116

[vigeeking]

Justin:
those volume permissions issues you are experiencing is a big reason why named volumes exist.

[vigeeking]

Mattermost is now up and running on amazon at http://ec2-18-219-52-207.us-east-2.compute.amazonaws.com/, with minimal configuration. I am going to see about the best way to deploy the mattermost server, and will now treat that as prod. Once I have mattermost up and running in such a way that I don't have to re-create the password every time, and I can point my domain at the instance, I will invite others.

[vigeeking]

This has now become issue#64

[vigeeking]

This has been accomplished though the requirements changed. I am deploying mattermost via bitnami.