-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
Trouble using rspec-mode with docker #192
Comments
Where does |
There is a Gemfile for each project next to each Dockerfile. I've updated the strings to use quotes as you mentioned but it still does not work. I wasn't sure how to run
and it returned the path to the root of my project (~/docker-projects/project_1/). |
Escape colon M-: and then type in the lisp you want to evaluate. Many variables are buffer specific so start while in the buffer where you are doing your work.
… On Feb 15, 2020, at 9:32 AM, Miguel Bernabeu Diaz ***@***.***> wrote:
There is a Gemfile for each project next to each Dockerfile. I've updated the strings to use quotes as you mentioned but it still does not work.
I wasn't sure how to run (rspec-project-root) so I did it in a scratch buffer opened in the root of my project. I run:
(rspec-mode)
(rspec-project-root)
and it returned the path to the root of my project (~/docker-projects/project_1/).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#192?email_source=notifications&email_token=AAASST3EYY7GKFNPQ3AO42LRDADJRA5CNFSM4KVYNHMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEL3PD4Y#issuecomment-586609139>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAASST67ZY2NM43245NVPK3RDADJRANCNFSM4KVYNHMA>.
|
@pedz Thanks for the tip! Just run it in the buffer where I was failing to run the specs and it returned the project root properly. |
Then I can recommend edebug-ing |
BTW, you might want to try https://github.com/bibendi/dip. It's a semi-transparent wrapper for Configuring
(Or do that in |
I'm trying to run the specs with rspec-mode against docker but it always fails as it tries to run the specs locally (bundler not installed locally). I also can't figure how to get some more verbose output to debug if my config may be wrong.
Setup is as follows:
Each of the projects is a separate git repository and they are put in this order manually (no submodules or anything similar). The projects interdepend, so we have a single docker-compose.yml for all of it.
I'm setting the variables in the dir-locals for each project as recommended in the README.
.dir-locals.el of project_1:
I'm setting
rspec-docker-file-name
as it seems to be necessary to detect the docker support (by skimming the code) which is not documented in the README. Also in my case, as thedocker-compose.yml
is outside the project root I'm overwriting it for the Dockerfile, which is present. I got the warning about unsafe dir-locals and accepted it, so I'm not expecting the error to be there.Any idea on what may be wrong or how to further debug the issue? Toggling from spec to implementation works and I assume all other features do work as well.
The text was updated successfully, but these errors were encountered: