dotfs alternatives and similar packages
Based on the "System" category.
Alternatively, view dotfs alternatives based on common mentions on social networks and blogs.
-
optparse-generic
Auto-generate a command-line parser for your datatype -
hapistrano
Deploy tool for Haskell applications, like Capistrano for Rails -
nix-deploy
Deploy software or an entire NixOS system configuration to another NixOS system -
ghc-hotswap
Example code for how we swap compiled code within a running Haskell process. -
typed-process
Alternative API for processes, featuring more type safety -
openssh-github-keys
Control SSH access to your servers via GitHub teams -
system-fileio
Contains the system-filepath and system-fileio packages -
atomic-write
Writes files atomically in Haskell while preserving permissions -
language-puppet
A library to work with Puppet manifests, test them and eventually replace everything ruby. -
ascii-progress
A simple Haskell progress bar for the console. Heavily borrows from TJ Holowaychuk's Node.JS project -
plugins
Dynamic linking and runtime evaluation of Haskell, and C, including dependency chasing and package resolution. -
directory-contents
Recursively build a tree of directory contents, avoiding symlink cycles
Clean code begins in your IDE with SonarLint
Do you think we are missing an alternative of dotfs or a related project?
README
DOTFS
DotFS is first and foremost a work in progress. It is, however, usable, and the authors use it on their personal machines. The idea is that you point DotFS to a folder containing your dotfiles containing special DotFS annotations, which will then be made available as a virtual filesystem at a user-specified mountpoint. The files will be scanned for special keywords and presented on the virtual filesystem, possibly configured per-host or per-OS, however you like. The use case is a user wanting automatic configuration adjustment in larger config files with shared sections. See the wiki for a quick guide, a users' guide, a specification of the grammar, and some examples.
Note that if a file doesn't contain DotFS markup, it is passed through "vanilla" — this includes binaries. This means that you don't have to convert all your config files before starting with DotFS, but that you can annotate those which currently pose an inconvenience, and leave all the others as they are.
Requirements
- POSIX system
- FUSE (or OSXFUSE)
- GHC (Haskell platform recommended)
- Tested on Linux, hfuse needs to be un-broken on OS X
Installation
First install some dependencies (example is for Debian-like systems):
NOTE to OS X users: the HFuse library, on which we depend, doesn't build using the latest OSXFUSE library. Please use the patched version fork for now, until the pull request is hopefully accepted.
sudo apt-get install libfuse-dev fuse-utils
Install DotFS, or run from the local directory using make
and then ./dotfs
.
cabal configure
cabal install
Usage
See the wiki entry on usage. Soon a short presentation will also be put online which will hopefully serve as both an elevator pitch and a short introduction to the features that are available. See here.
Interesting pointers
- Entry at the Dutch Haskell Day site: here
- We're online: video of the lightning talk
- There's a cabal package: hackage