| 18 Aug 2022 |
 Paul Tiplady | I hear a lot of people preaching on HN about how nice it is, and I see the appeal of setting up developer environments and CI/CD pipelines. I found that on MacOS at least, every 6 months my "new developer" guide for my team broke because of some library/OS change, and I am interested to see if doing things immutably, the Nix way, would be better.
Currently my dev env stack is (MacOS): pyenv, pyenv-virtualenv, poetry (would switch if other packaging systems integrated better), PyCharm. I use yarn and webpack for JS stuff. And everything goes into a Docker container and gets deployed to Kubernetes. While I'm mostly writing Python I just followed the example in the docs.
I have Docker as my "blessed environment" for builds and CI/CD, but it's annoying to ask developers to use Docker for their local dev loop. So we have two different env setups, one for local dev, and one for CI/CD build and prod deploy. | 03:51:54 |
| Paul Tiplady | I'm familiar with the git toolchain. | 03:52:28 |
 tpw_rules | and presumably some form of git hosting service? | 03:54:53 |
| Paul Tiplady | Yes, I've run projects on Github and Gitlab in the past | 03:55:08 |
| tpw_rules | one last random sounding question: do you use apple silicon macs? | 03:56:00 |
| tpw_rules | * one last random sounding question: do you use apple silicon macs? (and is that where you ran your niv command)? | 03:56:09 |
| Paul Tiplady | Nope, I'm currently on an old (Circa 2014) MBP. | 03:58:13 |
| tpw_rules | okay, thank you very much for coming here to share your experience. i did want to do some further opining on how i use nix, but this isn't really the place. do you want to join the main channel https://matrix.to/#/#nix:nixos.org or PM me? | 04:02:28 |
| Paul Tiplady | I have to sign off for the eve -- I'll check back in here if I get further with this. And thanks for the offer -- I'll ping you. | 04:06:46 |
| tpw_rules | okay, good luck. my first piece of advice is don't use nix-env -qaP for a variety of reasons. use this: https://search.nixos.org/packages | 04:07:48 |
 Sandro 🐧 | In reply to @tpw_rules:matrix.org
Sandro 🐧: nix-env -qaP is definitely a thing to take out in your "sync with best practices" PR Then I would need to replace those parts and I am not fast at waiting documentation. | 11:38:59 |
| 19 Aug 2022 |
 Solène Rapenne (she/her) | that's cool, someone wrote https://nixos.wiki/wiki/Specialisation after my tweag blog post. I added this section because it's a very useful use case but totally impossible to figure out (infinisil found how to do that). Could someone tell me if it's understandable? https://nixos.wiki/wiki/Specialisation#Special_case:_the_default_non-specialised_entry | 20:10:50 |
 Jan Tojnar | In reply to @rapenne-s:tchncs.de
that's cool, someone wrote https://nixos.wiki/wiki/Specialisation after my tweag blog post. I added this section because it's a very useful use case but totally impossible to figure out (infinisil found how to do that). Could someone tell me if it's understandable? https://nixos.wiki/wiki/Specialisation#Special_case:_the_default_non-specialised_entry It reads okay to me. Though does it need to be a new file? I would expect including the expression inline into the imports, or just anywhere using mkIf to work fine. | 21:17:09 |
| Jan Tojnar | Also the config will also apply to specializations containing specializations (not sure if that is a thing). | 21:18:22 |
| Solène Rapenne (she/her) | Jan Tojnar yes this can be inline within the imports but I find it very not practical | 21:54:52 |
| Solène Rapenne (she/her) | I dunno if it could be possible to cover specialisation in man configuration.nix ? | 22:05:18 |
 linj | In reply to @rapenne-s:tchncs.de
that's cool, someone wrote https://nixos.wiki/wiki/Specialisation after my tweag blog post. I added this section because it's a very useful use case but totally impossible to figure out (infinisil found how to do that). Could someone tell me if it's understandable? https://nixos.wiki/wiki/Specialisation#Special_case:_the_default_non-specialised_entry cool, config.specialisation != {} is a clever hack! I used to use mkRemove to remove items from a list in specialisation. | 22:16:44 |
| Jan Tojnar | In reply to @rapenne-s:tchncs.de
Jan Tojnar yes this can be inline within the imports but I find it very not practical I am somewhat worried about perpetuating the misconception that files are something special (I have seen newcomers confused by this) but I am not how to formulate it better without it becoming too clumsy or more confusing | 22:43:07 |
| Solène Rapenne (she/her) | I still don't understand why the code can't be put into configuration.nix ^^' so I used a file to keep things clean instead of a big chunk into imports | 22:43:56 |
| 20 Aug 2022 |
|  b-eric-d joined the room. | 02:33:32 |
|  kayla (she/they) joined the room. | 17:25:18 |
| 21 Aug 2022 |
|  greaka changed their display name from greaka ⚡️ to greaka . | 09:25:58 |
|  jurraca changed their display name from jurraca to jeak. | 18:08:54 |
| 22 Aug 2022 |
|  Johann Eicher joined the room. | 09:18:22 |
| 23 Aug 2022 |
|  Echo joined the room. | 00:49:38 |
|  psibi joined the room. | 12:46:30 |
|  raphi joined the room. | 18:55:49 |
| 24 Aug 2022 |
|  portothree joined the room. | 13:29:50 |
|  underpantsgnome! changed their display name from tinybronca to underpantsgnome. | 23:02:24 |
| 25 Aug 2022 |
|  shanesveller joined the room. | 15:32:54 |
