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
install script explodes on osx #3186
Comments
Something must be different about directly piping the script to sh, because when the script is downloaded first and then executed, it works normally... I have to go and look at how the RVM guys do it ... |
It also chokes on Ubuntu 11.10 when I pipe the script to sh
Works fine if I download it and execute it manually. |
Piping the script was blocking STDIN which is required for interactivity. Could you try again now? |
I just tried it on osx tonight. My first try resulted in this:
it seems that when i just put '.', that made it really confused. also, when i typed '' for the database password, it seemed upset as well. the second time, it seemed to work better...
but actually, it just cloned it into a directory called ~ Then I got bored. :/ |
@Raven24 I have seen these problems too. I really think we should cut the fancy stuff. Lets just clone it to a new diaspora folder in the current working directory that you clone the repo in. Lets also just default the db to mysql, and make sure it is really easy to just comment it out to enable the postgres setup. once thats bulletproof, we can work from there. Less questions and more opinions in the script, methinks. |
... but I wanna play install wizard pout It should now fail horribly if something went wrong. Also, it is necessary not to use '~' or '.' in the path, because it gets quoted and bash expansion doesn't seem to do its magic when paths are quoted. I can tackle that inconvenience later, but for now you can tab-expand your paths if necessary. ;) |
@rosannarosanna you should probably be running it on bsd... |
haven't heard about any more major failures in the install script lately... |
I get an error at the 'executing bundle exec rake db:schema:load_if...' stage because it can't find libcurl even though it is installed. What a headache. |
Close and open new ones for new issues with it? |
agreed |
I get the following error when I run the curl command:
help me @Raven24, your my only hope!
The text was updated successfully, but these errors were encountered: