https://github.com/tarcisioe/configmanager

A nice set of scripts for managing and sharing configuration files under VCS between multiple Linux user accounts.
https://github.com/tarcisioe/configmanager

Last synced: about 1 month ago
JSON representation

A nice set of scripts for managing and sharing configuration files under VCS between multiple Linux user accounts.

• Host: GitHub
• URL: https://github.com/tarcisioe/configmanager
• Owner: tarcisioe
• License: bsd-2-clause
• Created: 2013-07-22T23:17:52.000Z (over 11 years ago)
• Default Branch: master
• Last Pushed: 2015-10-19T06:43:05.000Z (about 9 years ago)
• Last Synced: 2024-03-23T23:50:16.835Z (9 months ago)
• Language: Shell
• Size: 164 KB
• Stars: 4
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
configmanager

=============

A nice set of scripts for managing and sharing user configuration files under

VCS between multiple Linux user accounts and systems.

# Installing

Installing can easily be done by cloning the repository and running the install

script.

    git clone https://github.com/tarcisioe/configmanager

    cd configmanager

    bash install.sh [optional directory]

    

The **optional directory** will be created by *install.sh* and must not exist

before (If the directory already exists, *install.sh* will refuse to install.).

If the directory is omitted, *install.sh* installs to `~/.configmanager/`.

**Note**: Installing is only needed the first time you are using this. Every

other computer where you will use this, you will import your directory, so

there will be no need to install this way again.

# Using

On first use, you will need to register the config files that will be managed.

This is done by **register.sh**.

(You might want to chmod +x the scripts, or optionally call them with bash.)

Usage is simple:

    ./register.sh  

    

*register.sh* will then move *file* to the *files* directory inside the

directory where you installed, under *storage name*, create a link to the stored

file and then register it on the mapping.

Note: files under your homedir will have your $HOME substituted by ~. The other 

scripts deal with that. This way, you can use this independently of username.

**IMPORTANT**: Filenames with spaces are basically guaranteed not to work.

Configuration files don't normally have spaces in their names, though. Also, no

file should. Really.

When done, you can then put the directory under version control and send it to a

remote repository. (Github is quite

cool!)

## Migrating a new system

Migration is also simple. Just obtain a copy of your installation folder on the

first system (Git will help you here on getting everything always synced.).

Run *migrate.sh*:

    ./migrate.sh

    

It takes no arguments. It will migrate any file registered on the mapping by

removing it and linking it back with the version stored.

## Linking files that don't yet exist

If for example, you are using a new system and haven't even created some config

files, *link.sh* will create links for files that are mapped but don't yet

exist.

Usage is just:

    ./link.sh

    

## Undoing

Just run *undo.sh*

    ./undo.sh

   

It will replace every mapped file with the version stored.

# Updating

If this repository is updated, just run *update.sh* pointing at your

installation directory. It will replace every script with the new version.

    bash update.sh [optional directory]

    

If your directory is under VCS, don't forget to commit :).