Results for #ansible

00:16 utc nov 05 2018 permalink

41-commit weekend 🤩Feel much better about my #webpack , #ansible, and #packer code #win

23:01 utc nov 04 2018 permalink

Removing just the dev package with #ansible #provisioning had no effect in local env, but combined with the apt purge in the #packer script, uninstalled mysqlclient

22:58 utc nov 04 2018 permalink

I recently started cleaning up after myself during #provisioning. There are two steps to this: #ansible uninstalls build deps and #packer executes a cleanup script that does an apt purge and autoremove

17:27 utc nov 03 2018 permalink

I completed removing build artifacts from source control. Static assets dist and document-root dirs: replaced with running #webpack on host. Third-party #ansible roles: installed from galaxy via #packer and #vagrant at provision time. #win

00:05 utc oct 29 2018 permalink

Significantly refactored my #webpack static asset pipeline today. No longer build assets locally and check them in. Build happens as part of #ansible provisioning. #win

08:11 utc apr 18 2018 permalink

Switched from community PPA to official nginx-provided binaries. That was ... really easy: #win #ansible

05:46 utc jul 30 2017 permalink

when reading from stdin, ansible-vault encrypt_string does not trim trailing newlines, forcing one to use echo -n. #ansible knows this is a sharp edge and documents it, but they should do the right thing and make it consistent with password files #fail

05:23 utc jul 25 2017 permalink

6. addendum: since I already had a deploy script, it was straightforward to translate it to #ansible tasks

05:23 utc jul 25 2017 permalink

6. problem: bespoke deployment steps. deploy and cron run as lopopolo. deploy needs sudo password. solution: #ansible deploy_helper module

05:21 utc jul 25 2017 permalink

5. problem: environment names are inconsistent across tooling and deployment. solution: hyperbola_environment #ansible variable which parameterizes everything

05:17 utc jul 25 2017 permalink

3. problem: manual, bespoke server configuration. solution: #ansible, #vagrant, #packer, prebaked AMIs. immutable infrastructure

09:50 utc jul 22 2017 permalink

The migration from a bespoke-bootstrapped, manual (scripted) deploy process to an #ansible playbook took about 20 commits. I deployed to a local #vagrant box first

18:40 utc jul 02 2017 permalink

Converted wiki from ELB to ALB this morning ... took a couple of hours. modified #terraform config and updated #ansible ... also converted from Let's Encrypt to ACM. #win

10:45 utc nov 20 2016 permalink

hyperbola-wiki is now fully deployed using #ansible. #vagrant made testing easy. #win