https://guides.hackclub.app/index.php?action=history&feed=atom&title=Systemd 2026-06-29T19:37:52Z Revision history for this page on the wiki MediaWiki 1.45.3 https://guides.hackclub.app/index.php?title=Systemd&diff=97&oldid=prev 2026-06-28T14:18:24Z

<p>Created page with &quot;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 &lt;code&gt;/etc/systemd/system/&lt;name&gt;.service&lt;/code&gt;. To create/edit this, file yo...&quot;</p> <p><b>New page</b></p><div>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).<br /> === Tutorial ===<br /> We are going to run your project as a systemd service, which are usually located in &lt;code&gt;/etc/systemd/system/&lt;name&gt;.service&lt;/code&gt;. To create/edit this, file you can either use &lt;code&gt;nano /etc/systemd/system/&lt;name&gt;.service&lt;/code&gt; or &lt;code&gt;systemctl edit --full --force &lt;name&gt;.service&lt;/code&gt;. For this guide we will use the latter. If you use nano, you will also need to run &lt;code&gt;systemctl daemon-reload&lt;/code&gt; after.<br /> <br /> # Find out how you are running your project &#039;&#039;&#039;exactly&#039;&#039;&#039;. If you are running with node, run &lt;code&gt;which node&lt;/code&gt; and note down the full path you get (for example &lt;code&gt;/usr/local/bin/node&lt;/code&gt;). For anything else it&#039;s the same, just run &lt;code&gt;which python/bun/etc&lt;/code&gt;.<br /> # Create a new systemctl service with &lt;code&gt;systemctl edit --full --force &lt;name&gt;.service&lt;/code&gt;, make sure name is unique and represents your project (for example: &quot;cool-slack-bot&quot; is good, python is bad). Example: &lt;code&gt;systemctl edit --full --force cool-slack-bot.service&lt;/code&gt;<br /> # Paste this file, and edit it to match your project:<br /> &lt;syntaxhighlight lang=&quot;systemd&quot;&gt;[Unit]<br /> Description=Cool Slack Bot<br /> Wants=network-online.target<br /> After=network-online.target<br /> <br /> [Service]<br /> # If you are not using node, replace /usr/local/bin/node<br /> # Also make sure to replace &lt;project&gt;, and index.js if necessary<br /> ExecStart=/usr/local/bin/node /root/&lt;project&gt;/index.js<br /> # Make sure to replace &lt;project&gt;<br /> WorkingDirectory=/root/&lt;project&gt;<br /> Restart=always<br /> RestartSec=5<br /> # Uncomment this if you have a .env file, change the path if needed:<br /> # EnvironmentFile=/root/&lt;project&gt;/.env<br /> <br /> [Install]<br /> WantedBy=multi-user.target<br /> &lt;/syntaxhighlight&gt;<br /> # Enable and start your project using &lt;code&gt;systemctl enable &lt;name&gt;.service --now&lt;/code&gt;, then check if it&#039;s running with &lt;code&gt;systemctl status &lt;name&gt;.service&lt;/code&gt;.<br /> # If you need to view the latest logs for the service, use &lt;code&gt;journalctl -eu &lt;name&gt;&lt;/code&gt;.</div>

Admin