sameersbn / sameersbn/docker-gitlab
PR: sidekick container for Confiuration
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
We Should apply the Sidekick Pattern for creating docker images that get configured from outside:
- Better support for large deployments
- Better usability
At Present we are solving building and configuration in the main gitlab image we should source that out to sidekick containers or a single sidekick at first
that means the sidekick container aka gitlab-config will have all mounts that it needs for configuration it will then start via volumes-from gitlab and configure it
configuration is:
bundle tasks
nodejs asset tasks
this will introduce also a new base image called gitlab-base where we install all build requirments like:
- Ruby
- Go
- Node
later we should probally isolate that images also and use the nativ node:, ruby Go* images.
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
No files or tests are named. Start by examining the main GitLab image and its current bundle and Node.js asset tasks, then determine the required mounts and responsibilities for the proposed gitlab-config sidekick and gitlab-base image; done would require an agreed container architecture and working build/configuration flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, node.js, ruby
- Domain
- build-system, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100