[-] fhoekstra@feddit.nl 1 points 2 hours ago

I was just relaying how the OpenCloud people explained it to me at Froscon this year

[-] fhoekstra@feddit.nl 1 points 3 hours ago

Nice, I hadn't heard of that one yet!

[-] fhoekstra@feddit.nl 1 points 7 hours ago
  • Not affiliated.
  • Why did you use NextCloud over OwnCloud? Same reasons apply
[-] fhoekstra@feddit.nl 4 points 7 hours ago* (last edited 2 hours ago)

Thanks for your feedback!

Some thoughts:

  • You could configure your cliff.toml (generated with git-cliff --init) to ignore any commits that aren't interesting to your users
  • You could use "squash merge" to the prerelease/staging/development branch so that you can commit without worry, and then only have your PR titles follow conventional commits (if the change is interesting to your users)

I should probably add those to the blog.

But yeah, I get preferring to write manual tailored changelogs. Personally I am just a little neurotic about single source of truth and a huge Git nerd. And I know that at least in this job, my users are neurotic enough to prefer completeness.

[-] fhoekstra@feddit.nl 8 points 9 hours ago

Just like the old PHP based OwnCloud was forked to NextCloud for governance reasons, we now also have a fork of OCIS under the name OpenCloud:

https://opencloud.eu/

5
submitted 9 hours ago by fhoekstra@feddit.nl to c/rust@lemmy.ml

cross-posted from: https://feddit.nl/post/45839000

Automated changelog generation

When publishing a package for use by programmers, automated changelog generation is very beneficial. In this blog post, I explore how to do it in a simple way that works everywhere.

4

cross-posted from: https://feddit.nl/post/45839000

Automated changelog generation

When publishing a package for use by programmers, automated changelog generation is very beneficial. In this blog post, I explore how to do it in a simple way that works everywhere.

4

cross-posted from: https://feddit.nl/post/45839000

When publishing a package for use by programmers, automated changelog generation is very beneficial. In this blog post, I explore how to do it in a simple way that works everywhere.

14

When publishing a package for use by programmers, automated changelog generation is very beneficial. In this blog post, I explore how to do it in a simple way that works everywhere.

19
5

cross-posted from: https://feddit.nl/post/43404968

How-to: Cloudnative PG serving MongoDB with Automated Recovery from Continuous Backups

First post on my personal blog!

3

First post on my personal blog!

46

cross-posted from: https://piefed.social/post/1302658

PostgreSQL 18.0 Released With Async I/O, Performance Improvements - Phoronix

[-] fhoekstra@feddit.nl 2 points 1 month ago* (last edited 1 month ago)

AsyncIO, OAuth2 support, and a new wire protocol (for the first time since 2003)!

fhoekstra

joined 2 years ago