central repo for storing machine set up bullshit
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
jowj f8f5f82bbf
Remove duplicate .emacs location
6 years ago
applicationConfiguration Restruction emacs into application config dir; update keyboard firmware and png; restructure to include easy rollback for keyboard firmware. 6 years ago
deployments Update docker run command to use bind mount instead of volume 6 years ago
keyboard Restruction emacs into application config dir; update keyboard firmware and png; restructure to include easy rollback for keyboard firmware. 6 years ago
powershell Remove old location for winDeploy scripts. 6 years ago
.bashrc add python aliases, path additions 6 years ago
.gitattributes update to view nothing as a text file 6 years ago
.gitignore Ignore *~ files in working dir. 6 years ago
.powershellCore.ps1 Remove unnecessary ssh utils. 6 years ago
.tmux.conf add .gitattributes and modifying .tmux.conf 6 years ago
README.md Update README.md to include some specifics about mojobot deployments. 6 years ago
conemu.xml adding conemu config 6 years ago

README.md

agares

agares was a demon who taught those who summoned him foreign languages, but only vulgar words. it must be true because i read it on the internet

purpose:

automate syncing and configuration of machines in my inventory so that i don't have config drift

subprojects:

  • sync powershell $profile and automate updates
  • windows device config:
    • automatically deploy and configure software that i use everywhere (password managers, sync services, text editors, etc)
    • set windows settings to be actually useable
    • set windows privacy settings
    • remove bloatware
  • sync emacs config
  • sync keyboard config for infinity ergodox

deployments

i currently am setting all my deployments to live within agares. i use agares as a submodule within my colove project in order to fascilitate deploys from within a container. this allows me to accomplish a few things that are important to my workflow, but are likely not super important to a lot of other people.

mojobot

ansible-playbook -i hosts.yml mojo.yml --ask-vault-pass (pass in ansible vault pw)

  • if you end up wanting to deploy this somewhere you'll need to update the hosts.yml file to include your targets
  • the ansible-vault file includes my slackbot token. You'll need to update that.