![]() ![]() Log in to each VPS via SSH as user root ssh -p Port_number Step 2: Update all packages and install Development tools Step 1: Log in via SSH on the CentOS server: GraphicsMagick – a robust collection of tools and libraries about image processing. NodeJS – an open source JavaScript run-time environment. MongoDB – most popular open source NoSQL database In order to run Rocket.Chat on your CentOS 7 VPS, we need the following requirements pre-installed: Rocket.Chat supports audio and video communication with screen sharing, with complete access to the source code, you can fully customize, extend or add new functionality to meet your requirements. The Installation of Rocket.Chat on CentOS 7 is fairly easy task and it shouldn’t take more then 10 minutes to complete. Rocket.Chat is unlimited and open source software solution that replaces Slack and HipChat. Rocket.Chat is a free team communication software, built with Meteor framework. I was wondering if it’s something from the nginx containers side but after adding the nf snippets suppiled in the egroupware-collabora and egroupware-rocket the nginx container doesn’t start.In this article we will show you how to install Rocket.Chat on a CentOS 7 server and configure Apache as reverse proxy for the Rocket.Chat application. #- WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PASSWORD="secret" #- WATCHTOWER_NOTIFICATION_EMAIL_SERVER_PORT=25 #- WATCHTOWER_NOTIFICATION_EMAIL_SERVER=“ ” # if you give your MX here, you need no user/password #- WATCHTOWER_NOTIFICATIONS_LEVEL=info # possible values: panic, fatal, error, warn, info or debug # for email notifications add your email and mail-server here WATCHTOWER_CLEANUP=true # delete old image after update to not fill up the disk root/.docker/config.json:/config.json:ro var/run/docker.sock:/var/run/docker.sock #DB# container_name: egroupware-db automatic updates of all containers daily at 4am see for more information Restart: always run an own MariaDB:10.4 (you can use EGroupware’s database backup and restore to add your existing database) # if no webserver is running on the host, change (first) number to 80 or 443 ![]() # AND uncomment the three lines starting with “listen 443”, “ssl_certificate”, “ssl_certificate_key” in nf certificate.pem:/etc/ssl/private/certificate.pem # to add a certificate create a certificate.pem containing (in that order) # can access Rocket.Chat or Collabora without the need to go over your firewall # set the ip-address of your docker host AND your official DNS name so EGroupware ![]() # alternativly you can specify an already existing database with full right by the given user! # a database “egroupware” with a random password is created for you on installation (password is stored in in data directory) # for internal db service you should to specify a root password here AND in db service # MariaDB/MySQL host to use: for internal service use “db”, for host database (socket bind-mounted into container) use “localhost” ![]() #- /etc/egroupware-docker/private-ca.crt:/usr/local/share/ca-certificates/private-ca.crt:ro # private CA so egroupware can validate your certificate to talk to Collabora or Rocket.Chat var/run/mysqld/mysqld.sock:/var/run/mysqld/mysqld.sock # - Debian/Ubuntu /var/run/mysqld/mysqld.sock # - openSUSE/SLE /var/run/mysql/mysql.sock # - RHEL/CentOS /var/lib/mysql/mysql.sock uncomment the next line and modify the host path, it depends on your distro: comment out the whole db service below AND # extra-sources rsync from entry-point into sources # setting a default language for a new installation # location of deprecated EGroupware packages like Wiki, SiteMgr, KnowledgeBase #device: $PWD/data extra sources with apps not part of egroupware container # otherwise data is stored in data subdirectory of the current directory # data directory /var/lib/egroupware AND the host database see below # to upgrade an existing non-docker installation most easy is to use the existing I’m using docker-compose to run all the containers, here is my egroupware yaml `version: '3’ All the containers are running, I can access the eGroupware page but when I try to access the rocket chat ip I get “Unknown path” and when I try to access collabora I get a blank page with “ok”. My problem is that I cannot access collabora and rocket.chat. Hi, I’ve been given the task of installing the 19.1 version of eGroupware on localhost for testing purposes before we migrate our current installation to docker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |