Use alpine images #137
Use alpine images #137
Conversation
|
I'm ok with the memcached change, but I'd rather not recommend Postgres on alpine. So if you wanna back that change out, I'll merge memcached. |
|
Reverted it back to regular image I have been using Postgres Alpine image for quite some time in production and have not noticed any errors / anomalies. |
|
The primary problem with alpine vs Debian images in Postgres is interapability with the data on disk. If you change from a Debian based image to Alpine or vice versa, you will corrupt your indices resulting in very confusing behaviors and unexpected results. If you use Alpine for Postgres, you need to make sure you literally never switch to another distro or change the version of musl, and I’m not sure how often this happens in alpine world. |
* Use alpine images (getsentry#137) * Use alpine images * Updated memcahced version from 1.4. to 1.5 * Reverted Postgres back to regular image * Update Dockerfile to get latest image (getsentry#162) * Add Minimum Hardware Requirements (getsentry#165) * Add Nginx * Fix conf.d path * Fix nginx with auto certificate creation
* Use alpine images (getsentry#137) * Use alpine images * Updated memcahced version from 1.4. to 1.5 * Reverted Postgres back to regular image * Update Dockerfile to get latest image (getsentry#162) * Add Minimum Hardware Requirements (getsentry#165) * Add Nginx * Fix conf.d path * Fix nginx * Fix nginx with cerbot * Add restart script * Demonize up Co-authored-by: McSneaky <kevin@synter.ee> Co-authored-by: Pieter <pietering1@gmail.com> Co-authored-by: Omid Raha <omidraha@users.noreply.github.com>
* Use alpine images * Updated memcahced version from 1.4. to 1.5 * Reverted Postgres back to regular image
No description provided.