!UKDpaKNNsBpOPfLWfX:zhaofeng.li

Colmena

291 Members
A simple, stateless NixOS deployment tool - https://github.com/zhaofengli/colmena97 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
19 Jun 2023
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.name although now it objects to specialArgs = { inherit inputs }; 06:01:16
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.nameer, forgot the closing ;06:01:30
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.name inputs is undefined within the body of the outputs fn 06:01:54
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.name does it need to be self.inputs? 06:02:05
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.nameor I guess I could just pass in the flake I care about in the outputs fn and then pass that as a special arg, I only need 2 or 3 flakes06:02:29
@zhaofeng:zhaofeng.liZhaofeng Li Ah, you do something like outputs = { self, nixpkgs, ... } @ inputs: { ... } 06:02:30
@zhaofeng:zhaofeng.liZhaofeng Li The @ inputs will bind the entire set as inputs 06:02:46
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.name @ syntax works on either side of the fn input set, right? 06:02:52
@zhaofeng:zhaofeng.liZhaofeng Liyes06:02:57
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.nameI'm not sure why they needed to implmenet it both ways06:03:17
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.nameanyway that seems to work06:03:19
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.nameand that did update my flake.lock06:03:35
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.namewith actually kind of a lot of stuff. I set up that flake I'm importing myself, like two days ago, I may not have done it correctly06:04:23
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.namebut in any case I can deploy06:04:25
@rendakuenthusiast:imperishable.name@rendakuenthusiast:imperishable.namethanks for your help!06:04:29
22 Jun 2023
@h4636oh:matrix.org@h4636oh:matrix.org joined the room.02:47:16
@h4636oh:matrix.org@h4636oh:matrix.org left the room.03:37:55
@a-kenji:matrix.orgkenji joined the room.05:55:29
@palo:xaos.space@palo:xaos.space

I'm sketching an Architecture for a service in an openstack cluster, which consists of multiple machines (and there will be new machines every now and than). I would like to have one machine that shares it's /nix/store with all the other instanzes in the cluster. That is not a problem. I have a mono repository and would like to build all machines (not deploy) and nix-copy-closure the resulting closures to this machine. Meaning the build server (which is not the cache server) is in a loop while true; git pull ; colmena build ; nix-copy-closure ???? private_cache_server How to find all closures that need to be copied?

08:12:45
@whentze:matrix.orgWanja Hentzewould you even be using colmena then? sounds more like you'd be reimplementing it08:14:48
@palo:xaos.space@palo:xaos.space

I want to use colmena. Because we would not deploy all machines instantly.

08:15:40
@palo:xaos.space@palo:xaos.space

I just want to enrich the cache.

08:16:07
@whentze:matrix.orgWanja Hentzeoh, cache warming08:16:37
@palo:xaos.space@palo:xaos.space

All machines have a very similar base setup, and updates should be pulled from the cache, to avoid uploading 50 times the same closures from my office to the data center.

08:18:00
@whentze:matrix.orgWanja Hentzethen why not use `colmena apply push`08:18:07
@palo:xaos.space@palo:xaos.space
In reply to @palo:xaos.space

All machines have a very similar base setup, and updates should be pulled from the cache, to avoid uploading 50 times the same closures from my office to the data center.

(I answered before you asked :D)

08:20:52
@palo:xaos.space@palo:xaos.spaceThe only solution I found so far is, a cache server that also creates the builds.08:21:33
@palo:xaos.space@palo:xaos.space

(and use the buildOnTarget option)

08:21:59

Show newer messages


Back to Room ListRoom Version: 6