| 22 Feb 2024 |
 Adrian | In reply to @mayel:matrix.org
Yeah but always talking tech in English so it may be a challenge 😅 Oh okay! It's alright then don't worry ❤️ | 21:43:21 |
| 27 Feb 2024 |
| Adrian | any ETA on the bonfire 1.0 by the way? 🙏 | 14:18:38 |
|  rvlobato joined the room. | 14:49:28 |
 Mayel | Difficult to say, we’re working on it while also dedicating part of our time to make the project sustainable… The best indicator would be looking at the milestones here (there will be two release candidates before the 1.0): https://github.com/bonfire-networks/bonfire-app/milestones?direction=asc&sort=title&state=open | 15:08:25 |
| Mayel | On that topic, today we’re introducing the Open Science Network https://indieweb.social/@bonfire/112003756663690626 | 15:09:08 |
| Adrian | Thanks! | 15:27:15 |
| 29 Feb 2024 |
|  adrian ⚡️ joined the room. | 17:15:15 |
| adrian ⚡️ | Allo! Does anyone happen to have a working flake/configuration.nix for deploying bonfire? | 18:44:06 |
| adrian ⚡️ | Working on getting a little test instance working on a raspberry pi | 18:44:21 |
| adrian ⚡️ | Love the project ;) | 18:44:24 |
| adrian ⚡️ | * Love the project :) | 18:44:29 |
| Mayel | In reply to @adrian:lorenzana.engineering
Allo! Does anyone happen to have a working flake/configuration.nix for deploying bonfire? There is one in the repo that a couple put together but it's a WIP and probably flaky ;) More recently someone added a guix config as well. | 18:50:52 |
| Mayel | In reply to @adrian:lorenzana.engineering
Working on getting a little test instance working on a raspberry pi Let us know how it goes! Have done it before and it runs fine, the slowest part is compilation (unless you're able to compile on another device or CI with same arch and distro) | 18:52:16 |
 aynish | i was the one developing the flake.nix in the repo, but it's borked af afair | 18:52:46 |
| aynish | i'm looking to pick that back up and ideally get it working for all flavours later this month! | 18:53:05 |
| aynish | would love for you to take a look / help out if you're interested in that :) | 18:53:42 |
| Mayel invited  fishinthecalculator. | 18:54:55 |
| Mayel | I wonder how much overlap there is / can be with the guix set up? I just invited the person in question | 18:55:37 |
 Ryuno-Ki (André Jaenisch) | In reply to @aynish:sealight.xyz
i'm looking to pick that back up and ideally get it working for all flavours later this month! Are you in March already? | 18:55:48 |
| Mayel | I think they used the docker containers rather than comping for bare elixir | 18:56:09 |
| aynish | there's probably a fair amount of overlap, but i'd need to look at the guix src to be sure | 18:56:37 |
| aynish | In reply to @Ryuno-Ki:matrix.org
Are you in March already? haha, no, i mispoke | 18:57:05 |
| aynish | In reply to @mayel:matrix.org
I think they used the docker containers rather than comping for bare elixir oh, that's less interesting. i'm hoping to compile / build for bare elixir | 18:57:25 |
| adrian ⚡️ | In reply to @aynish:sealight.xyz
would love for you to take a look / help out if you're interested in that :) Gotchca! I'll try and give a look through the repository flake soonish :) | 19:30:22 |
| fishinthecalculator joined the room. | 19:47:15 |
| fishinthecalculator | hi all I just read the discussion about nix/guix. for deploying on guix i wrote a Guix System service. for building bonfire with guix provided dependencies i added some logic .envrc . both the service and the dev environment now use docker provided dependencies to avoid packaging all of bonfire's dependencies. i'm planning to do that sooner or later but it is its own can of worms. aynish pretty cool work with the flake. did you manage to package all of the dependencies? | 19:55:28 |
| fishinthecalculator | * hi all I just read the discussion about nix/guix. for deploying on guix i wrote a Guix System service. for building bonfire with guix provided dependencies i added some logic in the .envrc . both the service and the dev environment now use docker provided dependencies to avoid packaging all of bonfire's dependencies. i'm planning to do that sooner or later but it is its own can of worms. aynish pretty cool work with the flake. did you manage to package all of the dependencies? | 19:55:43 |
| aynish | that's where the problems mostly began. it's been a few years but iirc i'm able to get a FOD with the dependencies, but it's fragile to changes. I looked into mix2nix solutions, but none at the time supported git dependencies which bonfire uses a lot of, and that's about all I remember right now | 19:58:06 |
| fishinthecalculator | * hi all I just read the discussion about nix/guix. for deploying on guix i wrote a Guix System service. for building bonfire with guix i added some logic in the .envrc . both the service and the dev environment now use docker provided dependencies to avoid packaging all of bonfire's dependencies. i'm planning to do that sooner or later but it is its own can of worms. aynish pretty cool work with the flake. did you manage to package all of the dependencies? | 19:58:36 |
| fishinthecalculator | i know one Guix dev has implemented something like mix2nix which should parse lockfiles and generate in-memory guix packages that can be then built, but it is still early work I'd say. also i don't know if it would support git dependencies. i guess in theory it could but should see the implementation first | 20:01:07 |
