angelico

10 ms·

1. 1.▲
   by angelico 5y ago

   When the transition from using a Dockerfile to Ansible was done, the primary consideration was to be able to reuse as much existing instruction/ task files as possible. As such, iirc, this was the first approach taken. It fortunately b
2. 2.▲
   by angelico 5y ago

   Hi! I'm one of the contributors to the repo. Just to clarify, our Docker image [0] only contains the latest version of Postgres (13) and the common extensions listed out here [1]. All the other features such as this [2] and this [3] ar
3. 3.▲
   by angelico 5y ago

   Hi! I'm one of the contributors to the repo. Just to clarify, our Docker image [0] only contains the latest version of Postgres (13) and the common extensions listed out here [1]. All the other features such as this [2] and this [3] ar
4. 4.▲
   by angelico 5y ago

   Hi! I'm one of the contributors to the repo. Primary reason was for uniformity. Initially, we built our EC2 and DO Droplet images with Ansible and our Docker image with a Dockerfile [0]. It became tedious over time as adding a new exte
5. 5.▲
   by angelico 6y ago

   author here - was toying around with WAL-G as one of the many possible solutions for creating physical backups in Postgres. It has been my choice so far given its relative simplicity. My main motivation towards writing this article was to c