@ichbinniklasfischer
Probably using and a simple pipeline, then setup a webhost where you can push via SSH. Using Woodpecker Secrets, you can allow the CI to auto-deploy the website by pushing via SSH to your server.
@InfiniteLuke

@liaizon We weren't able to reproduce (no Apple customer at hand), but deployed a possible fix to codeberg-test.org. Please test there and report back if it changed anything.

@liaizon @mondstern We did test carefully on mobile and implemented a different mockup with mobile optimizations, not sure what happens there. 😮

Will forward ..

@Riedler
Just for the record, we switched the default to main before GitHub did, and we don't see any shame in stopping to use discriminative language.
@dminca @mray

@loke
Exactly, there are only baby-steps. First end-user visible features are expected in the next version.

Codeberg will probably enable federation with some careful testing delay. We also do careful staging / migration tests before every Gitea release.
@algernon
@mray

We just updated to 1.17. As always, please report any bugs to our Community Issue Tracker. A blog post introducing the most important changes will likely follow soon.

And special thanks to @mray for designing a new landing page for us. Implementation took us a while, and there is still a lot on our backlog regarding UI renovation, but we're on it 😊

@helby
Seriously guys, please don't expect a web app to implement a full IDE. Other uses do, that's probably why there are some pop over tooltips now (we're not talking about pop up windows).

If you don't like the web editor, please just run a normal editor on your operating system and use the native Git.
@hacknorris @mray

@Zergling_man
We do consider codeberg community-owned. There are many reasons to not self-host, because many lack the time, energy, money, ...

You can read more about that topic here: blog.codeberg.org/community-ma

But anyway, we're glad about everyone not relying on proprietary megacorps and appreciate people who still find the time to host things themselves.
@pichan

We just updated to 1.17. As always, please report any bugs to our Community Issue Tracker. A blog post introducing the most important changes will likely follow soon.

And special thanks to @mray for designing a new landing page for us. Implementation took us a while, and there is still a lot on our backlog regarding UI renovation, but we're on it 😊

I just found out that @codeberg ia doing custom domain for pages. So you can host your pages on Codeberg and use your own domain. Lot of people stuck with GitHub because it provided pages. Now a lot of people can move to Codeberg and become free from GitHub. Amazing news.

@akib @dachary @forgefriends @hostea @forgefed @gitea for the record, gitea open issues on this feature are

#2386
#13442

Please join the discussion and consider contributing a PR!

@akib @dachary @forgefriends @hostea @forgefed @gitea there is no reply-via-email feature in gitea yet (but open issues/feature requests?). To the best of our knowledge reply-to-issues-via-email only works for registered accounts? This would be different from what asked above (send requests without identity), and ofc a desired feature!

Contributions welcome!

Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!