Need help with openpaas-esn?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

415 Stars 130 Forks Other 12.8K Commits 3 Opened issues


Open PaaS Enterprise Social Network

Services available


Need anything else?

Contributors list


OpenPaaS is your next collaboration platform, for enterprises & organizations.


Try it in docker

Discover the OpenPaaS platform on your machine within 5 minutes by checking out the demo docker-compose recipe.

Install it on your server

Check out the installation guide to install OpenPaaS on a Linux server and start using it now! If you're a developer looking for a development setup, head to the next section:

Improve it with us

Developers are more than welcome to help build OpenPaaS! To get your development environement up & running, see our developers installation documentation.

Once you are ready to go, you can explore the project's documentation site and this repository's documentation. If you have any question, don't hesitate to come and ask on the forum!

Our CI

We are currently using Gitlab CI.
Hence, you can have a look at the

file on the root of this repository for more information.

However, some jobs are more complicated than expected, as they are depending on external tools.
Hopefully for you, such jobs are the latest in the pipeline execution; linters, build & tests jobs are simple.
The "complexe" jobs are those dedicated to CD (Continuous Delivery) which main reason is that we are delivering Docker images to two different registries.

The main complexity is about

branches & their related delivery, the following matrix might help you:

| Branch name | Internal registry | DockerHub | | ----------- | ----------------- | --------- | |

| openpaas-snapshots/openpaas-esn:branch-master | linagora/esn:branch-master | |
(1) | openpaas-snapshots/openpaas-esn:* | linagora/esn:branch-* | |
(2) | openpaas-snapshots/openpaas-esn:* | linagora/esn:* |

(1) The goal of release branches is to be able to maintain release (bug fix backport, CVE fixes...), and then produce minor releases based on this major release.
They should be prefixed by

. e.g.
branch name
build will deliver: - openpaas-snapshots/openpaas-esn:1.6 - openpaas-snapshots/openpaas-esn:1.6.3 (depending on the minor release) - linagora/esn:branch-1.6.3

(2) Feature branches are not release. They are used in order to publish & validate features (maybe several MRs & commits). They should be prefixed by

. e.b.
branch name
build will deliver: - openpaas-snapshots/openpaas-esn:feature-friday-delivery - linagora/esn:feature-friday-delivery


Affero GPL v3

Special thanks


BrowserStack for supporting open source projects.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.