sameersbn / sameersbn/docker-gitlab
Postgres update as preparation of gitlab 13.0.0
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
We are using the setup described here since a while.
The migration went pretty smooth over the years. With the deprecation of Postgres < 11 introduced in Gitlab 13 I was wondering how i can prepare the migration to the new gitlab 13.0 in respect of our old postgres installation.
We use the following Postgres image:
sameersbn/postgresql:9.6-2
Thank you for your support and all the effort you put into this repo!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the deployment setup using sameersbn/postgresql:9.6-2 and compare it with GitLab 13's PostgreSQL requirement. Determine a supported preparation or upgrade path for the existing installation, and document the required steps and compatibility considerations so users can follow the migration confidently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab, postgresql
- Domain
- databases, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100