-
Notifications
You must be signed in to change notification settings - Fork 492
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Deploy Sinatra and Puma (w/ mina-puma) #400
Comments
In your gemfile add
On Thu, Jul 14, 2016, 01:54 Tara Planas notifications@github.com wrote:
|
@d4be4st Thank you! That works! 💃 |
Sorry to bring this up again, but I was wondering if you had any ideas about using this gem as a dependency in another gem; would you specify that it is a runtime dependency, or a development dependency? Basically, I currently have it as a runtime dependency in the gemspec, and am requiring it, for example,
Many thanks in advance for any pointers! ☝️ |
Hi @l0010o0001l. Mina isn't supposed to be a runtime dependancy. It is a separate CLI tool for deployement. You can put it in your gemfile but only as a 'note' for your future self that you are using mina as a deployment tool. If you still want to put
|
Hi @l0010o0001l , can you post your deploy and setup task? I want use mina to deploy a sinatra app but I do not so shure of deploy task |
Hello! :)
I have been trying to start a Sinatra application that uses Puma. The files and directory structure successfully are placed in the remote server, however I can't seem to get Puma to start. I have tried various ways of passing in commands to the server with
mina run
, or queueing up a task to start it (usingrackup -s Puma
), or getting into the#{deploy_to}/#{current_directory}
itself and trying to start it. The commonly returned error involves this stack trace:Any help is supremely appreciated in advance.
The text was updated successfully, but these errors were encountered: