You could always just setup your nextcloud directory to be network mountable
Though I’ve found badness comes from trying to modify nextcloud’s filesystem from outside nextcloud
Nixos is great for self hosting. The declarative part is obviously very useful but people have talked to death about that
Have nixos on my pi, to install and configure nextcloud, I just paste in a block to my config, rebuild, and it’s up and running
Most things seem to have built in nix options for them so there’s super easy to install and configure, no faffing around with having to add ppas, set things up as services, spend any amount of time remembering what you have installed
Sad to have to use Debian instead on my pi 5 because nix wasn’t ready when I got it
If there’s nothing about it in nix option search your best bet is just to put the regular config file in your nix repo and have it map it in where it’s meant to go
Ah right didn’t realise there was a nix version of it, will have a look
I’ve found the best way to use python under nix is not to use nix for its packages because not all of its libraries are in nixpkgs
Requirements.txt and a venv still work on nixos the same way they would on a normal system
It looks to me like a way to declaratively install your ssh keys which from what I’m reading sops doesn’t appear to do
Am I wrong in taking the conclusion SOPS stores that stuff encrypted at rest, and the only way to use them is either through the SOPS cli, or through whatever tool that wants the secrets implementing their library?
Looks cool, but why use yaml? I never understand why people choose to use yaml as their configuration format
Gonna have to give this a go seems way easier than using the website
That’s what home manager bash/fish/zsh rc config is for
You can import unstable as a package override
I’ve had it in the past where I can specify in the package name (like pkgs.unstable.chromium). You’ll be able to do the same with service options as most allow you to set the package they use with a config option
I think I did, but I since got a new controller anyway so can’t be sure. I switched to the latest kernel and it worked for the new one
Can vagrant do windows well? Was under the impression it wasn’t really meant for it and not sure how licensing would work for the windows instance
Currently using the key built into my machine, if there’s a way to automatically pull that and shove it into the VM that would be perfect
I’m looking to do this with nix config, would rather not mix and match if at all possible
Yeah, definitely works on other distros it’s NixOS specific
Ah right, I’ll probably just install pop in a VM or something and try it that way then (and/or wait for it to be a nix option)
Probably not stable enough to replace gnome anyway if it’s prealpha, had thought it had released for some reason