<commit_before>Cohoast 
===
Influence your hostfile in the terminal - ___v0.0.4___ [♫](https://play.spotify.com/track/0pu6LHgjcYVQZPnPgxFbzi) 

![Logo above the lonely railroad](http://i.imgur.com/S0UDcX1.jpg "Influence your hostfile in the terminal")


## The power of a single line
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 follow a step by step way.


### Ridin' along with the train of service
In these times with Puppet, Chef and Docker, configuration of your environment shouldn't be that much of a hassle anymore. So why would the last step, adding a hostname, be done in a text file? This when you have the 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.

#### Dealing with the virtual hosts in Apache, Nginx, etc
That is a separate concern. The `hosts`-file and `virtual host configuration`-file should not go together. Plans are for making a callback, so maybe that could help a lot of loose ends (although docker already helps you with this).

### Other motive
I'm trying to get to know Bash some more. Doing some projects like these will get to know the more basic stuff. So I got that going for me, which is nice. 

#### And last
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. 


### Configuration
... _soon_

### Installation

Put the folder in the desired location. Then simple run:

    . run.sh
    
#### Environment 

Bash in 
- osx
- linux ( not tested ) 




## Usage

Menu

    $ cohoast

Adding a host

    $ cohoast add [ hostname ]
    
## Finally

### Plans
First concern is to add hosts, but just look at the issues page for the roadmap.


![The Railrodder](http://blog.nfb.ca/wp-content/uploads/2013/10/BUSTER-KEATON-insert_31.jpg "")

> _Videostill from 'The Railrodder'_

<commit_msg>Replace of word and small version change<commit_after>Cohoast 
===
Manage your hostfile in the terminal - ___v0.0.5___ [♫](https://play.spotify.com/track/0pu6LHgjcYVQZPnPgxFbzi) 

![Logo above the lonely railroad](http://i.imgur.com/S0UDcX1.jpg "Influence your hostfile in the terminal")


## The power of a single line
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 follow a step by step way.


### Ridin' along with the train of service
In these times with Puppet, Chef and Docker, configuration of your environment shouldn't be that much of a hassle anymore. So why would the last step, adding a hostname, be done in a text file? This when you have the 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.

#### Dealing with the virtual hosts in Apache, Nginx, etc
That is a separate concern. The `hosts`-file and `virtual host configuration`-file should not go together. Plans are for making a callback, so maybe that could help a lot of loose ends (although docker already helps you with this).

### Other motive
I'm trying to get to know Bash some more. Doing some projects like these will get to know the more basic stuff. So I got that going for me, which is nice. 

#### And last
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. 


### Configuration
... _soon_

### Installation

Put the folder in the desired location. Then simple run:

    . run.sh
    
#### Environment 

Bash in 
- osx
- linux ( not tested ) 




## Usage

Menu

    $ cohoast

Adding a host

    $ cohoast add [ hostname ]
    
## Finally

### Plans
First concern is to add hosts, but just look at the issues page for the roadmap.


![The Railrodder](http://blog.nfb.ca/wp-content/uploads/2013/10/BUSTER-KEATON-insert_31.jpg "")

> _Videostill from 'The Railrodder'_


{'fraction_non_alphanumeric': 0.06986117330944917, 'fraction_numerical': 0.006717420510523959, 'mean_word_length': 3.767342582710779, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1475018', 'n_tokens_mistral': 1332, 'n_tokens_neox': 1235, 'n_words': 662}