-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add docker-compose #33
Conversation
docker-compose.yml
Outdated
image: "bblfsh/bblfshd" | ||
privileged: true | ||
volumes: | ||
- /var/lib/bblfshd:/var/lib/bblfshd |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It wouldn't work on macos. Please consider using named volume instead:
bblfsh/bblfshd#136
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smacker I rebased and addressed your suggestion about named volumes; It was my first time;) did I do it properly?
Looks great! Maybe this is asking too much, but would it be possible to build a bblfsh container that already has all the drivers installed? I imagine something like: compose:
Dockerfile-bblfsh-drivers
|
a6021dc
to
2b311e0
Compare
@carlosms I included the driver installation process in the Is it better for you? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tried on macOS - works like a charm. 👏
docs/quickstart.md
Outdated
--env GITBASEPG_DB_CONNECTION="gitbase@tcp(gitbase:3306)/none?maxAllowedPacket=4194304" | ||
--name gitbase_playground | ||
srcd/gitbase-playground:latest | ||
$ GITBASEPG_ENV=dev REPOS_FOLDER=./repos GITBASEPG_ENV=dev docker-compose up |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as this is a quickstart that first time users might follow - do you think it might be worth not to assume that they know, but rather state explicitly here that after this command, if a user does Ctrl+C
- he will still have the containers running and have to stop/kill/rm those?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with this command, Ctrl-C
would kill containers.
2b311e0
to
776e2cd
Compare
I updated the PR desc so: # Run latest released image:
$ REPOS_FOLDER=./repos docker-compose up
# Run from sources (useful when developing or willing to run the tip of master...)
$ REPOS_FOLDER=./repos make compose-serve @bzz This ☝️ address your #33 (comment) What it happened to you is that you started the latest tag (v0.0.1) not containing the frontend. To build the tip of @smacker @carlosms could you PTAL again? I included the two running options as agreed. @eiso you might be interested in this b874407, that address your suggestions made by #36 |
docs/quickstart-manually.md
Outdated
|
||
You can locally build and deploy `gitbase-playground` and its dependencies using [`docker-compose`](https://docs.docker.com/compose/install/) | ||
|
||
If you preffer to run `gitbase-playground` with [`docker-compose`](https://docs.docker.com/compose) (without taking care of the app dependencies), you can follow [the playground compose quickstart](quickstart.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
preffer -> prefer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks!!!
LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I left a couple of comments but I think it's looking great as it is.
Makefile
Outdated
@@ -68,6 +69,16 @@ build-path: | |||
|
|||
serve: | front-build back-start | |||
|
|||
compose-serve: | require-repos-folder front-dependencies build | |||
REPOS_FOLDER=${REPOS_FOLDER} \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: should this use the same GITBASEPG prefix as other env vars? It's not used by gitbase-playground itself, but it's used by the docker compose file we provide so... I'm not sure.
docker-compose.build.yml
Outdated
|
||
services: | ||
playground: | ||
image: gitbase-playground-from-sources |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: what about shorter gitbase-playground-dev
?
👏 go ahead! |
Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
Signed-off-by: David Pordomingo <David.Pordomingo.F@gmail.com>
00eab08
to
36e318b
Compare
If accepted it would be only needed to run:
Run latest released image:
Run from sources (useful when developing or willing to run
tip
ofmaster
...)