How should I proceed? Did I miss that in the docs?
You did not miss it, we should provide some documentation around this.
In short, the packages are gone, but the metadata which defines your environments is not.
The easiest way to recover your environments would be to push your environments up to github via flox push and flox pull them back down (docs). I’d recommend stashing your environments this way, never know when (or where) you may need them .
Another way to recover is to run flox edit to edit your manifest. Currently editing the manifest will force an upgrade to all packages in the environment, effectively re-rendering the env locally (adding a whitespace will suffice). If you don’t want to upgrade, go with the first option.
Can we exclude packages from GC that are referenced by flox?
Not currently, but we are working on handling GC better and should have some updates on this front soon. Look out for the release notes.
Thanks for checking back! Is Gitlab supported for hosting environments? If not, how can I re-configure flox push? It let me choose Gitlab from a list, but it seems Gitlab can’t be configured e.g. via flox gl auth login, so now it appears it always wants to push to Gitlab - I did the Github auth after selecting Gitlab from that list…
GitLab is supported, but we don’t ship the GitLab CLI with flox like we do with gh.
In the third step here, it asks you to confirm the URL, and you should input the gitlab URL, not the default.
If you haven’t messed with your config too much, a flox config --reset should be harmless and get you out of that loop. Just go back to flox push and with the prompt select GitLab, HTTPS, and the GitLab URL.
You’ll need to set up the GitLab token or similar auth in your shell somehow.
OK, sorry about that.
You can actually check your remote for the floxmeta repo with flox git remote -v.
And you can then replace the origin with git as you would with git (flox git remote add origin https://gitlab.com/myrepo).
Let me know if that doesn’t sort you out.