Hey #gitea instance admins. Do you have SSH for your Gitea instance enabled via OpenSSH? Then be aware that you should add `AcceptEnv GIT_PROTOCOL` to your `/etc/ssh/sshd_config` file! This enables Git Wire Protocol v2 for Git over SSH.

If you're using Gitea's Internal SSH Server, this behavior will be enabled in v1.17.1

Boost are are welcome for awareness.

Gitea 1.17.0 is released

We are proud to present the release of Gitea version 1.17.0, a relatively big release with a lot of new and exciting features and plenty breaking changes. We highly encourage users to update to this version after carefully reading about the breaking changes for some important bug-fixes.

645 Pull Requests were merged to release this version.

You can download one of our pre-built binaries from our downloads page - make sure to select the correct platform!

https://blog.gitea.io/2022/07/gitea-1.17.0-is-released/

#rss #gitea

The first of the @gitea 1.17 stable release was published a few hours ago. 🚀

Get ready to upgrade and make sure to check the "HOWTO Gitea upgrades, a guide for admins" published at before you do. ☘️

gitea.hostea.org/Hostea/admin-

---

Authored by @dachary

tip: the upcoming 1.17 release cannot be downgraded to 1.17.0-rc2

It is generally possible to downgrade from 1.17.x to 1.17.x-1 because there are no database migrations involved.

But there will be data migrations between 1.17.0-rc2 and 1.17 so that won't be an option. Once the upgrade is done, there is no turning back.

github.com/go-gitea/gitea/pull

---

Authored by @dachary

is looking for a co-founder with a business mindset 🌱 Someone who likes and , feeling adventurous and ready to bring to what @markosaric brought to @plausible

Very much looking forward to meeting you ❤️

forum.hostea.org/t/looking-for

---

Authored by @dachary

@hostea was created this year by @realaravinth and @dachary with the modest ambition of making redundant.

We would like Hostea to thrive as a in a post-growth economy. But we are geeks with no sense of business or marketing whatsoever.

Do you know someone who might be willing to team up and make this happen? A person who would bring balance to Hostea with a strong inclination for business development in a Free Software frame.

Boost appreciated 🚀

---

@dachary & @realaravinth

I wrote down my long term vision for . A constellation of forges, where Free Software is grown locally and organically 🌱

@forgefriends @gitea @hostea @forgefed @codeberg are pieces of this puzzle, each developed with ❤️

There is no need for mega forges with millions of projects and tenths of millions of people ruled by a centralized power. ☠️

They must vanish and make room for thousands of small forges communicating with each other. 🤝

blog.dachary.org/2022/07/21/ho

tip: @Gitea 1.17.0-rc2 is out and requires moving (again) a custom .gitconfig.

That's mostly relevant for production Gitea installations based on the Docker "latest" tag that unexpectedly got upgraded to the release candidate.

The Hostea blog post explains in details what happened and how to deal with the change.

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

---

Authored by @dachary

@forgefriends monthly update is 🗓️ July 20th 5pm UTC+2 and open to everyone.

* Software Development
* Collaboration with , ,
* Diversity
* Transparency and funding

forum.forgefriends.org/t/forge

tip: if you are running Gitea from docker 1.16 and wonder why you did not get the latest 1.16.9 yesterday, try again today.

The 1.16 tag was not updated and stayed on 1.16.8.

It has been manually updated today to match 1.16.9 (for amd64 only, not arm).

---

Authored by @dachary

is committed to provide hosting for @gitea instances with ActivityPub federation features enabled as soon as Gitea 1.18 is published.

It will also provide hosting for experimental @forgefriends and developer releases for everyone to try.

forgefriends.org/blog/2022/06/

---

Authored by @dachary

tip: obtaining the newly generated GPG key signing the Gitea 1.16.9 release may fail because the key server is unresponsive. The following oneliner will be useful to retry (in my case six times):

while : ; do if gpg --keyserver keys.openpgp.org --recv 7C9E68152594688862D62AF62D9AE806EC1592E2 2> /dev/null ; then echo success break ; else echo -n . ; fi ; done
......success

docs.gitea.io/en-us/install-fr

---

Authored by @dachary

tip: If you install the newly released Gitea 1.16.9 and get the following error message when verifying the signature of the binary:

gpg: Note: This key has expired!

It does not necessarily mean that it was compromised. The cryptographic key used to sign releases expired a few weeks ago and was not renewed yet.

If you run a highly sensitive Gitea instance (I know of at least two), you may want to wait until a new signature is issued.

docs.gitea.io/en-us/install-fr

---

Authored by @dachary

The "HOWTO Gitea upgrades, a guide for admins" moved to a repository: contributions are welcome 🚀

It previously was on a forum wiki page. But after a few months and 60+ edits, it became clear that regular updates will be necessary to keep up.

It was used to help with a few dozens upgrades and became the source of truths for Hostea system administration.

gitea.hostea.org/Hostea/admin-

---

Authored by @dachary

tip: the installation instructions in the @gitea documentation reference the 1.16.9 release that has not yet been published. It is an oversight that can be fixed by replacing 1.16.9 with 1.16.8.

$ wget -O gitea dl.gitea.io/gitea/1.16.8/gitea

docs.gitea.io/en-us/install-fr

---

Authored by @dachary

tip: the GPG key used to sign releases expired about two weeks ago:

$ gpg --list-key 7C9E68152594688862D62AF62D9AE806EC1592E2
pub rsa4096 2018-06-24 [SC] [expired : 2022-06-24]
<teabot@gitea.io>

It can however still be used to verify the integrity of the 1.16.8 release published a week before.

docs.gitea.io/en-us/install-fr

---

Authored by @dachary

@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

@team @humanetech @gitea @WoodpeckerCI @dachary

The tests run with

tox -e hostea

which essentially does the following:

* create the entire infrastructure from scratch (create the virtual machines, DNS, monitoring, the whole thing)
* run the Hostea playbooks
* run tests that verify common usage scenario

I think verifying the backup as you do is very valuable: there is nothing worse than a backup that cannot be restored 😨

lab.enough.community/main/infr

---

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.
...

Show older

Hostea Gitea Hosting & Clinic's choices:

Mastodon

A newer server operated by the Mastodon gGmbH non-profit