plenex.blogg.se

MM_GITLABSETTINGS_TOKENENDPOINT= MM_SERVICESETTINGS_LISTENADDRESS=127.0.0.1:8065 MM_PLUGINSETTINGS_DIRECTORY=/var/opt/gitlab/mattermost/plugins SSL_CERT_DIR=/opt/gitlab/embedded/ssl/certs/

PWD=/opt/gitlab/embedded/service/mattermost PATH=/opt/gitlab/bin:/opt/gitlab/embedded/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin Which will output something like this: OLDPWD=/opt/gitlab/sv/mattermost Next, run this command - replacing 12696 with the process ID you found - to find the environment variables: sudo strings /proc/12696/environ Look for the line that ends with config.json to find the process ID: 12696 ? SLsl 0:02 /opt/gitlab/embedded/bin/mattermost -config /var/opt/gitlab/mattermost/config.json To do that, first run ps ax | grep mattermost on the Gitlab server. Since Gitlab configures its Mattermost instance with environment variables, you’ll need to get those from the Mattermost process itself. 3.1 Copy and Modify Configįirst, make a copy of the Mattermost configuration file to make your edits: sudo cp /var/opt/gitlab/mattermost/config.json /tmp/mattermost-config.json If Mattermost is going to be on another server the fastest way to do this is to first set up SSH key-based authentication between the Mattermost server and the Gitlab server. These steps are for moving the data and configuration to a Mattermost instance on the same server. Make sure that you install the enterprise edition so that you can install your license later. Next, install Mattermost Enterprise edition on the other server by following our instructions including setting up Nginx with TLS. Install Mattermost EE on the other server In your gitlab.rb set these values to false: Psql -U mmuser -h 127.0.0.1 -f mattermost_production.sql # on the new Mattermost PostgreSQL server Pg_dump -U gitlab_mattermost -h 127.0.0.1 mattermost_production > mattermost_production.sql If you want to move the Mattermost database to another server as well, export your data from the mattermost_production database using pg_dump, then import it using psql, e.g.: # on the Gitlab server Replace 10.0.2.2 with the IP address of the server that will be hosting the Mattermost 1.2b Export Mattermost Database If want to continue using the Gitlab Omnibus internal PostgreSQL server you’ll need to edit these lines of your gitlab.rb file to allow connections from outside IP addresses. 1.2a Configure PostgreSQL for remote connections If you haven’t already, set up automated backups as well. 1.1 Make a Backupįirst thing to do is backup your Gitlab instance using the instructions here. Then, configure PostgreSQL to listen on the right IP address. Prepare your Gitlab Serverįirst, get your Gitlab server ready by making a backup. You’re ready to upgrade to Mattermost Enterprise Edition but are running Mattermost with Gitlab Omnibus Solution 1.