We plan to move Fluxer's code from GitHub to a Forgejo site that we run ourselves, and to build Fluxer on our own machines and publish its container images from our own registry. We haven't set a date, and until we move, everything on GitHub stays as it is.
Will Fluxer keep using GitHub?
For now, yes. The code for the server, web app and desktop app is in fluxerapp/fluxer on GitHub, and the code for the iOS and Android apps is in fluxerapp/flutter_client. Pull requests, most builds, desktop releases and container images are on GitHub too.
In the future, we want all of that on a Forgejo site that we run ourselves. Forgejo is free and open source software for hosting code, and it works a lot like GitHub.
Why is Fluxer moving to Forgejo?
We want the tools we build Fluxer with under our own control in Sweden and the EU, without depending on a US company. It's the same reason we're moving fluxer.com to our own hardware in Sweden. Forgejo is open source, and we can run it ourselves.
Fluxer is a Swedish company with no outside investors, and we want it to stay independent. Running the tools we make Fluxer with ourselves is part of that.
Will Fluxer run its own CI and container registry?
Yes, that's the plan. Today most of our builds run on GitHub Actions, and the container images are published to GitHub's container registry at ghcr.io/fluxerapp. We plan to run builds on our own machines and publish the images from our own registry.
Desktop downloads and their checksums are already on our own site, pkgs.fluxer.com, and we run our own apt, dnf, pacman and Flatpak repositories for Linux. Bug reports and feature requests go to Fluxer Feedback, and translations go through Fluxer's Weblate.
What changes for contributors?
Code contributions will move from pull requests on GitHub to pull requests on our Forgejo site, and we'll explain how to send your own changes there before we move. Until then, you can contribute on GitHub in the same way as you do today.
Bug reports and feature requests stay on Fluxer Feedback, where you sign in with your Fluxer account. To translate Fluxer, you sign up for Fluxer's Weblate with a GitHub account today, and we're looking into letting you sign in with your Fluxer account.
What changes for people who self-host Fluxer?
Today rexctl downloads its files from fluxer.dev, and Fluxer's container images come from ghcr.io/fluxerapp. When we move, the images will come from a registry that we run, and the operator docs and patch notes will say what you need to change, if anything.
Self-hosting Fluxer stays free, with no license key, paid tier or reduced edition, and the move to Forgejo doesn't change what Fluxer gets from your instance.
Will the move change how I check a Fluxer download?
No. Our download page and pkgs.fluxer.com stay the places to download the desktop app, with a SHA-256 checksum next to each download. Windows releases are signed in the name of Fluxer Platform AB, and our Linux repositories are signed with our archive key.
The desktop releases that are on GitHub today will move to our Forgejo site with the rest of the code. Here's how to check a download before you install it.
What stays the same after the move?
Fluxer stays free and open source under the AGPL, and anyone can run, study, change and share it. Contributors keep the copyright in their work, add a Developer Certificate of Origin sign-off to each commit they send and don't sign a CLA.
When will Fluxer leave GitHub?
We haven't set a date, and we'll update this page when we have one. Until then, the code, pull requests, releases and container images stay on GitHub.