Shulou(Shulou.com)06/01 Report--

How Discourse is deployed on Rainbond, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain for you in detail, people with this need can come to learn, I hope you can gain something.

An overview of the deployment of the open source community Discourse on Rainbond

Discourse is a completely open source forum platform. It has a rich plug-in library and theme library, which is suitable for the construction of open source community. The official community of Rainbond is an actual case based on Discourse.

Discourse has been used since the establishment of the Rainbond official community, when the version was 1.5.4. Times have changed, and for a better community experience, the Rainbond Community Operations team decided to deploy the latest version of the Discourse community and migrate data from the original community to the new community.

The editor will describe in detail how to deploy Discourse on the Rainbond container cloud platform, as well as the holes that have been leveled during the whole deployment and even data migration process. It will be of great help to small partners who are interested in building a Discourse-based community.

Rapid installation based on application market

Discourse has been released to the Rainbond application market and can be deployed and installed at the click of a button.

Click install, select App and wait for a moment to access your Discourse.

Be sure to modify the following environment variables before formal use:

Environment variables:

DISCOURSE_DB_PASSWORD= your custom database password

Email address of the DISCOURSE_DEVELOPER_EMAILS= administrator

The domain name prepared by DISCOURSE_HOSTNAME= for the community. If you want to use the domain name generated by Rainbond at port 80 by default, this value is set to ${DOMAIN}.

Smtp servers available for DISCOURSE_SMTP_ADDRESS=

Port of the DISCOURSE_SMTP_PORT=smtp server

DISCOURSE_SMTP_USER_NAME=smtp account

The password of the DISCOURSE_SMTP_PASSWORD=smtp account

After the modification is completed, you can continue to register for use.

How to make Discourse Application

When using the old version of Discourse, we did a lot of work to containerize it. However, in the current version, Discourse has officially supported and mainframe deployment, which is very friendly for deploying Discourse on the Rainbond container cloud platform.

In the next section, I will show you how to make a Discourse application that is ready to use.

Get the image

The first step in deployment is to get an image of Discourse.

Different from the general containerized deployment, Discourse does not host its own image on Docker Hub, but prepares a complete set of tools for users to highly customize the images they need, which is discourse_docker. In this set of tools, users can customize the deployment method, plug-ins and other information provided by the template, and quickly build the corresponding image through a command; you can also use it to manage the Discourse of the local running docker deployment.

The Discourse deployment supports the Standalone pattern for all in one, as well as the Multiple pattern for production. The Multiple pattern means to separate the WEB part of Discourse from the back-end database Postgresql and cache middleware Redis.

Multiple mode will be used in this deployment. The final topology will be as follows:

The requirements of the environment first, we need an environment that can run docker services, if you have installed the Rainbond container cloud platform, then any node in the cluster can meet your needs. If you haven't installed Rainbond yet, or you don't know what it is, you need to click to find out.

Get discourse_docker

Git clone https://github.com/discourse/discourse_docker.git

Configure templates in the root directory of the project, under the directory named samples, there will be the template files we need, web_only.yml data.yml. Copy these two template files to the containers directory under the root directory of the project.

The main customizations of the custom configuration Discourse are themes (theme) and plug-ins (plugins), where themes can be configured in the website settings, and plug-in installation requires modification of the above template file.

Edit the web_only.yml file, find the following paragraph near line 84, and append the plug-in address:

Hooks: after_code:-exec: cd: $home/plugins cmd:-git clone https://github.com/discourse/docker_manager.git-git clone https://github.com/discourse/discourse-whos-online.git

For specific principles and operations, click to learn more.

Other standard configurations, such as the configuration of the mail server, are specified in the form of environment variables, which can be kept by default and can be replaced by custom environment variables when deployed in Rainbond.

Instructions on the configuration of Discourse environment variables

About how Rainbond customizes environment variables

To build the WEB service image, use the command line tool launcher to build the web_only image:

. / launcher bootstrap web_only

After the construction is completed, the corresponding image will appear in the list of local images on the server:

Root@localhost:~/discourse_docker# docker images | grep web_onlylocal_discourse/web_only latest 79a99d0d8fd1 7 days ago 2.83GB

Just push this image to Docker hub or a private image repository for backup. In my deployment environment, I pushed it to Docker hub. The specific image address is: rainbond/discourse_web:2.4.0-beta8.

Build database mirroring

Use command line tools to build data images

. / launcher bootstrap data

After the construction is completed, the corresponding image will appear in the list of local images on the server:

Root@iZj6chkije5xk0gfyvcrzyZ:~/discourse_docker# docker images | grep datalocal_discourse/data latest 76e100480749 2 weeks ago 2.35GB

The image does not need to be pushed to the image repository. The next steps will continue to split the image and automatically initialize the data.

The currently built data image is an image that combines postgresql and redis. This is not in line with the way we want to deploy, and I'm going to split it further.

I decided to use an official image to run postgresql and redis. The postgresql is then processed so that it can be initialized automatically.

Redis deployment

This step is relatively simple. You can deploy a standard redis directly based on the image:

Postgresql deployment

Further processing is made based on the official postgresql image so that the database required by Discourse can be initialized automatically.

The deployment method uses a Dockerfile-based source build, project address: https://github.com/dazuimao1990/pri-postgresql

The key parts of Dockerfile are parsed:

In the following steps of FROM postgres:10-alpineMAINTAINER guox@goodrain.com#, the sql script used to initialize the data is placed in the specified directory ADD sql/*.sql / docker-entrypoint-initdb.d/ADD docker-entrypoint.sh / RUN chmod + x / docker-entrypoint.shENV TZ Aisa/ShanghaiENV LANG en_US.utf8ENV PGDATA / var/lib/postgresql/dataENV PG_MAJOR 10ENV PG_VERSION 10.11VOLUME / var/lib/postgresql/dataEXPOSE 5432

For the principle of automatic initialization, see the Initialization scripts section of https://hub.docker.com/_/postgres. Most docker-based databases support automatic initialization in this way. the advantage of this is that the container based on this image will automatically execute a sql script to complete the initialization when it starts for the first time. For Rainbond deployment, after such a database is released to the application market as part of the application, performing an one-click installation can achieve the effect of instant use.

Another focus of this step is how to get the sql script for initialization. This needs to take advantage of the database mirroring built in the previous step.

Start this image as a container:

. / launcher start data

At this point, an initialized data container will be launched. We need to back up the database discourse in it.

Docker exec-ti data bashpg_dump-d discourse-h 127.0.0.1-U discourse > data.sqlpg_dump-d discourse-h 127.0.0.1-U discourse > / shared/data.sql

After entering the password, you can start the backup. After the backup is completed, find the corresponding data.sql file in the / var/discourse/shared/data/ directory of the server.

A minor problem was found when the official image was initialized with data.sql. The official image did not create a role:postgres by default, so the following was manually added before the data.sql:

-This row is added manually because when the SQL is imported manually, recived role "postgres" does not exist-- CREATE USER postgres SUPERUSER

When you are ready, you can deploy the customized postgresql in Rainbond

Before building, you need to define advanced settings:

Component deployment type: stateful service

Environment variables:

POSTGRES_DB=discourse

Database password customized by POSTGRES_PASSWORD=

POSTGRES_USER=discourse

Deploy Discourse_web

Use the rainbond/discourse_web:2.4.0-beta8 image we have pushed to deploy the WEB service part.

Before clicking build, make advanced settings:

Environment variables:

DISCOURSE_DB_HOST=127.0.0.1

DISCOURSE_DB_PASSWORD= your custom database password

DISCOURSE_DB_USERNAME=discourse

Email address of the DISCOURSE_DEVELOPER_EMAILS= administrator

The domain name prepared by DISCOURSE_HOSTNAME= for the community. If you want to use the domain name generated by Rainbond at port 80 by default, this value is set to ${DOMAIN}.

DISCOURSE_REDIS_HOST=127.0.0.1

Smtp servers available for DISCOURSE_SMTP_ADDRESS=

Port of the DISCOURSE_SMTP_PORT=smtp server

DISCOURSE_SMTP_USER_NAME=smtp account

The password of the DISCOURSE_SMTP_PASSWORD=smtp account

Establish dependence

Using the Rainbond dependency relationship, the correct dependency relationship of the three services is established.

Discourse_web depends on postgresql10

Discourse_web depends on redis

Visit

Visit the domain name corresponding to port 80 of discourse_web and see the welcome page to prove that the system deployment is complete.

Some cramped email configurations

When Discourse initializes the installation, a registration email will be sent to the administrator's mailbox, so the correct configuration of mail service is a top priority. For more information on the official recommended mail server and configuration method, please see:

Https://github.com/discourse/discourse/blob/master/docs/INSTALL-email.md

Data recovery

If you are an old version user like me, it will be necessary to import the old version of data into the new version of Discourse. Discourse supports backup and recovery of site-wide data, but I encountered a lot of problems in the actual recovery process, the reason is that my old version is too old.

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.