GitXplorerGitXplorer
j

configfs

public
1 stars
0 forks
0 issues

Commits

List of commits on branch master.
Unverified
5ca30c322f4367ccb9abb89c08d180deda44eac7

Use git version of EasyFuse

jjD91mZM2 committed 5 years ago
Unverified
37281c1be4aef45ccc17833c0e54fe3b30041460

Polish up a little

jjD91mZM2 committed 5 years ago
Unverified
c3b6fe5f6f24cd8b38616373aa7986765ca1d171

Rewrite to use EasyFuse

jjD91mZM2 committed 5 years ago
Unverified
9ad5c8f7dd788058f4a92f9bb6c6c5811a60f5e0

Before deciding to write EasyFuse

jjD91mZM2 committed 5 years ago

README

The README file for this repository.

configfs

Crazy project that uses FUSE to create virtual configs for all your configs.

configfs test-mount/
ln -s my-config.toml test-mount/my-config.toml
ln -s my-config.json test-mount/my-config.json
ln -s my-config.yaml test-mount/my-config.yaml

This should have created a structure such as

test-mount
├── my-config.json/
│   ├── config.json
│   ├── config.toml
│   └── config.yml
├── my-config.toml/
│   ├── config.json
│   ├── config.toml
│   └── config.yml
└── my-config.yml/
    ├── config.json
    ├── config.toml
    └── config.yml

3 directories, 9 files

The my-config.json directory has 3 different variations of your original configuration:

  • One reformatted JSON config
  • One TOML config
  • One YAML config.

Why this is a thing

Because it can be a thing, which of course ultimately means it should be. In all seriousness though, it wouldn't be too crazy to plug something like dhall in here.

It also served as motivation to start EasyFuse, although unfortunately it looks like it won't hold as motivation to finish it.