chore(nix): replace rocksdb in flake.nix inputs #945

Merged

Jade merged 1 commit from Aviac/continuwuity:nix-rocksdb-derivation into main

2025-09-06 17:40:32 +00:00

Aviac commented

2025-08-26 14:03:37 +00:00

Contributor

Consuming this flake is pretty annoying since the rocksdb input is
fetched on every build which takes ~ 10 - 20 sec. By removing it and
replacing it with a pkgs.fetchFromGitea, we create an intermediate
derivation which is better for caching reasons and is also locked via the sha256.

Consuming this flake is pretty annoying since the `rocksdb` input is fetched on every build which takes ~ 10 - 20 sec. By removing it and replacing it with a `pkgs.fetchFromGitea`, we create an intermediate derivation which is better for caching reasons and is also locked via the sha256.

Aviac added 1 commit

2025-08-26 14:03:38 +00:00

feat(nix): remove rocksdb from flake.nix inputs

Documentation / Build and Deploy Documentation (pull_request) Has been skipped

Details

Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 11s

Details

3e18b183ba

Consuming this flake is pretty annoying since the rocksdb input is
fetched on every build which takes ~ 10 - 20 sec. By removing it and
replacing it with a `pkgs.fetchFromGitea`, we create an intermediate
derivation which is better for caching reasons.

Jade approved these changes

2025-08-26 15:57:32 +00:00

Jade left a comment

Owner

Looks all good to me, although how do I update the hash here? (ideally renovate would be able to handle it, once we get that working)

Aviac commented

2025-08-26 17:02:11 +00:00

Author

Contributor

Looks all good to me, although how do I update the hash here? (ideally renovate would be able to handle it, once we get that working)

I can look a bit more into that. No hurry to merge this. I think renovate doesn't support this kind of hash updating unfortunately. Maybe it's better to keep the rocksdb in the inputs then and accept the annoyances.

Anyways ... I'll research a bit more 👍

> Looks all good to me, although how do I update the hash here? (ideally renovate would be able to handle it, once we get that working) I can look a bit more into that. No hurry to merge this. I think renovate doesn't support this kind of hash updating unfortunately. Maybe it's better to keep the rocksdb in the inputs then and accept the annoyances. Anyways ... I'll research a bit more :+1:

Aviac changed title from ~~chore(nix): replace rocksdb in flake.nix inputs~~ to WIP: chore(nix): replace rocksdb in flake.nix inputs

2025-08-26 17:02:21 +00:00

Jade commented

2025-08-26 17:06:19 +00:00

Owner

No, it's fine (we already have the hash for the toolchain, for example), it's just "how is this going to stay working", which is an open question for the rest of the nix stuff too

Aviac commented

2025-08-27 06:59:19 +00:00

Author

Contributor

No, it's fine (we already have the hash for the toolchain, for example), it's just "how is this going to stay working", which is an open question for the rest of the nix stuff too

I'm going to dogfood this really hard. It's also built by my personal hydra (CI) so we'll notice if something goes wrong or old.

> No, it's fine (we already have the hash for the toolchain, for example), it's just "how is this going to stay working", which is an open question for the rest of the nix stuff too I'm going to dogfood this really hard. It's also built by my personal hydra (CI) so we'll notice if something goes wrong or old.