@gitea 1.17 breaking changes episode 1: if your Gitea instance uses a custom $HOME/.gitconfig it must be moved. Two steps:

* gitea --work-path /app/gitea -c /data/gitea/conf/app.ini doctor
- [I] Repository Root Path: "/data/git/repositories"
* cp $HOME/.gitconfig /data/git/repositories

If you are curious to know more, read on:

hostea.org/blog/1-17-breaking-

---

Authored by @dachary

@hostea @humanetech @gitea @WoodpeckerCI @dachary

...
3. image-build-time downloads we test for presence and validity.

I'm also interested in the way, you are doing tests :-)

@hostea @humanetech @gitea @WoodpeckerCI @dachary

... Things may be different for a massive hosting facility provisioning thousands of git instances a day ....

Aside of full integration test we have:
1. unittest (c4k is comparable to helm - but every build in convention we can unittest)
2. we build images from (mostly stable base dsitributions) - building fresh easy compared to handling drifted long running servers.
...

@hostea @humanetech @gitea @WoodpeckerCI @dachary at some of our modules we wrote an integrationtest ala

1. spawn a k3d (k3s in docker container)
2. install our app (i think it was c4k-nextcloud)
3. do a backup
4. kill k3d & span another one
5. install app and do a restore
6. make a curl that proves a successful restore.

But I'm not sure that the aspect proven by this test is worth the effort. (1/2)

The first version of the "HOWTO upgrades, a guide for admins" is available 🚀 Make sure to read it before performing your next @gitea upgrade, what you will learn in a few minutes may save you hours of painful work ✨

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

tip: If a @gitea instance stopped working today with this error:

Your database (migration version: 218) is for a newer Gitea, you can not use the newer database for this old Gitea release (211).

It needs to be upgraded to 1.17.0-rc1 to resume operations.

During a few minutes around 00h15 UTC the Gitea 1.16.9 release was accidentally set to latest and caused the downgrade.

Read on for more details at forum.hostea.org/t/gitea-downg

---

Authored by @dachary

tip: if your @gitea instance was unexpectedly upgraded from 1.16.8 to 1.17.0-rc1 ⚠️ do not ⚠️ try to revert back to 1.16.8.

Less than 24h ago the "latest" tag on the docker hub was moved from 1.16.8 to 1.17.0-rc1 by mistake. It should be set to the latest stable version, which 1.17.0-rc1 is not.

Downgrading to 1.16.8 is not supported and will cause problems.

See the "HOWTO Gitea upgrades, a guide for admins" for more information.

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

@team @hostea

Nice! I forwarded your toot to the #matrix chatroom at #hostea:matrix.batsense.net

OT:

I read the doc on Bounded Contexts in gitlab.com/domaindrivenarchite and I feel it misses the mark on the 'Cost' side of things.

The #DDD book is sub-titled "Tackling complexity in the heart of software", not increase it. And bounded contexts are helping improve the developer experience e.g. via Clean Architecture.

Bounded contexts are not tied to implementation, and also not to dependency hell.

tip: when Gitea is installed from from binary, you need to run it with --work-path in addition to -c to make the doctor work:

gitea doctor --work-path /var/lib/gitea -c /etc/gitea/app.ini

It is not enough to provide @Gitea with the configuration file, it always needs the --work-path argument, or the GITEA_WORK_DIR environment variable.

Reason why it is set in the systemd service file:

github.com/go-gitea/gitea/blob

---

Authored by @dachary

@ale indeed, there are plenty self-hosted #gitea servers.

This is why #forge federation will be so cool, as it wil tie them together in a large whole, and with that open the ecosystem and create a level playing field, that can weigh up to #Github network effects and #FOMO.

There's also a volunteer collective dedicated to provide easy #hosting of Gitea + #WoodpeckerCI + Pages and the ability to self-host again at any time. And they have a Clinic to help upgrade you self-hosted server: @hostea

tip: running `gitea doctor` on a docker `gitea/gitea:1.16.8` installation can be done with:

docker exec --user git --workdir=/tmp gitea gitea doctor --all

The --user git is because it otherwise runs as root and is not setup properly to run gitea. And the --workdir is because it otherwise does not have permission to write the log file in the container.

When using `gitea/gitea:1.16.8-rootless` there is no need for these extra flags.

---

Authored by @dachary

tip: only use `gitea doctor --all` and never `gitea doctor --run`.

Because of a bug in @gitea v1.16.8 the `--run` option may silently discard the messages reporting errors or warning.

Until it is fixed, the simplest workaround is to use the `--all` option instead: it is more noisy but accurate.

---

Authored by @dachary

tip: make sure to upgrade docker to version 20.10.6 or later before upgrading to @gitea 1.17 (which will be released in a few weeks).

Otherwise you will experience mysterious breakage. This can be done at any time: it is compatible with the latest Gitea 1.16. If in doubt, take a look at the HOWTO Gitea upgrades guide for admins for the latest tips.

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

tip: when @Gitea is installed with docker, here is how you will want to run the doctor 🩺 to verify it is not sick 🤕

docker exec --user git gitea gitea doctor --all --log-file /tmp/doctor.log

Should there be a need for more information looking 👀 in the doctor.log will display the gory details:

docker exec --user git gitea cat /tmp/doctor.log

---

Authored by @dachary

A instance brought to the clinic was successfully upgraded from 1.11.0 to 1.16.8 🚀

A test run was conducted to identify potential issues and there was no surprise when upgrading the production instance.

It was also an opportunity to fix a minor bug in the Gitea doctor command and to improve the Hostea upgrade guide.

gitea.hostea.org/dachary/hoste

---

Authored by @dachary

tip: the gitea doctor command is available starting with 1.10.5 & 1.10.6 and for all versions >= 1.11.5.

But contrary to what one would expect it is not available for Gitea 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.11.4.

This was discovered today while migrating a Gitea 1.11.0 instance and the HOWTO Gitea upgrade was updated with this tip.

forum.hostea.org/t/howto-gitea

---

Authored by @dachary

zombies :zombie: first showed up in 2017 and they are now explained, the bug fix is tested and ready to be merged hostea.org/blog/zombies-part-2

@codeberg must collect more than a few on a daily basis ... when processes survive the timeout supposed to kill them.

---

Authored by @dachary

tip: make your app.ini file resistant 💪 to upcoming @Gitea 1.17 breaking changes related to where expects to find its data. It is simple ✨ make sure all path related variables (ending with PATH for the most part) are explicitly set with an absolute path for your current app.ini.

Use github.com/go-gitea/gitea/blob as a checklist.

If want to know more read the in depth analysis of a regression involving APP_DATA_PATH hostea.org/blog/path-not-found

---

Authored by @dachary

Show older
Mastodon

A newer server operated by the Mastodon gGmbH non-profit