[BRANDING] Rebrand systemd service (#137)

- We can rebrand this quite safely, as only new installations would likely look into this file and configure the correct folders(to use forgejo instead of gitea).

Co-authored-by: Gusted <postmaster@gusted.xyz>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/137
(cherry picked from commit fa78e52b5d)
(cherry picked from commit e36d649989)
(cherry picked from commit 37e15a2f41)
(cherry picked from commit a09a4b3ce0)
(cherry picked from commit 10615fca8e)
(cherry picked from commit f765a10fd3)
(cherry picked from commit 2b1b539d2c)
This commit is contained in:
Gusted 2022-12-18 19:03:34 +00:00 committed by Loïc Dachary
parent 278923718d
commit df4250b6a8
No known key found for this signature in database
GPG key ID: 992D23B392F9E4F2

View file

@ -1,5 +1,5 @@
[Unit] [Unit]
Description=Gitea (Git with a cup of tea) Description=Forgejo (Beyond coding. We forge.)
After=syslog.target After=syslog.target
After=network.target After=network.target
### ###
@ -25,21 +25,21 @@ After=network.target
# If using socket activation for main http/s # If using socket activation for main http/s
### ###
# #
#After=gitea.main.socket #After=forgejo.main.socket
#Requires=gitea.main.socket #Requires=forgejo.main.socket
# #
### ###
# (You can also provide gitea an http fallback and/or ssh socket too) # (You can also provide forgejo an http fallback and/or ssh socket too)
# #
# An example of /etc/systemd/system/gitea.main.socket # An example of /etc/systemd/system/forgejo.main.socket
### ###
## ##
## [Unit] ## [Unit]
## Description=Gitea Web Socket ## Description=Forgejo Web Socket
## PartOf=gitea.service ## PartOf=forgejo.service
## ##
## [Socket] ## [Socket]
## Service=gitea.service ## Service=forgejo.service
## ListenStream=<some_port> ## ListenStream=<some_port>
## NoDelay=true ## NoDelay=true
## ##
@ -55,28 +55,28 @@ RestartSec=2s
Type=simple Type=simple
User=git User=git
Group=git Group=git
WorkingDirectory=/var/lib/gitea/ WorkingDirectory=/var/lib/forgejo/
# If using Unix socket: tells systemd to create the /run/gitea folder, which will contain the gitea.sock file # If using Unix socket: tells systemd to create the /run/forgejo folder, which will contain the forgejo.sock file
# (manually creating /run/gitea doesn't work, because it would not persist across reboots) # (manually creating /run/forgejo doesn't work, because it would not persist across reboots)
#RuntimeDirectory=gitea #RuntimeDirectory=forgejo
ExecStart=/usr/local/bin/gitea web --config /etc/gitea/app.ini ExecStart=/usr/local/bin/forgejo web --config /etc/forgejo/app.ini
Restart=always Restart=always
Environment=USER=git HOME=/home/git GITEA_WORK_DIR=/var/lib/gitea Environment=USER=git HOME=/home/git GITEA_WORK_DIR=/var/lib/forgejo
# If you install Git to directory prefix other than default PATH (which happens # 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 # for example if you install other versions of Git side-to-side with
# distribution version), uncomment below line and add that prefix to PATH # 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 # Don't forget to place git-lfs binary on the PATH below if you want to enable
# Git LFS support # Git LFS support
#Environment=PATH=/path/to/git/bin:/bin:/sbin:/usr/bin:/usr/sbin #Environment=PATH=/path/to/git/bin:/bin:/sbin:/usr/bin:/usr/sbin
# If you want to bind Gitea to a port below 1024, uncomment # If you want to bind Forgejo to a port below 1024, uncomment
# the two values below, or use socket activation to pass Gitea its ports as above # the two values below, or use socket activation to pass Forgejo its ports as above
### ###
#CapabilityBoundingSet=CAP_NET_BIND_SERVICE #CapabilityBoundingSet=CAP_NET_BIND_SERVICE
#AmbientCapabilities=CAP_NET_BIND_SERVICE #AmbientCapabilities=CAP_NET_BIND_SERVICE
### ###
# In some cases, when using CapabilityBoundingSet and AmbientCapabilities option, you may want to # 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 gitea process. The following # set the following value to false to allow capabilities to be applied on Forgejo process. The following
# value if set to true sandboxes gitea service and prevent any processes from running with privileges # value if set to true sandboxes Forgejo service and prevent any processes from running with privileges
# in the host user namespace. # in the host user namespace.
### ###
#PrivateUsers=false #PrivateUsers=false