-
Notifications
You must be signed in to change notification settings - Fork 25
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
puma-dev #184
Comments
Thank you for the report! To determine if the Rails app is running, we just make a request to the Rack app we automatically mount. I don't know how puma-dev works, but maybe it's changing the booting behaviour somehow? If you boot the Rails app, do you get a |
I couldn't tell you exactly how it works, but I think the idea is that there is a global service that runs and manages the registered puma apps. The idea is that there is no explicit start/stop with There is no |
Okay, the absence of that file is certainly the issue. Now, we need to understand why the file isn't there. We use a railtie initializer to write the URL of your app to that file - otherwise, the Ruby LSP addon has no way of knowing which URL to make requests to. What I suspect might be happening based on your description, is that If you add a breakpoint/puts statement in the initializer, we can probably figure out if that's the case. If that is indeed what's happening, then we need to understand if there is a way of determining the host and port when using |
@joelmoss maybe double check you don't have I was seeing a similar problem with regular puma, found this thread, and seeing this:
Made me realize I copied the line for ruby-lsp-rspec, which does use |
You should not add |
We're changing how the LSP communicates with Rails, so this will no longer be a problem: (not yet released but should be soon). |
I use puma-dev to run my rails apps, but ruby-lsp-rails doesn't know that...
Any way to get it working with puma-dev? thx
The text was updated successfully, but these errors were encountered: