Admin: pm2 mentioned

2026-07-13T17:56:57Z

pm2 mentioned

← Older revision		Revision as of 17:56, 13 July 2026
Line 1:		Line 1:
	The (generally) best way to run your apps 24/7 in the background on nest is through the use of systemd. It runs as PID 1 and is the first thing that starts in any nest container. For more information check out https://wiki.archlinux.org/title/Systemd (one of the best systemd docs in my opinion).		The (generally) best way to run your apps 24/7 in the background on nest is through the use of systemd. It runs as PID 1 and is the first thing that starts in any nest container. For more information check out https://wiki.archlinux.org/title/Systemd (one of the best systemd docs in my opinion). If you're overwhelmed by this guide or want a simpler option, you may want to check out [[PM2]] as an alternative.
	=== Tutorial ===		=== Tutorial ===
	We are going to run your project as a systemd service, which are usually located in <code>/etc/systemd/system/<name>.service</code>. To create/edit this, file you can either use <code>nano /etc/systemd/system/<name>.service</code> or <code>systemctl edit --full --force <name>.service</code>. For this guide we will use the latter. If you use nano, you will also need to run <code>systemctl daemon-reload</code> after.		We are going to run your project as a systemd service, which are usually located in <code>/etc/systemd/system/<name>.service</code>. To create/edit this, file you can either use <code>nano /etc/systemd/system/<name>.service</code> or <code>systemctl edit --full --force <name>.service</code>. For this guide we will use the latter. If you use nano, you will also need to run <code>systemctl daemon-reload</code> after.

Admin: Created page with "The (generally) best way to run your apps 24/7 in the background on nest is through the use of systemd. It runs as PID 1 and is the first thing that starts in any nest container. For more information check out https://wiki.archlinux.org/title/Systemd (one of the best systemd docs in my opinion). === Tutorial === We are going to run your project as a systemd service, which are usually located in `/etc/systemd/system/.service`. To create/edit this, file yo..."

2026-06-28T14:18:24Z

Created page with "The (generally) best way to run your apps 24/7 in the background on nest is through the use of systemd. It runs as PID 1 and is the first thing that starts in any nest container. For more information check out https://wiki.archlinux.org/title/Systemd (one of the best systemd docs in my opinion). === Tutorial === We are going to run your project as a systemd service, which are usually located in <code>/etc/systemd/system/<name>.service</code>. To create/edit this, file yo..."

New page

The (generally) best way to run your apps 24/7 in the background on nest is through the use of systemd. It runs as PID 1 and is the first thing that starts in any nest container. For more information check out https://wiki.archlinux.org/title/Systemd (one of the best systemd docs in my opinion).
=== Tutorial ===
We are going to run your project as a systemd service, which are usually located in <code>/etc/systemd/system/<name>.service</code>. To create/edit this, file you can either use <code>nano /etc/systemd/system/<name>.service</code> or <code>systemctl edit --full --force <name>.service</code>. For this guide we will use the latter. If you use nano, you will also need to run <code>systemctl daemon-reload</code> after.

# Find out how you are running your project '''exactly'''. If you are running with node, run <code>which node</code> and note down the full path you get (for example <code>/usr/local/bin/node</code>). For anything else it's the same, just run <code>which python/bun/etc</code>.
# Create a new systemctl service with <code>systemctl edit --full --force <name>.service</code>, make sure name is unique and represents your project (for example: "cool-slack-bot" is good, python is bad). Example: <code>systemctl edit --full --force cool-slack-bot.service</code>
# Paste this file, and edit it to match your project:
<syntaxhighlight lang="systemd">[Unit]
Description=Cool Slack Bot
Wants=network-online.target
After=network-online.target

[Service]
# If you are not using node, replace /usr/local/bin/node
# Also make sure to replace <project>, and index.js if necessary
ExecStart=/usr/local/bin/node /root/<project>/index.js
# Make sure to replace <project>
WorkingDirectory=/root/<project>
Restart=always
RestartSec=5
# Uncomment this if you have a .env file, change the path if needed:
# EnvironmentFile=/root/<project>/.env

[Install]
WantedBy=multi-user.target
</syntaxhighlight>
# Enable and start your project using <code>systemctl enable <name>.service --now</code>, then check if it's running with <code>systemctl status <name>.service</code>.
# If you need to view the latest logs for the service, use <code>journalctl -eu <name></code>.

Systemd - Revision history

Admin: pm2 mentioned