Minimalist FUSE Manager
Version, currently 0.1.1114 versions
- 1.0latestOct 23, 2023
- 0.2.0not indexedJun 7, 2025
- 0.1.11not indexedJun 7, 2025
- 0.1.10not indexedJun 7, 2025
- 0.1.9not indexedJun 7, 2025
- 0.1.8not indexedJun 7, 2025
- 0.1.7not indexedJun 7, 2025
- 0.1.6not indexedJun 7, 2025
- 0.1.5not indexedJun 7, 2025
- 0.1.4not indexedJun 7, 2025
- 0.1.3not indexedJun 7, 2025
- 0.1.2not indexedJun 7, 2025
- 0.1.1not indexedJun 7, 2025
- 0.1.0not indexedJun 7, 2025
github.com/glenux/mfm
FIXME. write description
Nothing has been indexed for 0.1.11 yet. The tag is recorded, its shard.yml has not been read, so the manifest and dependency list below are empty because they are unknown rather than because they are absent.
Installation
# Add this to your shard.yml
dependencies:
Minimalist FUSE Manager:
github: glenux/mfm
version: ~> 0.1.11Then run:
shards installshard.yml
No shard.yml has been indexed for 0.1.11. You can read it on the repository.
Dependencies
Unknown: the shard.yml for this version has not been read yet.
README
This README is the one indexed from the repository at its latest ref, not from the tag for this version.
GX-Vault Manager
GX-Vault Manager is a Crystal-lang script that helps in managing encrypted vaults using gocryptfs. The script offers a user-friendly interface for mounting and unmounting vaults, providing real-time status and handling errors gracefully.
Configuration
The script uses a YAML configuration file, typically stored at ~/.config/gx-vault.yml. This file contains details about the vaults, including their names and paths.
YAML File Format
The configuration file consists of an array of vaults, with each vault having a name and an encrypted path. Below is the structure of the YAML file:
vaults:
- name: "vault1"
encrypted_path: "/absolute/path/to/vault1"
- name: "vault2"
encrypted_path: "/absolute/path/to/vault2"
# Add more vaults as needed
Fields Description
-
vaults: The root element containing an array of all defined vaults.
-
name: The unique name of the vault. This is used for display and selection purposes.
-
encrypted_path: The absolute path to the directory where the encrypted data is stored. This path is used by
gocryptfsfor mounting the vault.
Example
Here is a sample configuration with two vaults named "Personal" and "Work":
vaults:
- name: "Personal"
encrypted_path: "/home/user/encrypted/personal"
- name: "Work"
encrypted_path: "/home/user/encrypted/work"
Usage
Once the YAML configuration file is set up, run the script. It will read the configuration, and you can select a vault to mount or unmount using the fzf interactive selector. The status of each vault (whether it's open or closed) is displayed next to the vault's name.
Dependencies
- gocryptfs
- fzf
- Crystal-lang
- Other dependencies as per the Crystal-lang script
License
GPL-2
Documentation
Built from the current release. The first visit to a release nobody has asked for starts its build.
Links
This release
- Version
0.1.11- Tagged
- Jun 7, 2025
- Commit
5cfe6159c521- Indexed
- not yet
Dependents
No indexed shard depends on this one yet.
Repository
github.com/glenux/mfm
Metadata
- Created
- Aug 12, 2026
- Updated
- Aug 16, 2026
- Synced
- Aug 15, 2026
- Versions
- 14