mastodon.ar.al is one of the many independent Mastodon servers you can use to participate in the fediverse.
This is my personal fediverse server.

Administered by:

Server stats:

1
active users

#gitea

4 posts4 participants0 posts today

If you, like me, are incredibly excited by this wonderful news, know that —at least for now— you can disable all this #Copilot crap by visiting github.com/settings/copilot and switching all the options to Disabled/Blocked. Perhaps especially the on-by-default "Allow GitHub to use my data for product improvements" one.
Thanks to #GitHub for reminding me how glad I am for #SelfHosting my own #Gitea #Git #Forge. If you're not already, maybe consider it or a (partial) move to #Codeberg too. It's great!

Anyone done a #Gitea to #Forgejo migration? Is the guide on the Forgejo site sufficient documentation?

ETA: I was one version too far to do the database compatible switchover, but it was easy enough to install, configure, and reimport my repos.

🌱 Il futuro è decentralizzato, passo dopo passo

Anche Organic Maps, l'app #opensource per navigare senza tracciamento, abbandona #GitHub di Microsoft e sceglie piattaforme self-hosted. Un segnale forte: sempre più progetti scelgono autonomia dai #BigTech.

🚀 Per chi vuole seguire questa via, su gitea.it è ora disponibile una guida aggiornata con tutti i client e le app per usare Gitea al 100%:

🔗 Scopri la guida qui: gitea.it/Gitea/Gitea-Italia

:diggita: @opensource@diggita.com

GiteaGiteaGitea (Git with a cup of tea) is a painless self-hosted Git service written in Go

Hi everyone, GitNex 8.0.0 is now out with numerous new features and UI refinements.

- User activity heatmap on the profile
- Dependencies for issues and prs
- Tracked time for issues and prs
- Search within files
- Filter issues by labels
- Filter issues where I am mentioned
- and more...

It's time to update! 🎉

Release notes: codeberg.org/gitnex/GitNex/rel

Summary card of repository gitnex/GitNex
Codeberg.orgGitNexAndroid client for Forgejo(https://codeberg.org), Gitea(https://gitea.com) [OR your custom hosted server]
Replied in thread

@liaizon @ojack @yala
@Codeberg @forgejo

+1 for #codeberg

but all "auxiliary" data—issues, prs, tasks, everything that's not `.git`—remains pretty much siloed within a particular server. afaik no forge lets you export those

otoh there is "import": repo mirroring in #gitea/ #forgejo works well. afterwards you set the repo to be a non-mirror. won't help migrate a community tho—it's instantaneous switchover

the real game-changer would be #forgefed forgefed.org/ but no news on that🙁

forgefed.orgForgeFed

Migrated my self-hosted code repo from #gitea to #forgejo, the best time to do it was before upgrading gitea to 1.23.0, the next best time is now

Seriously, upgrading a gitea 1.22.0 (docker) to latest forgejo is literally just changing the base docker image and restarting the service, but any ulterior gitea version won't be officially supported by forgejo for a seamless migration and may require lots of fiddling (if at all possible), or otherwise require exporting/reimporting the repos.

Don't be lazy!

A short PSA: Gitea's newest Helm Chart, 11.0, switches from DockerHub to docker.gitea.com for the Gitea image. A good thing of course, but you might want to configure your internal cache to cache docker.gitea.com as well, to be a good neighbour and not hammer their infra too much.

For some reason I can't SSH from my laptop to my #Gitea server via its public interface. It just keeps timing out. It's only the laptop having this issue; my tablet and phone are doing this just fine. I was finally able to push my commits by sending them directly over the LAN instead. I've tried resetting the VPN on the laptop, but it's still not working normally.

I am officially confused.

Edit: Mystery solved. I forgot to pay my VPN provider... again.

If you run a #Drone CI server, set DRONE_REGISTRATION_CLOSED=true (and manually create users only when you really really trust someone).

The CPU on my CI/CD server suddenly spiked to 100% today.

A closer look found some users who had registered on git.platypush.tech and on the CI/CD server and created a repo with a .drone.yml, a .gitlab-ci.yml and some scripts with base64-encoded commands.

The repo also contains a deepCC.ipynb Jupyter notebook that downloads some training data from S3 and uses Tensorflow to train a model, and then uses the deepCC binary to do something with that model.

The repository also has a configure script with base64-encoded commands that seem to configure a miner (the wallet ID is R9WpFbvkb6dep6bfLdbpcyz3LpMeikUL6W and the coin is VRSC, if anyone is interested in investigating further).

The deepCC binary is itself quite big (~50 MB), and a look at the setup script reveals that it’s actually a .tar.gz archive with a larger binary inside.

A quick run of strings on the binary confirms that it’s actually a miner - it connects to eu1-etc.ethermine.org and it also has a bunch of CUDA bindings to run on GPUs.

I still don’t get what’s the point of the Jupyter notebook that trains a model and passes it to this miner, but if you feared the day of the arrival of the zombie Docker containers that exhaust system resources by mining cryptocrap AND training AI models, well, I’m afraid to inform you that that day has come.

If you are a #Gitea / #Forgejo admin, take a look at the users and repos created in the past couple of weeks. Check in particular if any recently registered users have created a repo named deepcc-v.

The most likely authors are users named farzanfarid16 and zurizoey0.

A quick search confirms that both these users are registered on #Gitea too and have already created the incriminated repo:

And if you are a Drone CI or #Gitlab admin, check if any of these users have also started CI/CD pipelines connected to that repo.

For now, disabling the execution of CI/CD pipelines unless a user has been explicitly authorized is the best idea that comes to my mind.

Platypush GitPlatypush GitForgejo is a self-hosted lightweight software forge. Easy to install and low maintenance, it just does the job.
Replied in thread

@chicraote @maiwann

Merci !

Savez-vous s'il est compatible avec notre ZGit = #gitea ?

Et, désolé je ne suis pas de l'équipe technique, c'est probablement une question bête, comment nos abonné.e.s y accèderaient ? Il y a une partie login et l'API pour discuter avec notre système ?

On peut personnaliser avec son propre nom de domaine ? Ça aussi c'est demandé la plupart du temps.