Public Repository

Last pushed: 5 months ago
Short Description
Kezmo is an enterprise chat, and task management tool for teams.
Full Description

Quick reference

What is Kezmo?

Kezmo is an enterprise chat and collaboration tool to help teams get things done. It’s an email alternative for secure team communication. It can be used both internally to manage projects, and externally to manage the relationship with customers and contractors.

Provide context by creating different collaboration spaces for different topics. Grant access only to those that need to be kept in the loop of things, as collaborators, or just readers.

Go from agile conversations to structured agreements. Create tasks, raise issues, run polls, and store notes without leaving the chat experience.

Features

  • Real Time Messaging: Enable a rich chat experience in your team. Control who’s received and read your messages.Transition from unstructured conversations to structured actionable content. Transform chat messages to task items, issues, contacts, notes with a click.
  • File Sharing: Share files and images across platforms.
  • Task Management: Assign tasks and control who’s doing what in your team.
  • Secure: Take control of your organization’s data. Use our servers in the cloud, or setup your own server on your premises.
  • Localized: Make it easier for your teams abroad to adopt the app by providing a user experience in their native language.

How to use this image

Installation

In order to install the Community Edition of Kezmo on your premises you must have a local installation of Docker in your server. Once you have the Docker environment ready, you can install Kezmo by running the following command:

docker run -it --name kctr -p 8080:8080 kezmo/ce --init

The image will prompt you for required information to set up the installation's administrator account, and smtp email configuration required to enable emails messages, used by many features (sign up, password reset, notifications, etc).

Once you enter all the required information you can start using Kezmo just by opening a browser and navigating to:

http://localhost:8080/web/

Image Information

The initial docker command will run the 'kezmo/ce' image inside a container named 'kctr' and forwards the exposed port 8080 on the container to port 8080 on the host machine. Notice we use the --init flag to execute the database initialization process which will prompt for the main user data such as email and password. The use of this flag will cause the database to be dropped if it exists. Database can be accessed fowarding exposed port 5432.

To exit the interactive Docker session without stopping the container you can daemonize the container typing ctrl+p and ctrl+q after each other which keeps the container running but frees up your terminal. You can attach to it later using docker attach, if you need to interact with the container more. To run the container directly in the background, start it in detached mode with -d.

Once it runs, you can execute other commands in the same container with exec, such as:

docker exec -ti kctr bash

The above will start a bash session in the same container, which is great for taking a look around if you need to and perform one-off maintenance tasks.

Persistance

For data persistence a volume should be mounted at /var/lib/postgresql (db data) and /srv/kezmo-ce (local storage).

SELinux users are also required to change the security context of the mount point so that it plays nicely with selinux.

mkdir -p /to/path/data
sudo chcon -Rt svirt_sandbox_file_t /to/path/data

The updated run command looks like this.

docker run -it --name kctr -p 8080:8080 -v /host/to/path/data:/var/lib/postgresql -v /host/to/path/data:/srv/kezmo-ce kezmo/ce --init

This will make sure that the data stored in the database and user files are not lost when the container is stopped and started again.

Enviromental Variables

The following environment variables are also honored for configuring your KezmoCE instance. They can be set during run using '-e' option. Otherwise will be prompted during initialization.

-e SNOWFLAKE_HOST_IP=... (Defaults to localhost)
-e SNOWFLAKE_HOST_PORT =... (Defaults to 8080)

SMTP configuration variables for outgoing emails:

-e SNOWFLAKE_EMAIL_FROM=...  
-e SNOWFLAKE_SMTP_USERNAME=...
-e SNOWFLAKE_SMTP_PASSWORD=...
-e SNOWFLAKE_SMTP_HOST=...
-e SNOWFLAKE_SMTP_PORT=...
-e SNOWFLAKE_SMTP_USE_TLS=...

Access

Finally, access it via http://localhost:8080/web/ and experience infinite pleasure.

Restrictions

  • Up to 50 registered users.
  • No search.
  • No bots.
  • No online support.
  • One group visibility. Every user sees all other users.
  • Single server deployment without escalation capabilities.
  • Lack of integrations with Facebook, Google Calendar, Google Drive, Dropbox.

License

View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

Docker Pull Command
Owner
kezmo