discourse_ynh/conf/systemd.service

[Unit]
Description=__APP__ service
Wants=postgresql.service
Wants=redis-server.service
After=redis-server.service
After=postgresql.service

[Service]
User=__APP__
Group=__APP__
WorkingDirectory=__FINALPATH__
Environment=__ADDITIONAL_ENV__
Environment=RAILS_ENV=production
Environment=LD_PRELOAD=__LIBJEMALLOC__
ExecStart=__RBENVROOT__/shims/bundle exec unicorn --config config/unicorn.conf.rb -E production
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target
Initial commit 2018-04-02 16:36:02 +02:00			`[Unit]`
Use unicorn instead of puma, hence not needing a separate sidekiq service and drastically reducing memory footprint Limit number of workers to 2 on ARM devices See here: https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278/8 2018-05-04 12:51:16 +02:00			`Description=__APP__ service`
Initial commit 2018-04-02 16:36:02 +02:00			`Wants=postgresql.service`
			`Wants=redis-server.service`
			`After=redis-server.service`
			`After=postgresql.service`

			`[Service]`
			`User=__APP__`
			`Group=__APP__`
			`WorkingDirectory=__FINALPATH__`
Add ARM compatibility 2018-04-29 11:25:32 +02:00			`Environment=__ADDITIONAL_ENV__`
Initial commit 2018-04-02 16:36:02 +02:00			`Environment=RAILS_ENV=production`
Use unicorn instead of puma, hence not needing a separate sidekiq service and drastically reducing memory footprint Limit number of workers to 2 on ARM devices See here: https://meta.discourse.org/t/does-discourse-require-2gb-to-work-lag-free/25278/8 2018-05-04 12:51:16 +02:00			`Environment=LD_PRELOAD=__LIBJEMALLOC__`
			`ExecStart=__RBENVROOT__/shims/bundle exec unicorn --config config/unicorn.conf.rb -E production`
Initial commit 2018-04-02 16:36:02 +02:00			`Restart=always`
			`RestartSec=10`

			`[Install]`
			`WantedBy=multi-user.target`