4 ms·
It would be nifty to save out "try"s in a sqlite/whatever and then curl install tries on other systems - such that you can easily clone certain setups between m
by samstave 3y ago
It would be nifty to save out "try"s in a sqlite/whatever and then curl install tries on other systems - such that you can easily clone certain setups between machines on a small/home network.
Also, if you can name tries, install-stacks - such that you can do "Try --name 'homeWebSever' [then do your tries here]
Then go to another machine and from your try repo, just type 'try install --name homeWebServer -- and it does whatever your try stack was
- JadeNB 3y agoFrom my cursory understanding (based solely on the README), it seems that `try`s are just directories, so that they can automatically be slung around, without any need for a backing database: > Sometimes, you might want to pre-execute a command and commit its result at a later time. Invoking try with the -n flag will return the overlay directory, without committing the result. Also: > curl install tries … my brain instantly translated that to "curly fries". Built-in auto-correct!
- samstave 3y agoMakes more, simpler, sense...
- tripdout 3y agoThis is basically what you can get with Nix, sharing a binary cache between machines and getting an identical dev environment / package setup.