Post 471850 by ehashman@toot.cat
 (DIR) More posts by ehashman@toot.cat
 (DIR) Post #471850 by ehashman@toot.cat
       2018-10-10T21:26:55Z
       
       0 likes, 0 repeats
       
       Apparently I am now responsible for converting all our Ansible into Debian packages, wheeee
       
 (DIR) Post #472049 by calvin@cronk.stenoweb.net
       2018-10-10T21:39:28Z
       
       0 likes, 0 repeats
       
       @ehashman revenge of real package managers, FINALLY
       
 (DIR) Post #472813 by ehashman@toot.cat
       2018-10-10T22:23:25Z
       
       0 likes, 0 repeats
       
       @calvin we can't turn Ansible into a base image, but we can select packages for inclusion into a base image, soooAlso, packages ensure that the configs stay with the software, rather than be scattered in 20 places between 5 ansible roles >_<
       
 (DIR) Post #472950 by wink@mastodon.social
       2018-10-10T22:29:49Z
       
       0 likes, 0 repeats
       
       @ehashman That does not really fit any use case I ever had. Except that one time we were doing deploys with Debian packages. I've since been pretty much against packaging my own software in this way and rather do custom deployments.But I hope it works out for you :)
       
 (DIR) Post #473020 by ehashman@toot.cat
       2018-10-10T22:34:01Z
       
       0 likes, 0 repeats
       
       @wink all our base images are Debian and this fits into our preexisting pipeline. You can either tell our image builders packages to include in images or deployments from our monorepo; our current "download and unzip a tarball from cold storage" is not working so well with that