Manage your hostfile in the terminal - v1.0.0 'Track Ballast' ♫
Have the ability to automate your hostfile. Create automatic backups and add a hostname with just one single line in your terminal. Also comes with a fancy menu if you want to do it step by step.
In these times with Puppet, Chef, Docker, etc, configuration of your environment shouldn't be that much of a hassle anymore. Why would the last step, adding a hostname, be done in a text file while you have your terminal right in front of you?
Keyword is simplicity in your workflow and you should be lazy. Don't get into that textfile! This project comes to help for completing the last step for setting up the environment; linking it.
That is a separate concern. The hosts-file and virtual host configuration-file should not go together.
Use this command:
curl https://raw.githubusercontent.com/Krettis/cohoast/master/.dot/install.sh | bash
Download the release or clone this repo. the folder in the desired location. Then simple run:
. run.sh
Bash in
- osx
- linux ( not tested )
In the root of the repo you can set your configuration in the YAML-file. Rename the config.sample.yml to config.yml. It is not required to configure everything, lines can be left out.
Menu
$ cohoast
Adding a host
$ cohoast add [ hostname ]
Default this will added the configured default category and the default ip-address
To assign it to a different ipaddress use the -i or --address flag.
For assigning it to a another category use the -c or --category flag.
Example of adding host with different flags:
$ cohoast add -h sub.mydomain.com --category homemade-locals --address 192.168.22.101
Block a host
$ cohoast block [ hostname ]
Deletion
$ cohoast delete [ hostname ]
Backup
$ cohoast backup
For a more details use man cohoast or cohoast help
To check if the code is somewhat decent bash:
make lint
For tests:
make test
Having some fancy ideas what should be in this repo? Go to my issues and submit an idea. Or even better, code it yourself, create a test and do a pull request.
If you see any mistakes in code or grammatics just let me know. Or better, create a pull request.
I'm trying to get to know Bash some more. Doing some projects like these will get to know the more basic stuff. Also getting a better idea of what to commit in git, how the commit message should be formatted and when to move on to the next issue. So I got that going for me, which is nice.
This project is get myself working on better documentation. I've learned that no matter how good/powerful your tool is, if the documentation is poor people will just go to the alternative. Which may be suck, but it is known to suck.
Look at the documented milestones in the issue which way this is going
Videostill from 'The Railrodder'