grafana/packaging/deb/systemd/grafana-server.service

[Unit]
Description=Grafana instance
Documentation=http://docs.grafana.org
Wants=network-online.target
After=network-online.target
After=postgresql.service mariadb.service mysql.service

[Service]
EnvironmentFile=/etc/default/grafana-server
User=grafana
Group=grafana
Type=simple
Restart=on-failure
WorkingDirectory=/usr/share/grafana
RuntimeDirectory=grafana
RuntimeDirectoryMode=0750
ExecStart=/usr/sbin/grafana-server                                                  \
                            --config=${CONF_FILE}                                   \
                            --pidfile=${PID_FILE_DIR}/grafana-server.pid            \
                            cfg:default.paths.logs=${LOG_DIR}                       \
                            cfg:default.paths.data=${DATA_DIR}                      \
                            cfg:default.paths.plugins=${PLUGINS_DIR}                \
                            cfg:default.paths.provisioning=${PROVISIONING_CFG_DIR}  


LimitNOFILE=10000
TimeoutStopSec=20
UMask=0027

[Install]
WantedBy=multi-user.target
Worked on new deb & rpm packaging and init.d scripts 2015-04-08 07:10:04 -05:00			`[Unit]`
Update systemd unit's description to be more understandable Signed-off-by: Christopher Meng <i@cicku.me> 2016-09-06 09:29:15 -05:00			`Description=Grafana instance`
Worked on new deb & rpm packaging and init.d scripts 2015-04-08 07:10:04 -05:00			`Documentation=http://docs.grafana.org`
			`Wants=network-online.target`
			`After=network-online.target`
Add an After= DB ordering relation to systemd .service (#7903) In systemd `After=` merely codes an ordering relation and does not start other units. Grafana needs to specify that it wants to start up _after_ either of the supported DB services have started, _if they start_. Enabling the database services, however, is out of scope for Grafana. 2017-03-22 10:49:35 -05:00			`After=postgresql.service mariadb.service mysql.service`
Worked on new deb & rpm packaging and init.d scripts 2015-04-08 07:10:04 -05:00
			`[Service]`
systemd service is working on debian jessie 2015-04-10 04:26:03 -05:00			`EnvironmentFile=/etc/default/grafana-server`
More deb & rpm work, systemd testing 2015-04-08 09:58:05 -05:00			`User=grafana`
			`Group=grafana`
			`Type=simple`
feat(packaging): added Restart=on-failure to systemd service spec file 2016-01-13 06:57:22 -06:00			`Restart=on-failure`
systemd service is working on debian jessie 2015-04-10 04:26:03 -05:00			`WorkingDirectory=/usr/share/grafana`
packaging: changed how pid directory is created for systemd systems, #9133 2017-09-04 09:40:42 -05:00			`RuntimeDirectory=grafana`
			`RuntimeDirectoryMode=0750`
dashboards as cfg: move dash/ds config files to /provisioning/* 2017-12-07 08:14:57 -06:00			`ExecStart=/usr/sbin/grafana-server \`
			`--config=${CONF_FILE} \`
			`--pidfile=${PID_FILE_DIR}/grafana-server.pid \`
			`cfg:default.paths.logs=${LOG_DIR} \`
			`cfg:default.paths.data=${DATA_DIR} \`
			`cfg:default.paths.plugins=${PLUGINS_DIR} \`
			`cfg:default.paths.provisioning=${PROVISIONING_CFG_DIR}`
dashboards as cfg: include cfg files in dist packages 2017-12-05 08:44:10 -06:00

More deb & rpm work, systemd testing 2015-04-08 09:58:05 -05:00			`LimitNOFILE=10000`
Worked on new deb & rpm packaging and init.d scripts 2015-04-08 07:10:04 -05:00			`TimeoutStopSec=20`
Fixing permission issues for new installations The umask as 0027 will generates permissions like: 0640 - for files 0750 - for directories This should solve the grafana.db being accesable by any user for new installations. 2015-08-16 11:43:27 -05:00			`UMask=0027`
Worked on new deb & rpm packaging and init.d scripts 2015-04-08 07:10:04 -05:00
			`[Install]`
			`WantedBy=multi-user.target`