Answered my own question I guess, reading a post at https://about.gitlab.com/2013/06/20/integrating-gitlab-ci-with-gitlab/
We still want a clean separation between GitLab and GitLab CI to allow them to develop independently, reduce security risks and keep each code base small. Therefore, GitLab CI has its own database and uses GitLab’s public API to communicate with GitLab. GitLab CI does not have access to more code or user information than what is accessible by the users who are logged in to GitLab CI. Thanks! fred On Tuesday, August 18, 2015 at 7:28:17 AM UTC+2, Fred Blaise wrote: > > Hi all, > > New to gitlab, and so far so good :-) > > I was quickly trying to bring a gitlab-ci container up alongside gitlab, > but apparently, I just cannot put the ci stanza in the same > docker-compose.yml as gitlab. > gitlab-ci complains then that the postgres tables already exist, and shuts > down the containers. > > Do we really have to have separate postgres containers got gitlab and > gitlab-ci? What about the redis containers? Do we also need to duplicate > that one too? > > Thanks for your help. > Best, > fred > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/a026cbc5-9a29-474b-94cb-4bb9305b6d30%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
