Makes a minor correction to which is the next version number.
Also includes information about the `7.0` docker tag's versioning based on facts the author only can recall seeing on Matrix but currently cannot actually find direct proof of such messages existence for reference now.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/645
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: adagio <h759bkyo4@mozmail.com>
Co-committed-by: adagio <h759bkyo4@mozmail.com>
The page grew over the past year to have redundancies and
inconsistencies. It is organized to keep sections that are common to
all machines in one place:
* LXC container creation
* Forgejo runner creation
* DRBD
* vSwitch
The other sections are unified (Disk partitioning).
Places `.` symbol at the end of a couple of list sentences.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/633
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: adagio <h759bkyo4@mozmail.com>
Co-committed-by: adagio <h759bkyo4@mozmail.com>
Now that I've finished `/docs/user` I suppose I will start working on `/docs/admin`. I didn't change all the files at once since I thought it would be annoying for the maintainers to review. If you prefer I make all the changes at once, feel free to let me know and I would be happy to do that as well. :)
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/656
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Reviewed-by: Caesar Schinas <caesar@caesarschinas.com>
Co-authored-by: Abdur-Rahman Mansoor <armansoor@missingno.dev>
Co-committed-by: Abdur-Rahman Mansoor <armansoor@missingno.dev>
You'll notice that asides from some typo fixes, "organisation" has been changed to "organization" to ensure a more consistent style guide, adapted to Codeberg's style: https://docs.codeberg.org/improving-documentation/style-guide/
Also changed "orgs" to "organizations" as it's more professional and easier to understand.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/647
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Abdur-Rahman Mansoor <armansoor@missingno.dev>
Co-committed-by: Abdur-Rahman Mansoor <armansoor@missingno.dev>
I've added a more comprehensive guide to set up Reverse Proxies.
So far I've added nginx configuration, I'm also planning to add apache configuration later on.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/600
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Kwonunn <kwonunnx@gmail.com>
Co-committed-by: Kwonunn <kwonunnx@gmail.com>
- add a checklist to the release instructions
- use a pattern for push instead of an explicit list of branches
it was previously advisable to avoid conflicts when there was
no automated backports but it is no longer necessary
Per "request" of @0ko in https://codeberg.org/forgejo/forgejo/pulls/3270#issuecomment-1774032
TODOs
- postponed: how to add codespell (written in Python) to CI -- separate workflow? add to some other step? to some other tool/specification?
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/536
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
Co-committed-by: Yaroslav Halchenko <debian@onerussian.com>
`[clean up job]../../admin/config-cheat-sheet/#cron---cleanup-expired-packages-croncleanup_packages)` -> `[clean up job](../../admin/config-cheat-sheet/#cron---cleanup-expired-packages-croncleanup_packages)`
- LTS are listed in the table, no hint in the version number
- update the RC release names
- CLI updates
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/561
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
in the case of a release that is not yet published, it will exist as
release candidates in the experimental organization. Every release go
through there and it is a reliable source.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/542
Reviewed-by: crystal <crystal@noreply.codeberg.org>
Co-authored-by: Earl Warren <contact@earl-warren.org>
Co-committed-by: Earl Warren <contact@earl-warren.org>
They get /forgejo/forgejo/archive/100448a007707c049a769cb71cd170fcb5b64a25.bundle
despite https://code.forgejo.org/robots.txt having
Disallow: /*/*/archive/
Disallow: /*/*/archive/*.bundle
Hi,
somehow I made a hash of the last PR #522 so it failed linting again. I hope it is ok now. Sorry for the noise!
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/525
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Christian Drexler <xunzi@noreply.codeberg.org>
Co-committed-by: Christian Drexler <xunzi@noreply.codeberg.org>
This reverts commit 28cdb8ca82, because
the functionality has been superseded by a different implementation.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
It was quite painful yesterday to try to figure out why my workflow didn't work anymore after the Forgejo migration. Turns out that `gitea/act_runner` used a different default Docker image. With this PR, it should be clearer to other people what is the meaning of the labels.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/475
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
This PR extends the examples that were provided by @earl-warren in https://codeberg.org/forgejo/runner. I've tested this configuration twice today on two completely separate servers. For more information about the whole process that I've used, see https://huijzer.xyz/posts/forgejo-setup/.
I'll try to extract upstream a bit more information to the Forgejo docs. Feel free to take anything from my blog that seems useful and don't worry about credits. Feel free to copy whatever seems useful.
Co-authored-by: Rik Huijzer <github@huijzer.xyz>
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/474
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Rik Huijzer <rikh@noreply.codeberg.org>
Co-committed-by: Rik Huijzer <rikh@noreply.codeberg.org>
It doesn't feel right to have such guide on the installation page, it
feels more natural to have it's own page. This also keeps the
'installation' page clean, which currently feels more like an index
page, given it's linking to two other pages (installation from {binary,docker}).
* Release number is v7.0.0+1.22.0 and following semantic versioning
* Remove the workflow page which is no longer needed as:
* it is implicitly understood pull requests go to the default branch
* testing requirements are documented in the testing.md page
* Explain how to cut a release and set the tag in forgejo-integration
for proper numbering of the test releases that come out of the
development branch
Refs: https://codeberg.org/forgejo/forgejo/pulls/2448
Preview: https://forgejo.codeberg.page/@docs_pull_427/docs/next/admin/customization/
---
The previous version of this document insinuated that you need to be
familiar with Forgejo's source code and compile Forgejo from source
for custom branding changes. As of the most recent Forgejo version,
this is not necessarily true, as custom files can be served from
the CustomPath.
Administrators that were not developers therefore dismissed the
other guide and its contents without reading this, and I was one
of them. I thought it would make sense for this file to provide
information on where to put a custom logo. This change does not
fix it (this will be done later), but it will reduce the confusion
for now.
This warning confused me personally and other Forgejo users, as I
had one person tell me IRL that they thought that it was not possible
to serve a custom logo.
Reviewed-on: https://codeberg.org/forgejo/docs/pulls/427
Reviewed-by: Earl Warren <earl-warren@noreply.codeberg.org>
Co-authored-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
Co-committed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net>
