Service files - Revision history

SHRED: /* Making a systemd service file */

2026-05-27T11:11:22Z

Making a systemd service file

← Older revision		Revision as of 13:11, 27 May 2026
Line 7:		Line 7:
	Useful: https://containersolutions.github.io/runbooks/posts/linux/debug-systemd-service-units/		Useful: https://containersolutions.github.io/runbooks/posts/linux/debug-systemd-service-units/

	$ sudo nano /etc/systemd/system/YOUR_NAME_OF_THE_APP.service		$ sudo nano /etc/systemd/system/YOUR_NAME_OF_THE_APP'''.service'''

	<pre>		<pre>

2026-05-27T11:10:40Z

← Older revision		Revision as of 13:10, 27 May 2026
Line 33:		Line 33:
	User=YOUR_USERNAME		User=YOUR_USERNAME
	WorkingDirectory=/YOUR/PATH/		WorkingDirectory=/YOUR/PATH/
	ExecStart=/YOUR/PATH/.venv/bin/flask --app NAME_OF_YOUR_PY_FILE run --port 51?? #DO NOT PUT .py AT THE END #PUT YOUR_PORT		ExecStart=/YOUR/PATH/.venv/bin/flask --app NAME_OF_YOUR_PY_FILE run --port 51?? #DO NOT PUT .py AT THE END + #PUT YOUR_PORT
	Restart=always		Restart=always

2026-05-27T11:10:07Z

Making a systemd service file

← Older revision		Revision as of 13:10, 27 May 2026
Line 49:		Line 49:
	$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP

	When you see that ~~start works~~ (checking status, ~~checking~~ that it actually is running , etc)		When you see that it's working (checking its status, that it actually is running, etc...)

	$ sudo systemctl '''enable''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''enable''' YOUR_NAME_OF_THE_APP
Line 55:		Line 55:
	Will make the "service" auto start when the pi restarts.		Will make the "service" auto start when the pi restarts.

	Additional commands:		'''Additional commands:'''
	$ sudo systemctl restart YOUR_NAME_OF_THE_APP		$ sudo systemctl restart YOUR_NAME_OF_THE_APP
	$ sudo systemctl stop YOUR_NAME_OF_THE_APP		$ sudo systemctl stop YOUR_NAME_OF_THE_APP

2026-05-27T11:09:00Z

Making a systemd service file

← Older revision		Revision as of 13:09, 27 May 2026
Line 49:		Line 49:
	$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP

	~~'''Then finally''' when~~ you see that start works (checking status, checking that it actually is running , etc)		When you see that start works (checking status, checking that it actually is running , etc)

	$ sudo systemctl '''enable''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''enable''' YOUR_NAME_OF_THE_APP

2026-05-27T11:08:18Z

← Older revision		Revision as of 13:08, 27 May 2026
Line 48:		Line 48:
	$ sudo systemctl '''start''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''start''' YOUR_NAME_OF_THE_APP
	$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP

	~~Additional commands:~~
	~~$ sudo systemctl restart YOUR_NAME_OF_THE_APP~~
	~~$ sudo systemctl stop YOUR_NAME_OF_THE_APP~~

	'''Then finally''' when you see that start works (checking status, checking that it actually is running , etc)		'''Then finally''' when you see that start works (checking status, checking that it actually is running , etc)
Line 58:		Line 54:

	Will make the "service" auto start when the pi restarts.		Will make the "service" auto start when the pi restarts.

			Additional commands:
			$ sudo systemctl restart YOUR_NAME_OF_THE_APP
			$ sudo systemctl stop YOUR_NAME_OF_THE_APP

	To view the log file (errors):		To view the log file (errors):

2026-05-27T11:07:39Z

← Older revision		Revision as of 13:07, 27 May 2026
Line 49:		Line 49:
	$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP		$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP

	~~Addition~~ commands:		Additional commands:
	$ sudo systemctl restart YOUR_NAME_OF_THE_APP		$ sudo systemctl restart YOUR_NAME_OF_THE_APP
	$ sudo systemctl stop YOUR_NAME_OF_THE_APP		$ sudo systemctl stop YOUR_NAME_OF_THE_APP

2026-05-27T11:05:23Z

Making a systemd service file

← Older revision		Revision as of 13:05, 27 May 2026
Line 44:		Line 44:
	$ sudo systemctl daemon-reload		$ sudo systemctl daemon-reload

	Then in order ~~you can~~:		Then in order:

	$ sudo systemctl ~~enable YOUR_NAME_OF_THE_APP.service~~		$ sudo systemctl '''start''' YOUR_NAME_OF_THE_APP
	~~$ sudo systemctl~~ start YOUR_NAME_OF_THE_APP		$ sudo systemctl '''status''' YOUR_NAME_OF_THE_APP
	$ sudo systemctl status YOUR_NAME_OF_THE_APP

	Addition commands:		Addition commands:
Line 56:		Line 55:
	'''Then finally''' when you see that start works (checking status, checking that it actually is running , etc)		'''Then finally''' when you see that start works (checking status, checking that it actually is running , etc)

	$ sudo systemctl enable YOUR_NAME_OF_THE_APP		$ sudo systemctl '''enable''' YOUR_NAME_OF_THE_APP

	Will make the "service" auto start when the pi restarts.		Will make the "service" auto start when the pi restarts.

2026-05-27T11:03:14Z

← Older revision		Revision as of 13:03, 27 May 2026
Line 44:		Line 44:
	$ sudo systemctl daemon-reload		$ sudo systemctl daemon-reload

	Then you can:		Then in order you can:

			$ sudo systemctl enable YOUR_NAME_OF_THE_APP.service
	$ sudo systemctl start YOUR_NAME_OF_THE_APP		$ sudo systemctl start YOUR_NAME_OF_THE_APP
	$ sudo systemctl status YOUR_NAME_OF_THE_APP		$ sudo systemctl status YOUR_NAME_OF_THE_APP

			Addition commands:
	$ sudo systemctl restart YOUR_NAME_OF_THE_APP		$ sudo systemctl restart YOUR_NAME_OF_THE_APP
	$ sudo systemctl stop YOUR_NAME_OF_THE_APP		$ sudo systemctl stop YOUR_NAME_OF_THE_APP

2026-05-27T10:59:14Z

Making a systemd service file

← Older revision		Revision as of 12:59, 27 May 2026
Line 40:		Line 40:
	</syntaxhighlight>		</syntaxhighlight>

	~~When the~~ service file is new or changed~~, you need (one time) to:~~		1st thing to do when your <code>.service</code> file is new or changed

	$ sudo systemctl daemon-reload		$ sudo systemctl daemon-reload

2026-05-27T10:56:57Z

Making a systemd service file

← Older revision		Revision as of 12:56, 27 May 2026
Line 27:		Line 27:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	[Unit]		[Unit]
	Description=~~An example of a fieldwork-tool~~ made in ~~flask~~		Description=Bla Bla Bla made in Flask
	After=network.target		After=network.target

	[Service]		[Service]
	User=~~manetta~~		User=YOUR_USERNAME
	WorkingDirectory=/YOUR/PATH/		WorkingDirectory=/YOUR/PATH/
	ExecStart=/YOUR/PATH/.venv/bin/flask --app NAME_OF_YOUR_PY_FILE run --port 51?? #DO NOT PUT .py AT THE END #PUT YOUR_PORT		ExecStart=/YOUR/PATH/.venv/bin/flask --app NAME_OF_YOUR_PY_FILE run --port 51?? #DO NOT PUT .py AT THE END #PUT YOUR_PORT