Forgejo - Revision history

Kruziikrel13: fixed a minor typo

2026-10-03T11:56:28Z

fixed a minor typo

← Older revision		Revision as of 11:56, 3 October 2026
Line 89:		Line 89:
	If you plan to use SSH keys for authenticating your git usage, there's a little extra configuration to be done to set that up:		If you plan to use SSH keys for authenticating your git usage, there's a little extra configuration to be done to set that up:
	{{File\|3={ config, lib, ... }: let		{{File\|3={ config, lib, ... }: let
	inherit (lib.lists) head);		inherit (lib.lists) head;
	in {		in {
	...		...

Kruziikrel13: Small review of forgejo runner service declarations.

2026-10-03T11:41:15Z

Small review of forgejo runner service declarations.

← Older revision		Revision as of 11:41, 3 October 2026
Line 34:		Line 34:
	{		{
	services.nginx = {		services.nginx = {
	virtualHosts.${~~cfg.settings.server~~.DOMAIN} = {		virtualHosts.${srv.DOMAIN} = {
	forceSSL = true;		forceSSL = true;
	enableACME = true;		enableACME = true;
Line 88:		Line 88:
	== Setting up OpenSSH integration ==		== Setting up OpenSSH integration ==
	If you plan to use SSH keys for authenticating your git usage, there's a little extra configuration to be done to set that up:		If you plan to use SSH keys for authenticating your git usage, there's a little extra configuration to be done to set that up:
	{{File\|3={ config, lib, ... }: {		{{File\|3={ config, lib, ... }: let
			inherit (lib.lists) head);
			in {
	...		...
	services = {		services = {
	forgejo.settings.server.SSH_PORT = ~~lib.~~head config.services.openssh.ports;		forgejo.settings.server.SSH_PORT = head config.services.openssh.ports;
	};		};
	...		...
Line 101:		Line 103:

	You can create a server-wide Runner by going to ''Profile Picture > Site Administration > Actions > Runners > Create new Runner.''		You can create a server-wide Runner by going to ''Profile Picture > Site Administration > Actions > Runners > Create new Runner.''
	Store your token in your [[Comparison of secret managing schemes\|secrets management system]] of choice, then add the following to the configuration of the machine to be used as a runner:<syntaxhighlight lang="nixos">		Store your token in your [[Comparison of secret managing schemes\|secrets management system]] of choice, then add the following to the configuration of the machine to be used as a runner:<syntaxhighlight lang="nixos">{ pkgs, config, ... }: {
	{ pkgs, config, ... }: {		# Configure a single host local runner with default package set access
	services.~~gitea-actions~~-runner = {		services.forgejo-runner = {
	package = pkgs.forgejo-runner;		package = pkgs.forgejo-runner;
	instances.default = {		instances.default = {
	enable = true;		enable = true;
	~~name~~ = ~~"monolith"~~;		runtimes.host = true;
	~~url = "https://git~~.~~example~~.~~com";~~		settings.runner.labels = [
	# ~~Obtaining~~ the ~~path to the runner token file may differ~~		# Native Execution on the Host
	~~# tokenFile should be in format TOKEN=<secret>, since it's EnvironmentFile for systemd~~		"native:host"
	~~tokenFile = config.age.secrets.forgejo-runner-token.path;~~
	~~labels = [~~		# Assuming Docker has been setup on the host machine
	"ubuntu-latest:docker://node:16-bullseye"		"ubuntu-latest:docker://node:16-bullseye"
	"ubuntu-22.04:docker://node:16-bullseye"		"ubuntu-22.04:docker://node:16-bullseye"
	"ubuntu-20.04:docker://node:16-bullseye"		"ubuntu-20.04:docker://node:16-bullseye"
	"ubuntu-18.04:docker://node:16-buster"		"ubuntu-18.04:docker://node:16-buster"
	~~## optionally provide native execution on the host:~~
	~~# "native:host~~"
	];		];
			secrets.server.connections."forgejo".token_url = "/var/lib/forgejo/forgejoToken.key"; # Path to forgejo runner key file provided by forgejo.
			settings.server.connections.forgejo = {
			url = "https://localhost:3000"; # Forgejo Instance URL
			uuid = "aaaaaaaa-bbbbbbbbbb-cccccccccc-ddddddd"; # UUID of forgejo runner instance
			};
	};		};
	};		};
	}		};</syntaxhighlight>
	</syntaxhighlight>

	== Ensure users ==		== Ensure users ==

ZephLevy: Add additional instructions to the OpenSSH integration section of the Forgejo page

2026-09-24T08:19:20Z

Add additional instructions to the OpenSSH integration section of the Forgejo page

← Older revision		Revision as of 08:19, 24 September 2026
Line 94:		Line 94:
	};		};
	...		...
	}\|name=/etc/nixos/configuration.nix\|lang=nix}}		}\|name=/etc/nixos/configuration.nix\|lang=nix}}If <code>services.openssh.settings.AllowUsers</code> is configured, ensure you add the <code>forgejo</code> user to that list to allow SSH access.

	== Actions Runner ==		== Actions Runner ==

Obale: Fixed latest release date.

2026-04-18T04:14:09Z

Fixed latest release date.

← Older revision		Revision as of 04:14, 18 April 2026
Line 8:		Line 8:
	\| platform = Cross-platform		\| platform = Cross-platform
	\| initialRelease = 15 December 2022		\| initialRelease = 15 December 2022
	\| latestRelease = 15.0.0; 17 April 2026		\| latestRelease = 15.0.0; 16 April 2026
	\| programmingLanguage = Go, JavaScript		\| programmingLanguage = Go, JavaScript
	}}		}}

Obale: Updated the latest available version to 15.0.0

2026-04-18T04:12:05Z

Updated the latest available version to 15.0.0

← Older revision		Revision as of 04:12, 18 April 2026
Line 8:		Line 8:
	\| platform = Cross-platform		\| platform = Cross-platform
	\| initialRelease = 15 December 2022		\| initialRelease = 15 December 2022
	\| latestRelease = 14.0.2; ~~29 January~~ 2026		\| latestRelease = 15.0.0; 17 April 2026
	\| programmingLanguage = Go, JavaScript		\| programmingLanguage = Go, JavaScript
	}}		}}

Taxborn: Updated the latest release

2026-02-23T22:30:35Z

Updated the latest release

← Older revision		Revision as of 22:30, 23 February 2026
Line 8:		Line 8:
	\| platform = Cross-platform		\| platform = Cross-platform
	\| initialRelease = 15 December 2022		\| initialRelease = 15 December 2022
	\| latestRelease = 11.0.7; ~~26 October 2025~~		\| latestRelease = 14.0.2; 29 January 2026
	\| programmingLanguage = Go, JavaScript		\| programmingLanguage = Go, JavaScript
	}}		}}

Starfish2228: /* Setting up OpenSSH integration */ remove redundant config

2025-12-25T04:13:02Z

Setting up OpenSSH integration: remove redundant config

← Older revision		Revision as of 04:13, 25 December 2025
Line 92:		Line 92:
	services = {		services = {
	forgejo.settings.server.SSH_PORT = lib.head config.services.openssh.ports;		forgejo.settings.server.SSH_PORT = lib.head config.services.openssh.ports;
	~~openssh.settings.AcceptEnv = "GIT_PROTOCOL";~~
	};		};
	...		...

Onny: Add see also section

2025-12-15T09:56:33Z

Add see also section

← Older revision		Revision as of 09:56, 15 December 2025
Line 185:		Line 185:
	</div>		</div>
	{{template "base/footer" .}}\|name=/etc/nixos/forgejo/home.tmpl\|lang=gotmpl}}		{{template "base/footer" .}}\|name=/etc/nixos/forgejo/home.tmpl\|lang=gotmpl}}

			== See also ==

			* [[Gitlab]], a web application offers git repository management, code reviews, issue tracking, activity feeds and wikis.
			* [[Gitea]], a web app, Git development repository and project management.

	[[Category:Web Applications]]		[[Category:Web Applications]]
	[[Category:Server]]		[[Category:Server]]
	[[Category:NixOS Manual]]		[[Category:NixOS Manual]]

Kaya: Add section on setting up openssh integratiojn

2025-11-18T23:19:56Z

Add section on setting up openssh integratiojn

@@ Line 85: / Line 85: @@
+}
 </syntaxhighlight>
 == Actions Runner ==

Kaya: Small clean up

2025-11-18T23:13:57Z

Small clean up

← Older revision		Revision as of 23:13, 18 November 2025
Line 17:		Line 17:

	== Usage ==		== Usage ==
	~~NixOs~~ provides a module for easily setting-up a Forgejo server, here is an example of typical usage with some optional features:		NixOS provides a module for easily setting-up a Forgejo server, here is an example of typical usage with some optional features:

	* Use Nginx to enable easy https configuration		* Use Nginx to enable easy https configuration
Line 86:		Line 86:
	</syntaxhighlight>		</syntaxhighlight>

	== Runner ==		== Actions Runner ==
	According to the [https://forgejo.org/docs/latest/admin/actions/#forgejo-runner documentation] the <code>Forgejo runner</code> is:<blockquote>A daemon that fetches workflows to run from a Forgejo instance, executes them, sends back with the logs and ultimately reports its success or failure.</blockquote>In order to use Actions, you will need to setup at least one Runner. You can use your server, another machine or both as runners.		According to the [https://forgejo.org/docs/latest/admin/actions/#forgejo-runner documentation] the <code>Forgejo runner</code> is:<blockquote>A daemon that fetches workflows to run from a Forgejo instance, executes them, sends back with the logs and ultimately reports its success or failure.</blockquote>In order to use Actions, you will need to setup at least one Runner. You can use your server, another machine or both as runners.


	To register a runners you will need to generate a token. https://forgejo.org/docs/latest/user/actions/#forgejo-runner		To register a runners you will need to generate a token. https://forgejo.org/docs/latest/user/actions/#forgejo-runner

	You can create a server-wide Runner by going to ''Profile Picture > Site Administration > Actions > Runners > Create new Runner.''		You can create a server-wide Runner by going to ''Profile Picture > Site Administration > Actions > Runners > Create new Runner.''


	Store your token in your [[Comparison of secret managing schemes\|secrets management system]] of choice, then add the following to the configuration of the machine to be used as a runner:<syntaxhighlight lang="nixos">		Store your token in your [[Comparison of secret managing schemes\|secrets management system]] of choice, then add the following to the configuration of the machine to be used as a runner:<syntaxhighlight lang="nixos">
	{ pkgs, config, ... }: {		{ pkgs, config, ... }: {
Line 120:		Line 116:

	== Ensure users ==		== Ensure users ==
	Using the following snippet, you can ensure users:		Using the following snippet, you can declaratively ensure these users will always exist:
	<syntaxhighlight lang="nixos">		<syntaxhighlight lang="nixos">
	sops.secrets.forgejo-admin-password.owner = "forgejo";		sops.secrets.forgejo-admin-password.owner = "forgejo";