Skip to content
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

Mina not working on windows #169

Closed
gcarrero opened this issue Feb 26, 2014 · 9 comments
Closed

Mina not working on windows #169

gcarrero opened this issue Feb 26, 2014 · 9 comments
Labels

Comments

@gcarrero
Copy link

I was trying to setup a project with mina for deploying. Our team has windows and mac machines . We have made a deploy test using mina through a mac and we had no problem. The problem is when we use the same deploy file in windows we get a:

bash: #!/usr/bin/env bash: No such file or directory
bash: -c: line 137: unexpected EOF while looking for matching `"'
bash: -c: line 140: syntax error: unexpected end of file

Then the connection is closed.

We have tried to simulate the deploy, getting the bash script that is generated. If we pass this script to the ssh command directly ( ssh user@www.testdeploy.dev -t < deploy.sh ) it works with no problems but not when is run through mina.

Do anyone have an idea what's going on?

Thanks!!

@zacksiri
Copy link

zacksiri commented Mar 8, 2014

generally its not recommended to do ruby development on windows because ruby gem / tools developers don't test their stuff on windows. you'll probably save a lot of time and headache switching to linux or mac.

@gamead
Copy link

gamead commented May 10, 2014

I have same problem,but I need work on windows system,please help.

@orest22
Copy link

orest22 commented May 17, 2014

Same as I have too...

@luozhihua
Copy link

I have same problem, anyone have solutions?

@insub
Copy link

insub commented Jun 6, 2014

I have same problem

@insub
Copy link

insub commented Jun 7, 2014

@gcarrero hello, I have same problem,so ,how getting the bash script that is generated?
thk :)

@mgoggin
Copy link

mgoggin commented Jun 9, 2014

Possibly related to issue #83.

@insub
Copy link

insub commented Jul 12, 2014

hi, i fix that. Just check #83

@pavei
Copy link

pavei commented Sep 17, 2014

  • 1

@d4be4st d4be4st added the bug label Jul 5, 2015
@d4be4st d4be4st closed this as completed Jul 8, 2016
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants