<commit_before># weblabdeusto-playbooks

Ansible playbooks to install and manage WebLab-Deusto.



## Requisites

    ansible-galaxy install brad.virtualenv

## Usage examples

### Using vagrant

    cd vagrant
    vagrant up
   
Please, check _vagrant/Vagrantfile_ for more information.

### Using only ansible

__Assumption__: you have a machine equivalent to the one created by vagrant in the previous step (see _vagrant/Vagrantfile_) in the IP defined by the _simple_ file.

    # Executing the whole playbook using the "simple" inventory with user "vagrant", etc.
    ansible-playbook -vvvv -u vagrant --private-key=~/.vagrant.d/insecure_private_key -i simple --limit='local' main.yml
    
    # To execute only Weblab related steps
    ansible-playbook -vvvv -u vagrant --private-key=~/.vagrant.d/insecure_private_key -i simple --limit='local' main.yml --tags weblab

I will try to adhere to Ansible's [best practices](http://docs.ansible.com/playbooks_best_practices.html#content-organization) in the project organization. Therefore, [these usage patterns](http://docs.ansible.com/playbooks_best_practices.html#what-this-organization-enables-examples) should be applicable once the playbook is finished.<commit_msg>Adding a kind message to warn about the database password storage<commit_after># weblabdeusto-playbooks

Ansible playbooks to install and manage WebLab-Deusto.



## Requisites

    ansible-galaxy install brad.virtualenv

## Usage examples

### Using vagrant

    cd vagrant
    vagrant up
   
Please, check _vagrant/Vagrantfile_ for more information.

### Using only ansible

__Assumption__: you have a machine equivalent to the one created by vagrant in the previous step (see _vagrant/Vagrantfile_) in the IP defined by the _simple_ file.

    # Executing the whole playbook using the "simple" inventory with user "vagrant", etc.
    ansible-playbook -vvvv -u vagrant --private-key=~/.vagrant.d/insecure_private_key -i simple --limit='local' main.yml
    
    # To execute only Weblab related steps
    ansible-playbook -vvvv -u vagrant --private-key=~/.vagrant.d/insecure_private_key -i simple --limit='local' main.yml --tags weblab

I will try to adhere to Ansible's [best practices](http://docs.ansible.com/playbooks_best_practices.html#content-organization) in the project organization. Therefore, [these usage patterns](http://docs.ansible.com/playbooks_best_practices.html#what-this-organization-enables-examples) should be applicable once the playbook is finished.


## Notes

If you are going to fork this and parametrize it with your own installation details, please make sure that either you don't version the resulting file or you use vault for the passwords.

For example, the file with the "global" variables (group_vars/local) stores a default database password.
{'fraction_non_alphanumeric': 0.08139950017850768, 'fraction_numerical': 0.0, 'mean_word_length': 4.27683615819209, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, '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': '6550323', 'n_tokens_mistral': 861, 'n_tokens_neox': 821, 'n_words': 295}