Introduction to the configuration of using Consul to manage Laravel projects

I have been running in the pre-production environment for more than a year, so I will record and share it here.

Problems & Other Solutions

When we need to deploy multiple different projects on multiple servers, we need a centralized configuration information management and synchronization Tool of. The solutions that have been considered are:

1. Synchronize with rsync.env Files: The configuration of multiple projects is a bit cumbersome, and you need to ssh to the server to modify and then synchronize

2. Use Docker: Cluster deployment is more convenient. You can use the graphical interface to modify environment variables, but updating environment variables requires restarting the container. Most projects have not been migrated to Docker

Let’s take a look at the solution of Consul Consul Template.

Installation

Both Consul and Consul Template provide precompiled executable files, which can be downloaded and decompressed.

Start Consul:

consul agent -server -bootstrap -ui -bind <ip>

Other service nodes can join the cluster through consul agent -join <ip>.

After startup, manage Consul through consul commands, RESTful API, and Web UI.

Consul KV

Consul provides a distributed key-value pair storage that can be used to store dynamic configuration information of applications. Basic operations:

# put 设置一个KV对
consul kv put APP_DEBUG false

# get 获取
consul kv get APP_DEBUG

# exprot 导出JSON
consul kv export > data.json

# import 导入JSON
consul kv import @data.json

# delete 删除
consul kv delete APP_DEBUG

Consul KV support directory , can be achieved by separating keys with /. For example, we use a directory like configs/<app_name>/ to store all configurations of a project.

Consul Template

The configuration is centrally managed, how to pass it to Laravel? One method is to use Consul's API in Laravel to obtain configuration information. The second method is to monitor KV changes externally and write them to the .env file. Consul Template is such an external tool.

The configuration template we use (.env.tpl):

{{ range ls "configs/crm" }}
{{ .Key }}={{ .Value }}{{ end }}

means traversing the config/crm KV directory and generating key=valueFormat.

Run:

## 格式： 模板文件:目标文件:更新后执行的命令
consul-template --template \
    /path/to/.env.tpl:/path/to/.env:'php /path/to/artisan config:cache'

You can generate the .env file and continue to monitor changes. A consul-template instance can have multiple --template multiple parameters, which can be used for multiple parameters on one server. Generate configuration files for each project.

The above is the entire content of this article. I hope it will be helpful to everyone's study. For more related content, please pay attention to the PHP Chinese website!

Related recommendations:

Interpretation of Laravel Service Container (IocContainer)

##Laravel User Authentication System (Basic Introduction)

Laravel WeChat applet obtains user details and analysis of applet code expansion with parameters

The above is the detailed content of Introduction to the configuration of using Consul to manage Laravel projects. For more information, please follow other related articles on the PHP Chinese website!