If anyone is just looking for a way to manage and sync dotfiles without any of the sharing features (which are interesting but a little scary), you might want to check out my thing: https://bitbucket.org/davidn/dotstuff
Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
11–17 of 17 posts
Re: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#12If anyone is just looking for a way to manage and sync dotfiles without any of the sharing features (which are interesting but a little scary), you might want to check out my thing: https://bitbucket.org/davidn/dotstuff
Fresh handles local files too: https://github.com/twe4ked/dotfiles/blob/master/config/fresh...
Re: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#13I'm amazed at the number of projects that don't have even the simplest description as to what problem the software purports to solve. This well-intentioned project strikes me as among the more egregious examples.
The README contains almost zero information as to why the project was created, which problems it aims to rectify, and why you might want to use it. That this information may or may not be contained in an embedded video is of no relevance to someone (like myself) who has neither the time nor ability at this particular moment to watch anything on video that could have been more succinctly explained in 2-3 sentences. It won't be bookmarked or favorited for later perusal -- just ignored.
Please understand I mean this as constructively as possible: it's hard to create something and share it with the world, and for that your efforts are most highly commended. I suggest adding a general introduction/description and some use cases to both the project site and README file. That will go a long way toward garnering the attention of those who might otherwise simply shrug and walk away.
Re: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#14I'm amazed at the number of projects that don't have even the simplest description as to what problem the software purports to solve. This well-intentioned project strikes me as among the more egregious examples. The README contains almost zero information as to why the project was created, which problems it aims to rectify, and why you might want to use it. That this information may or may not be contained in an emb…
Thanks for the feedback. We should have done this a while ago. It's easy to forget that other people have no idea what we are building. Cheers.
https://github.com/freshshell/fresh/commit/4ebf599aa61b54b66... and https://github.com/freshshell/fresh/commit/000d7ce00b9029881...
Re: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#15If you're looking for a mature alternative, there's homesick @ https://github.com/technicalpickles/homesick. I use it everywhere and it's great. Unfortunately, it does have a ruby dependency.
Re: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#16If you're looking for a mature alternative, there's homesick @ https://github.com/technicalpickles/homesick . I use it everywhere and it's great. Unfortunately, it does have a ruby dependency.
One of the big features of fresh is that it is able to merge configuration from multiple sources into a single output file. This applies to both shell (aliases) as well as configuration files.
For example, @twe4ked uses my tmux configuration but also has his own additions using the following:
fresh jasoncodes/dotfiles tmux.conf --file
fresh config/tmux.conf --fileRe: Show HN: fresh - a tool to manage and distribute dot files (think Bundler)
#17Whats to stop malicious git repos changing an alias after you have already added it to your freshrc? I think locking to a specific git ref needs to be top priority.
Locking to a specific git reference (https://github.com/freshshell/fresh/issues/11) has been implemented. You can now use `--ref` to lock to a particular git reference. `fresh update` will grab the new version.