From eb70b6d8f872645dd506417d025e062eed91f4f3 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Tue, 8 Feb 2022 14:32:57 +0100 Subject: [PATCH] docs: and deploy --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3ece623..72f46d0 100644 --- a/README.md +++ b/README.md @@ -7,7 +7,7 @@ ## release management -We're using [Hometown](https://github.com/hometown-fork/hometown) with [this PR](https://github.com/mastodon/mastodon/pull/16221) merged in. Yes, that's a fork of a fork. The process of making a new release is basically merging that PR into the latest Hometown, building, tagging & pushing a container and then updating the [hometown recipe configs](https://git.coopcloud.tech/coop-cloud/hometown/src/branch/main/compose.oidc.yml). +We're using [Hometown](https://github.com/hometown-fork/hometown) with [this PR](https://github.com/mastodon/mastodon/pull/16221) merged in. Yes, that's a fork of a fork. The process of making a new release is basically merging that PR into the latest Hometown, building, tagging & pushing a container and then updating the [hometown recipe configs](https://git.coopcloud.tech/coop-cloud/hometown/src/branch/main/compose.oidc.yml). Then deploy it and debug any issues. How to do it, you ask? Abandon all hope. Computers were a mistake.