You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* giteaofficial/main:
Filter inactive auth sources (go-gitea#27870)
refactor postgres connection string building (go-gitea#27723)
doc: actions/act-runner: document running as a systemd service (go-gitea#27844)
Support storage base path as prefix (go-gitea#27827)
Copy file name to clipboardExpand all lines: docs/content/administration/config-cheat-sheet.en-us.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -424,7 +424,7 @@ The following configuration set `Content-Type: application/vnd.android.package-a
424
424
## Database (`database`)
425
425
426
426
-`DB_TYPE`: **mysql**: The database type in use \[mysql, postgres, mssql, sqlite3\].
427
-
-`HOST`: **127.0.0.1:3306**: Database host address and port or absolute path for unix socket \[mysql, postgres\] (ex: /var/run/mysqld/mysqld.sock).
427
+
-`HOST`: **127.0.0.1:3306**: Database host address and port or absolute path for unix socket \[mysql, postgres[^1]\] (ex: /var/run/mysqld/mysqld.sock).
428
428
-`NAME`: **gitea**: Database name.
429
429
-`USER`: **root**: Database username.
430
430
-`PASSWD`: **_empty_**: Database user password. Use \`your password\` or """your password""" for quoting if you use special characters in the password.
@@ -455,6 +455,8 @@ The following configuration set `Content-Type: application/vnd.android.package-a
455
455
-`CONN_MAX_LIFETIME`**0 or 3s**: Sets the maximum amount of time a DB connection may be reused - default is 0, meaning there is no limit (except on MySQL where it is 3s - see #6804 & #7071).
[^1]: It may be necessary to specify a hostport even when listening on a unix socket, as the port is part of the socket name. see [#24552](https://github.com/go-gitea/gitea/issues/24552#issuecomment-1681649367) for additional details.
459
+
458
460
Please see #8540 & #8273 for further discussion of the appropriate values for `MAX_OPEN_CONNS`, `MAX_IDLE_CONNS` & `CONN_MAX_LIFETIME` and their
Copy file name to clipboardExpand all lines: docs/content/usage/actions/act-runner.en-us.md
+34Lines changed: 34 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -268,6 +268,40 @@ The runner will fetch jobs from the Gitea instance and run them automatically.
268
268
269
269
Since act runner is still in development, it is recommended to check the latest version and upgrade it regularly.
270
270
271
+
## Systemd service
272
+
273
+
It is also possible to run act-runner as a [systemd](https://en.wikipedia.org/wiki/Systemd) service. Create an unprivileged `act_runner` user on your system, and the following file in `/etc/systemd/system/act_runner.service`. The paths in `ExecStart` and `WorkingDirectory` may need to be adjusted depending on where you installed the `act_runner` binary, its configuration file, and the home directory of the `act_runner` user.
If using Docker, the `act_runner` user should also be added to the `docker` group before starting the service. Keep in mind that this effectively gives `act_runner` root access to the system [[1]](https://docs.docker.com/engine/security/#docker-daemon-attack-surface).
304
+
271
305
## Configuration variable
272
306
273
307
You can create configuration variables on the user, organization and repository level.
0 commit comments