Catching up with current dev
This commit is contained in:
10
README.md
10
README.md
@@ -20,10 +20,9 @@ ansible-playbook -i your-inventory.yml playbooks/sshkey.yml
|
||||
ansible-playbook -i your-inventory.yml playbooks/deploy.yml
|
||||
```
|
||||
|
||||
For convenience, we recommend adding the following alias to your .bashrc or .bashrc.local.
|
||||
```
|
||||
alias deploy="cd ~/src/Ubiqtorate; ansible-playbook -i examples/msn0.yml playbooks/deploy.yml; cd -"
|
||||
```
|
||||
We've also added two scripts in `./bin` to make your life easier:
|
||||
* `full-deploy`: This is the general role. If you are creating an AniNIX replica, once you have your inventory and vault populated, then you can run this script to push everything. This is also optimal when rotating vault secrets or other global tasks. This is effectively standardizing invocation of our overall deployment playbook.
|
||||
* `deploy-role`: When you are updating a specific role, use this script to push that role to your group. Ideally, this should only be used to push a role that you have been working on to a target group in your inventory that's already tagged for the role in the deployment playbook.
|
||||
|
||||
Happy hacking!
|
||||
|
||||
@@ -31,6 +30,3 @@ Happy hacking!
|
||||
|
||||
Some services, such as AniNIX/Sharingan and AniNIX/Geth, store their configuration in internal datastructures and databases such that we cannot easily export our build for others to use. We will document what we have done for each of these as best we can in the README.md files for others to replicate. Backups of these services into AniNIX/Aether are therefore dumps of these databases and not available to share.
|
||||
|
||||
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user