我已经完成了一个使用 Ruby on Rails 构建的应用程序。现在我想将其托管在 AWS 上的 EC2 实例上。
我已经为其配置了服务器，并且正在使用pumaHTTP服务器作为应用服务器。在生产中启动应用程序总是需要我运行RAILS_ENV=production rails s这通常不太方便，因为应用程序启动时它不会返回提示。
我还希望能够使用systemd来管理Puma，这样我就可以轻松地start, stop, check status and restart通过运行一行命令来连接 puma 服务器。
我在网上尝试了很多解决方案，但是当我尝试启动服务器时经常出现错误：
● puma.service - Puma HTTP Forking Server
Loaded: error (Reason: Exec format error)
Active: activating (start) since Mon 2019-12-16 15:33:06 UTC; 59s ago
Cntrl PID: 4473 (bundle)
Tasks: 30 (limit: 4703)
CGroup: /system.slice/puma.service
├─4473 puma 3.12.1 (tcp://0.0.0.0:3000) [my-app]
├─4522 puma: cluster worker 0: 4473 [my-app]
└─4527 puma: cluster worker 1: 4473 [my-app]
Dec 16 15:33:06 ip-172-31-19-238 rbenv[4473]: [4473] * Environment: production
Dec 16 15:33:06 ip-172-31-19-238 rbenv[4473]: [4473] * Process workers: 2
Dec 16 15:33:06 ip-172-31-19-238 rbenv[4473]: [4473] * Preloading application
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] * Listening on tcp://0.0.0.0:3000
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] ! WARNING: Detected 1 Thread(s) started in app boot:
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] ! #<Thread:0x000055f4b08bf7e0@/home/deploy/.rbenv/versions/2.5.0/lib/ruby/gems/2.5.0/gems/a
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] Use Ctrl-C to stop
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] - Worker 0 (pid: 4522) booted, phase: 0
Dec 16 15:33:08 ip-172-31-19-238 rbenv[4473]: [4473] - Worker 1 (pid: 4527) booted, phase: 0
我需要一些帮助。先感谢您。
这是我修复它的方法：
-
Install Puma https://rubygems.org/gems/puma如果尚未安装。
-
运行命令which puma打印你机器上puma服务器的安装目录，一般安装在/home/your-username/.rbenv/shims/puma目录。
-
打开puma.service文件位于/etc/systemd/system/puma.service通过运行以下命令：
sudo nano /etc/systemd/system/puma.service
-
将下面的 Puma 服务配置文件复制到其中并保存。
美洲狮服务配置
[Unit]
Description=Puma HTTP Server
After=network.target
[Service]
# Foreground process (do not use --daemon in ExecStart or config.rb)
Type=simple
# Preferably configure a non-privileged user
User=deploy
# The path to the your application code root directory
WorkingDirectory=/home/deploy/my-app
# The command to start Puma
ExecStart=/home/deploy/.rbenv/shims/puma -C /home/deploy/my-app/config/puma.rb
# The command to stop Puma
ExecStop=/home/deploy/.rbenv/shims/puma -S /home/deploy/my-app/config/puma.rb
# Path to PID file so that systemd knows which is the master process
PIDFile=/home/deploy/my-app/tmp/pids/puma.pid
# Should systemd restart puma?
# Use "no" (the default) to ensure no interference when using
# stop/start/restart via `pumactl`. The "on-failure" setting might
# work better for this purpose, but you must test it.
# Use "always" if only `systemctl` is used for start/stop/restart, and
# reconsider if you actually need the forking config.
Restart=always
[Install]
WantedBy=multi-user.target
Note:
- For
ExecStart: ExecStart=/your-puma-directory-path -C /your-app-puma-config-file-path
- For
ExecStop: ExecStop=/your-puma-directory-path -S /your-app-puma-config-file-path
- 不需要定义
ExecReload or ExecRestart，它们开箱即用。
您现在可以使用以下命令启动 puma 服务器：
sudo systemctl start puma
或者使用以下命令重新启动 puma 服务器：
sudo systemctl restart puma
或者使用以下命令检查 puma 服务器的状态：
sudo systemctl status puma
或者使用以下命令停止 puma 服务器：
sudo systemctl stop puma
就这样。
我希望这有帮助
本文内容由网友自发贡献，版权归原作者所有，本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容，请联系:hwhale#tublm.com(使用前将#替换为@)
