New post: Migrating my repositories to Forgejo
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
This commit is contained in:
parent
199f07d0dd
commit
0fa88d8007
1 changed files with 48 additions and 0 deletions
|
@ -1,5 +1,53 @@
|
|||
#+hugo_base_dir: ../
|
||||
|
||||
* DONE Migrating my repositories to Forgejo :english:selfhost:free_software:
|
||||
CLOSED: [2024-02-24 Sat 23:51]
|
||||
:PROPERTIES:
|
||||
:EXPORT_FILE_NAME: migrating-to-forgejo
|
||||
:END:
|
||||
|
||||
After some thought, I decided to migrate my repositories to [[https://forgejo.org][Forgejo]].
|
||||
I know, I know... The name sucks a little bit, but nothing is
|
||||
perfect. Forgejo is a fork of [[https://gitea.com][Gitea]], and was created after [[https://gitea-open-letter.coding.social/][some drama]]
|
||||
regarding Gitea Ltd taking over the development of the Gitea project.
|
||||
I have to be honest and say that I'm growing tired of seeing so much
|
||||
drama and confusion arise from Free Software communities and projects,
|
||||
but in a way this is just a reflection of what's happening with the
|
||||
world in general, and there's very little I can do about it. Anyway.
|
||||
|
||||
Deploying Forgejo was easy thanks to [[https://github.com/mother-of-all-self-hosting/mash-playbook][mash-playbook]], which is a project
|
||||
I've been using more and more to deploy my services. I like how
|
||||
organized it is, and the maintainer is pretty responsive. On top of
|
||||
that, learning more about Ansible had been on my TODO list for quite a
|
||||
while.
|
||||
|
||||
All of this means that I decided to move /away/ from [[https://sr.ht][Sourcehut]] (I
|
||||
might use it as a mirror for my public repositories, though). I did
|
||||
that because I wanted to self-host my git forge again (I've been doing
|
||||
that for more than a decade if you don't count my migration to
|
||||
Sourcehut last year). Not liking some of Sourcehut's creator's
|
||||
opinions (and the way he puts them out there) may or may not have
|
||||
influenced my decision as well.
|
||||
|
||||
** A Continuous Integration to rule them all
|
||||
|
||||
Something that I immediately missed when I setup Forgejo was a CI. I
|
||||
don't have that many uses for it, but when I was using Sourcehut I
|
||||
setup its build system to automatically publish this blog whenever a
|
||||
new commit was made to its git repository. Fortunately,
|
||||
=mash-playbook= also supports deploying [[https://woodpecker-ci.org/][Woodpecker CI]], so after
|
||||
fiddling during a couple of days with the Forgejo ↔ Woodpecker
|
||||
integration, I managed to make it work just the way I wanted.
|
||||
|
||||
** Next steps
|
||||
|
||||
Write more :-). Really... It's almost as if I like more to deploy
|
||||
things than to write on my blog! Which is true, but at the same
|
||||
isn't. I've always liked writing, but somehow I grew so conscious of
|
||||
what to publish on this blog that I'm finding myself avoiding doing it
|
||||
at all. Maybe if I try to change the way I look at the blog I'll get
|
||||
motivated again. We'll see.
|
||||
|
||||
* DONE Using WireGuard to host services at home :english:howto:selfhost:wireguard:debian:
|
||||
CLOSED: [2023-05-23 Tue 00:56]
|
||||
:PROPERTIES:
|
||||
|
|
Loading…
Reference in a new issue