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

Closed
ksylvest opened this issue Dec 22, 2010 · 9 comments
Closed

Errno::ENOENT: No such file or directory - /Users/kevin/.fog #121

ksylvest opened this issue Dec 22, 2010 · 9 comments

Comments

@ksylvest
Copy link

Running under Mac OS X 10.6.5 I'm getting:

Fog::Storage.new(:provider => 'AWS') # Errno::ENOENT: No such file or directory - /Users/kevin/.fog
Fog::Storage.new(:provider => 'Google') # Errno::ENOENT: No such file or directory - /Users/kevin/.fog

It doesn't make a difference if the credentials are specified or not.

@andypearson
Copy link

I'm using Carrierwave with S3 uploads, but I'm getting exactly the same issue...

@ksylvest
Copy link
Author

I think it is an issue with the tagged gem. I didn't have any issues prior to updating.

@andypearson
Copy link

Indeed, the prior version (0.3.31) works without requiring .fog -- so it certainly seems to have been something introduced recently.

A simple touch ~/.fog gets 0.3.32 working, but I'm not sure if that solution can be considered "right".

@adriaant
Copy link

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 touch ~/.fog to fix the above error.

@geemus
Copy link
Member

geemus commented Dec 22, 2010

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.

@geemus
Copy link
Member

geemus commented Dec 22, 2010

[core] ./fog should not be required

closed by 9d6d16b

@geemus
Copy link
Member

geemus commented Dec 22, 2010

I'm going to look at a couple other bugs, but should get a version with this fix out later today.

@adriaant
Copy link

Awesome! Thanks for the quick fix! :)

@geemus
Copy link
Member

geemus commented Dec 23, 2010

My pleasure, just sorry I broke it in the first place.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants