mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-17 19:46:18 +00:00
613192ae64
The problem is Type=notify - when that is set, systemd waits for a signal from the service that it's ready so systemctl start forgejo takes forever (or until it runs into a timeout). Refs: https://codeberg.org/forgejo/forgejo/issues/777 (cherry picked from commitc127369bba) (cherry picked from commit883a7eb570) (cherry picked from commit4dfa4c7d21) (cherry picked from commit961163d010) (cherry picked from commit6a05812628) (cherry picked from commit112c419f0b) (cherry picked from commitf3cd60dee7) (cherry picked from commit6fccc6bf0b) (cherry picked from commit556862de70) (cherry picked from commiteb8e2880f7) (cherry picked from commit264d85330c) (cherry picked from commit083e66a2b6) (cherry picked from commitc1385bca55) (cherry picked from commitd61930730d) (cherry picked from commitcfc815254f)
88 lines
2.5 KiB
Desktop File
88 lines
2.5 KiB
Desktop File
[Unit]
|
|
Description=Forgejo (Beyond coding. We forge.)
|
|
After=syslog.target
|
|
After=network.target
|
|
###
|
|
# Don't forget to add the database service dependencies
|
|
###
|
|
#
|
|
#Wants=mysql.service
|
|
#After=mysql.service
|
|
#
|
|
#Wants=mariadb.service
|
|
#After=mariadb.service
|
|
#
|
|
#Wants=postgresql.service
|
|
#After=postgresql.service
|
|
#
|
|
#Wants=memcached.service
|
|
#After=memcached.service
|
|
#
|
|
#Wants=redis.service
|
|
#After=redis.service
|
|
#
|
|
###
|
|
# If using socket activation for main http/s
|
|
###
|
|
#
|
|
#After=forgejo.main.socket
|
|
#Requires=forgejo.main.socket
|
|
#
|
|
###
|
|
# (You can also provide forgejo an http fallback and/or ssh socket too)
|
|
#
|
|
# An example of /etc/systemd/system/forgejo.main.socket
|
|
###
|
|
##
|
|
## [Unit]
|
|
## Description=Forgejo Web Socket
|
|
## PartOf=forgejo.service
|
|
##
|
|
## [Socket]
|
|
## Service=forgejo.service
|
|
## ListenStream=<some_port>
|
|
## NoDelay=true
|
|
##
|
|
## [Install]
|
|
## WantedBy=sockets.target
|
|
##
|
|
###
|
|
|
|
[Service]
|
|
# Uncomment the next line if you have repos with lots of files and get a HTTP 500 error because of that
|
|
# LimitNOFILE=524288:524288
|
|
RestartSec=2s
|
|
Type=simple
|
|
User=git
|
|
Group=git
|
|
WorkingDirectory=/var/lib/forgejo/
|
|
# If using Unix socket: tells systemd to create the /run/forgejo folder, which will contain the forgejo.sock file
|
|
# (manually creating /run/forgejo doesn't work, because it would not persist across reboots)
|
|
#RuntimeDirectory=forgejo
|
|
ExecStart=/usr/local/bin/forgejo web --config /etc/forgejo/app.ini
|
|
Restart=always
|
|
Environment=USER=git HOME=/home/git GITEA_WORK_DIR=/var/lib/forgejo
|
|
WatchdogSec=30s
|
|
# If you install Git to directory prefix other than default PATH (which happens
|
|
# for example if you install other versions of Git side-to-side with
|
|
# distribution version), uncomment below line and add that prefix to PATH
|
|
# Don't forget to place git-lfs binary on the PATH below if you want to enable
|
|
# Git LFS support
|
|
#Environment=PATH=/path/to/git/bin:/bin:/sbin:/usr/bin:/usr/sbin
|
|
# If you want to bind Forgejo to a port below 1024, uncomment
|
|
# the two values below, or use socket activation to pass Forgejo its ports as above
|
|
###
|
|
#CapabilityBoundingSet=CAP_NET_BIND_SERVICE
|
|
#AmbientCapabilities=CAP_NET_BIND_SERVICE
|
|
###
|
|
# In some cases, when using CapabilityBoundingSet and AmbientCapabilities option, you may want to
|
|
# set the following value to false to allow capabilities to be applied on Forgejo process. The following
|
|
# value if set to true sandboxes Forgejo service and prevent any processes from running with privileges
|
|
# in the host user namespace.
|
|
###
|
|
#PrivateUsers=false
|
|
###
|
|
|
|
[Install]
|
|
WantedBy=multi-user.target
|