Newest at the top
| 2024-12-23 15:17:11 +0100 | <JuanDaugherty> | u could do plans for backup generations |
| 2024-12-23 15:15:22 +0100 | <JuanDaugherty> | a nice UI for rsnapshot would be great |
| 2024-12-23 15:15:22 +0100 | jero98772 | (~jero98772@31.130.32.65) (Quit: leaving) |
| 2024-12-23 15:14:13 +0100 | xff0x | (~xff0x@p3704193-ipxg12201sapodori.hokkaido.ocn.ne.jp) (Ping timeout: 248 seconds) |
| 2024-12-23 15:14:02 +0100 | <haskellbridge> | <magic_rb> A lot of my project fall into the same category but slightly different context |
| 2024-12-23 15:13:45 +0100 | <haskellbridge> | <magic_rb> Oh yeah but this is like a general problem |
| 2024-12-23 15:13:16 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) (Ping timeout: 252 seconds) |
| 2024-12-23 15:13:06 +0100 | <JuanDaugherty> | a plethora of tolls exist for most fs tasks |
| 2024-12-23 15:12:28 +0100 | manny_ | (~manny@45.134.142.209) |
| 2024-12-23 15:12:04 +0100 | <JuanDaugherty> | or just silverhammer, but u might wanna rethink hammering on ppls fs |
| 2024-12-23 15:11:32 +0100 | son0p | (~ff@186.121.98.118) son0p |
| 2024-12-23 15:11:20 +0100 | <JuanDaugherty> | as a monicker not an adjective |
| 2024-12-23 15:11:08 +0100 | <JuanDaugherty> | *then |
| 2024-12-23 15:11:03 +0100 | <JuanDaugherty> | maxwell them maybe (silverhammer) |
| 2024-12-23 15:10:33 +0100 | <haskellbridge> | <magic_rb> System |
| 2024-12-23 15:10:31 +0100 | <haskellbridge> | <magic_rb> Id call it a "given a current state of a system and a desired out, hammer it into shape" |
| 2024-12-23 15:09:21 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds) |
| 2024-12-23 15:08:55 +0100 | <JuanDaugherty> | i dunno from terraform so cant say; often in such cases a related name is used |
| 2024-12-23 15:07:46 +0100 | <JuanDaugherty> | absolutely, just checking |
| 2024-12-23 15:07:26 +0100 | <haskellbridge> | <magic_rb> Isnt this the haskell irc room (: |
| 2024-12-23 15:07:16 +0100 | manny_ | (~quassel@45.134.142.209) (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) |
| 2024-12-23 15:07:12 +0100 | <haskellbridge> | <magic_rb> Ofc |
| 2024-12-23 15:07:06 +0100 | <JuanDaugherty> | and ur gonna use haskell, right? |
| 2024-12-23 15:06:35 +0100 | <haskellbridge> | <magic_rb> So for those familiar with tmpfilesd, something like that, a bit less stupid and 100% less C |
| 2024-12-23 15:03:45 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-23 15:02:56 +0100 | <haskellbridge> | <magic_rb> The compare sounds like a good use case for gdiff. Then if i can make sense of the patch data type, i could form a plan by that |
| 2024-12-23 15:02:10 +0100 | <haskellbridge> | <magic_rb> I need suggestions, i want to eventually make a small prototype of a terraform like tool. Not sure what actual adjective id use, but the gist is that the tool would get the current state, in this case filesystem layout, get the desired state from a config file, compare the two, produce a plan, execute said plan |
| 2024-12-23 14:57:46 +0100 | simplystuart | (~simplystu@c-75-75-152-164.hsd1.pa.comcast.net) |
| 2024-12-23 14:55:39 +0100 | manny_ | (~quassel@45.134.142.209) |
| 2024-12-23 14:55:15 +0100 | manny_ | (~quassel@45.134.142.209) (Client Quit) |
| 2024-12-23 14:55:00 +0100 | JuanDaugherty | (~juan@user/JuanDaugherty) JuanDaugherty |
| 2024-12-23 14:52:40 +0100 | manny_ | (~quassel@45.134.142.209) |
| 2024-12-23 14:51:24 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
| 2024-12-23 14:49:08 +0100 | manny_ | (~manny@45.134.142.209) (Quit: Quit) |
| 2024-12-23 14:44:23 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-23 14:43:37 +0100 | hseg | (~gesh@46.120.21.36) |
| 2024-12-23 14:42:26 +0100 | systemhalted | (~systemhal@130.51.137.77) (Read error: Connection reset by peer) |
| 2024-12-23 14:42:25 +0100 | systemhalted | (~systemhal@130.51.137.77) systemhalted |
| 2024-12-23 14:41:21 +0100 | mange | (~user@user/mange) (Quit: Zzz...) |
| 2024-12-23 14:39:15 +0100 | jero98772 | (~jero98772@31.130.32.65) |
| 2024-12-23 14:38:27 +0100 | manny_ | (~manny@45.134.142.209) |
| 2024-12-23 14:38:06 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 272 seconds) |
| 2024-12-23 14:33:51 +0100 | forell | (~forell@user/forell) forell |
| 2024-12-23 14:33:10 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) merijn |
| 2024-12-23 14:32:45 +0100 | rvalue- | rvalue |
| 2024-12-23 14:25:43 +0100 | ensyde | (~ensyde@c-73-147-64-74.hsd1.va.comcast.net) ensyde |
| 2024-12-23 14:25:13 +0100 | rvalue | (~rvalue@user/rvalue) (Ping timeout: 252 seconds) |
| 2024-12-23 14:24:41 +0100 | rvalue- | (~rvalue@user/rvalue) rvalue |
| 2024-12-23 14:22:20 +0100 | merijn | (~merijn@128-137-045-062.dynamic.caiway.nl) (Ping timeout: 244 seconds) |
| 2024-12-23 14:20:26 +0100 | jero98772 | (~jero98772@2a00:1fa0:48a8:106e:59c5:719e:9cd2:863) (Read error: Connection reset by peer) |