Page MenuHomePhorge
Files F117756470

README.md
No OneTemporary
Actions

Authored By
Unknown
Size
2 KB
Referenced Files
None
Subscribers
None

README.md
View Options

## Quickstart Instructions to try it out
* Make sure you have docker and docker-compose available.
* Change to the base directory of this repository.
* Run 'HOST=kolab.local ADMIN_PASSWORD="simple123" bin/configure.sh config.prod' to configure this deployment.
* Run 'env ADMIN_PASSWORD="simple123" bin/deploy.sh' to start the deployment.
* Add an /etc/hosts entry "127.0.0.1 kolab.local"
* navigate to https://kolab.local
* login as "admin@kolab.local" with password "simple123" (or whatever you have set), and create your users.
# Customization
To customize the installation, copy config.prod and adjust to your liking. You can then install the configuration using 'bin/configure.sh $YOURCONFIG',
and afterwards 'bin/deploy.sh' again.
Please note that bin/deploy.sh will remove any existing data.
## Alternative configurations
Everything but config.prod is for development or demo purposes:
* config.prod: A docker environment with just an admin account prepared. A starting point for a production environment.
* config.demo: A docker environment with demo data included.
* config.docker-dev: A development environment with everything running in docker. Includes a cyrus-murder. Don't use unless you know what you're doing.
* config.host-dev: Run only dependencies in docker with ports exposed, and expect kolab4 to be run locally. Don't use unless you know what you're doing.
* config.legacy: A docker environment that includes ldap and other legacy components. Don't use unless you know what you're doing.
# Use the ansible setup
The ansible/ directory contains setup scripts to setup a fresh Fedora system with a kolab deployment.
Modify the Makefile with the required variables and then execute `make setup`.
This will configure the remote system and execute the above steps.
### Update
To update the containers without removing the data:
* git pull
* Run "bin/update.sh"
### Backup / Restore
The "bin/backup.sh" script will stop all containers, snapshot the volumes to the backup/ directory, and restart the containers.
"bin/restore.sh" will stop all containers, restore the volumes from tarballs in the backup/ directory, and restart the containers.
### Requirements
* docker
* openssl

File Metadata

Mime Type
text/plain
Expires
Sat, Apr 4, 8:42 AM (2 w, 4 d ago)
Storage Engine
local-disk
Storage Format
Raw Data
Storage Handle
6b/30/f4f17340cb39b85b27dbc2f3121f
Default Alt Text
README.md (2 KB)

Event Timeline