2017-03-02 12:23:23 +02:00
# Install mailcow
2017-03-02 23:27:46 +02:00
You need Docker and Docker Compose.
2017-03-02 12:23:23 +02:00
2017-03-02 23:27:46 +02:00
1\. Learn how to install [Docker ](https://docs.docker.com/engine/installation/linux/ ) and [Docker Compose ](https://docs.docker.com/compose/install/ ).
2017-03-02 12:23:23 +02:00
2017-03-06 16:43:13 +02:00
Quick installation for most operation systems:
- Docker
```
curl -sSL https://get.docker.com/ | sh
```
- Docker-Compose
```
curl -L https://github.com/docker/compose/releases/download/$(curl -Ls https://www.servercow.de/docker-compose/latest.php)/docker-compose-$(uname -s)-$(uname -m) > /usr/local/bin/docker-compose
chmod +x /usr/local/bin/docker-compose
```
2017-03-03 04:56:11 +02:00
Please use the latest Docker engine available and do not use the engine that ships with your distros repository.
2017-03-02 23:27:46 +02:00
2\. Clone the master branch of the repository
```
git clone https://github.com/andryyy/mailcow-dockerized & & cd mailcow-dockerized
```
2017-03-02 22:43:08 +02:00
2017-03-02 23:27:46 +02:00
3\. Generate a configuration file. Use a FQDN (`host.domain.tld`) as hostname when asked.
```
./generate_config.sh
```
2017-03-02 12:23:23 +02:00
2017-03-02 23:27:46 +02:00
4\. Change configuration if you want or need to.
```
nano mailcow.conf
```
2017-03-02 21:11:48 +02:00
If you plan to use a reverse proxy, you can, for example, bind HTTPS to 127.0.0.1 on port 8443 and HTTP to 127.0.0.1 on port 8080.
2017-03-05 14:41:41 +02:00
5\. Run the composer file. It will pull images and build containers.
2017-03-02 23:27:46 +02:00
```
docker-compose up -d
```
2017-03-02 21:11:48 +02:00
Done!
2017-03-02 12:23:23 +02:00
You can now access **https://${MAILCOW_HOSTNAME}** with the default credentials `admin` + password `moohoo` .
The database will be initialized right after a connection to MySQL can be established.
# Update mailcow
2017-03-05 14:41:41 +02:00
There is no update routine. You need to refresh your pulled repository clone and apply your local changes (if any). Actually there are many ways to merge local changes. Here is one to
2017-03-06 11:54:09 +02:00
stash all local changes, pull changes from the remote master branch and apply your stash on top of it. You will most likely see warnings about non-commited changes; you can ignore them:
2017-03-02 12:23:23 +02:00
```
2017-03-05 14:51:56 +02:00
# Stash local changes
2017-03-05 14:41:41 +02:00
git stash
2017-03-05 14:51:56 +02:00
# Re-pull master
2017-03-05 14:41:41 +02:00
git pull
2017-03-05 14:51:56 +02:00
# Apply stash and remove it
2017-03-05 14:41:41 +02:00
git stash pop
2017-03-02 12:23:23 +02:00
```
2017-03-05 14:41:41 +02:00
Pull new images (if any) and recreate changed containers:
2017-03-02 12:23:23 +02:00
```
docker-compose pull
docker-compose up -d --remove-orphans
```
2017-03-06 11:54:09 +02:00
Clean-up dangling (unused) images and volumes:
```
docker rmi -f $(docker images -f "dangling=true" -q)
docker volume rm $(docker volume ls -qf dangling=true)
2017-03-06 16:43:13 +02:00
```