-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Errno::ENOENT: No such file or directory - /Users/kevin/.fog #121
Comments
I'm using Carrierwave with S3 uploads, but I'm getting exactly the same issue... |
I think it is an issue with the tagged gem. I didn't have any issues prior to updating. |
Indeed, the prior version (0.3.31) works without requiring .fog -- so it certainly seems to have been something introduced recently. A simple |
It seems 0.3.32 introduced some changes to the workflow. What used to work for uploading to S3 now give deprecation errors ("Fog => #config_path is deprecated, use #credentials_path instead", although I'm not using this definition). I also had to do a |
Yeah, it was intended to support either workflow (rather than forcing having a ~/.fog). Since I have those files on my machines I guess I didn't notice the problem. Will work to make both work again now. |
[core] ./fog should not be required closed by 9d6d16b |
I'm going to look at a couple other bugs, but should get a version with this fix out later today. |
Awesome! Thanks for the quick fix! :) |
My pleasure, just sorry I broke it in the first place. |
Running under Mac OS X 10.6.5 I'm getting:
It doesn't make a difference if the credentials are specified or not.
The text was updated successfully, but these errors were encountered: