Admin at 00:20, 10 September 2018

2018-09-10T00:20:01Z

← Older revision		Revision as of 00:20, 10 September 2018
Line 10:		Line 10:

	The start and stop scripts should be located somewhere easy to find, like ~/scripts.		The start and stop scripts should be located somewhere easy to find, like ~/scripts.

			Examples:

			* https://github.com/dcppc/uncle-archie/tree/dcppc/scripts

	==Service Script==		==Service Script==

Admin: /* Quick Guide to Startup Scripts */

2018-09-10T00:19:30Z

Quick Guide to Startup Scripts

← Older revision		Revision as of 00:19, 10 September 2018
Line 9:		Line 9:
	The service script will run the service via systemd, while the start/stop scripts are actually called by the service.		The service script will run the service via systemd, while the start/stop scripts are actually called by the service.

	~~These~~ should be ~~installed in a "standard" location~~ like ~/scripts.		The start and stop scripts should be located somewhere easy to find, like ~/scripts.

	==Service Script==		==Service Script==

Admin: Created page with "=Quick Guide to Startup Scripts= Three components are needed for a startup service: * Service script * Start script * Stop script The service script will run the service vi..."

2018-09-10T00:18:58Z

Created page with "=Quick Guide to Startup Scripts= Three components are needed for a startup service: * Service script * Start script * Stop script The service script will run the service vi..."

New page

=Quick Guide to Startup Scripts=

Three components are needed for a startup service:

* Service script
* Start script
* Stop script

The service script will run the service via systemd, while the start/stop scripts are actually called by the service.

These should be installed in a "standard" location like ~/scripts.

==Service Script==

The service script runs as sudo, so keep that in mind if you run any scripts that use the home variable or require user credentials in a dotfile in the home folder.

<pre>
[Unit]
Description=Uncle Archie CI Server
After=multi-user.target

[Service]
Restart=always
ExecStart=/usr/bin/sudo -H -u ubuntu /usr/bin/bash /home/ubuntu/uncle-archie/scripts/start_archie.sh
uxecStop=/usr/bin/sudo pkill -f uncle_archie

[Install]
WantedBy=multi-user.target
</pre>

==Start Script==

Example start script:

<pre>
#!/bin/bash
#
# To test-run:
#
# sudo -H -u ubuntu ./start_archie.sh
#
# To actually run:
#
# (install archie.service startup service)
#
# Shell script used to start up uncle archie
# so uncle archie can run as a startup service.
#
# This is reliant on having pyenv set up already
# on beavo, the server that runs archie.

ARCHIE_DIR="/home/ubuntu/uncle-archie"
PYENV_BIN="/home/ubuntu/.pyenv/bin"

echo "Preparing python"
eval "$(${PYENV_BIN}/pyenv init -)"

echo "Changing directories"
cd ${ARCHIE_DIR}

echo "Installing virtualenv"
virtualenv vp
source vp/bin/activate

echo "Running Uncle Archie bare"
python ${ARCHIE_DIR}/uncle_archie.py && tail -f /nev/null
</pre>

==Stop Script==

Example stop script:

<pre>
#!/bin/bash
#
# This command actually goes straight into
# archie.service, don't use this script.

/usr/bin/sudo pkill -f uncle_archie
</pre>

=Flags=

[[Category:Bash]]
[[Category:Linux]]
[[Category:Unix]]

Service/Quick - Revision history

Admin at 00:20, 10 September 2018

Admin: /* Quick Guide to Startup Scripts */

Admin: Created page with "=Quick Guide to Startup Scripts= Three components are needed for a startup service: * Service script * Start script * Stop script The service script will run the service vi..."