@samuteki It would be fantastic to get a new logo for the Gna! résurrection. 😍
---
Authored by: @dachary
Hostea Gitea Hosting & Clinic
The Clinic is open and doctors are focusing on helping admins #troubleshoot #issues related Gitea #upgrade. Dedicated Gitea hosting is still in alpha and actively developed.
Hostea is committed to implement #forge #federation features as soon as they are available from #forgefriends, #forgeflux or Gitea.
This Hostea mastodon account is operated by Hostea members and each toot is signed by its authors.
Hostea Gitea Hosting & Clinic boosted:
Gitea 1.17.1 is released
We are proud to present the release of Gitea version 1.17.1.
We highly encourage users to update to this version for some important bug-fixes.
We have merged 35 pull requests to release this version.
Thanks to the security researcher who reported the security issue in this release, and @zeripath for the fix!
You can download one of our pre-built binaries from our downloads page - make sure to select the correct platform! For further details on how to install, follow our installation guide.
https://blog.gitea.io/2022/08/gitea-1.17.1-is-released/
#rss #gitea
Hostea Gitea Hosting & Clinic boosted:
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 #Hostea before you do. ☘️
https://gitea.hostea.org/Hostea/admin-guide/
---
Authored by @dachary
#Hotea 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.
---
Authored by @dachary
#Hostea is looking for a co-founder with a business mindset 🌱 Someone who likes #Zebra and #postgrowth, feeling adventurous and ready to bring to #Hostea what @markosaric brought to @plausible
Very much looking forward to meeting you ❤️
https://forum.hostea.org/t/looking-for-a-co-founder-with-a-business-mindset/151
---
Authored by @dachary
@hostea was created this year by @realaravinth and @dachary with the modest ambition of making #GitHub redundant.
We would like Hostea to thrive as a #Zebra 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 🚀
---
#Hostea 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.
https://hostea.org/blog/1-17-breaking-episode-2/
---
Authored by @dachary
#Hostea 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
#Hostea 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 #ForgeFlux developer releases for everyone to try.
https://forgefriends.org/blog/2022/06/30/2022-06-state-forge-federation/
---
Authored by @dachary
#Hostea 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
https://docs.gitea.io/en-us/install-from-binary/#verify-gpg-signature
---
Authored by @dachary
#Hostea 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.
https://docs.gitea.io/en-us/install-from-binary/#download
---
Authored by @dachary
The #Hostea "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.
https://gitea.hostea.org/Hostea/admin-guide/src/branch/master/README.md
---
Authored by @dachary
#Hostea 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 https://dl.gitea.io/gitea/1.16.8/gitea-1.16.8-linux-amd64
https://docs.gitea.io/en-us/install-from-binary/#download
---
Authored by @dachary
#Hostea 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.
https://docs.gitea.io/en-us/install-from-binary/#verify-gpg-signature
---
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:
https://hostea.org/blog/1-17-breaking-episode-1/
---
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 😨
---
Authored by @dachary
The first version of the #Hostea "HOWTO #Gitea 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 ✨
https://forum.hostea.org/t/howto-gitea-upgrades-a-guide-for-admins/39
---
Authored by @dachary
#Hostea 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 https://forum.hostea.org/t/gitea-downgrade-from-1-17-0-rc1-to-1-16-9-on-june-22-2022/105
---
Authored by @dachary
#Hostea 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.
https://forum.hostea.org/t/howto-gitea-upgrades-a-guide-for-admins/39
---
Authored by @dachary
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst