-
Notifications
You must be signed in to change notification settings - Fork 54
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
Passing local file to parse command #282
Comments
Hi @dustinmichels! It is indeed Docker-related, but we should clarify it in the documentation anyway. You achieve similar results in a few different ways, please pick one that suits your workflow better. Mount the directory to bblfshd containerThe first way is to expose one of your directories to bblfshd directly. It is the simplest option, but if you don't trust either Docker or bblfshd, you should not expose your whole FS or home directory to the container. A safe middle ground may be to expose an empty directory, or the directory that you want to analyze. It can be done by adding a
Note that you don't need to add a Use bblfshctlThis is a more secure option that requires a You run bblfshd as usual, make sure to pass
It will automatically connect to Use one of the clientsGo client has a simple The same example exists for Python client as well. Running it is similar to running |
Thank you so much for the detailed reply. Much appreciated! |
Agreed, this is great, and in fact I would like to turn all of #282 (comment) into a new entry on the documentation site. I'll look into that now. |
Hi,
I realize this may be more of a Docker question than an issue specific to this repo, but I would love an example in the documentation for how to pass a local file to the parse command.
On the Getting Started you list the following command to run an example file included in the container:
docker exec -it bblfshd bblfshctl parse /opt/bblfsh/etc/examples/python.py
I'm having a lot of trouble figuring out how to pass my own file, on my computer, into the container.
Thanks!
The text was updated successfully, but these errors were encountered: