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

[WIP] 2.0.0 changes #336

Merged
merged 1 commit into from
Dec 21, 2016
Merged

[WIP] 2.0.0 changes #336

merged 1 commit into from
Dec 21, 2016

Conversation

PikachuEXE
Copy link
Member

@PikachuEXE PikachuEXE commented Dec 16, 2016

Main changes

  • require fog-core instead of fog

Copy link

@SuperTux88 SuperTux88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only some small things, the rest looks good to me.


## Installation

Add the gem to your Gemfile

``` ruby
gem 'asset_sync'
gem "asset_sync"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that can be removed? Because you always need to add a provider which is described below?

If you prefer to load fewer classes into your application, which will reduce load time and memory use,
you need to load those parts of Fog yourself *before* loading AssetSync:
Asset Sync has no idea about what provider will be used,
so you are responsible for bundling the right gem for the provided to be used.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"... the provider to be used."

```

If you don't install the required gem,
Fog will complain (by exception) about it when provider is set by Asset Sync.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if you should keep a require "fog/core" in the lib/asset_sync.rb. Normally it shouldn't be needed, because if you add a provider, the provider requires it. But If you don't do that, then Fog can't complain about it, because Asset Sync doesn't even find Fog.

@PikachuEXE
Copy link
Member Author

@SuperTux88
All 3 things fixed, please check :)

@@ -1,4 +1,6 @@
require File.dirname(__FILE__) + '/../spec_helper'
require "fog/core"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't needed anymore.

@@ -1,4 +1,5 @@
require File.dirname(__FILE__) + '/../spec_helper'
require "fog/core"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some here.

@PikachuEXE
Copy link
Member Author

@SuperTux88
Those lines are removed

I have given up on making integration spec green.
It seems requiring real AWS key for running.

Copy link

@SuperTux88 SuperTux88 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doc and code looks good to me now.

@PikachuEXE
Copy link
Member Author

I will release this within this week (unless I forgot o_0

@SuperTux88
Copy link

About the spec: I haven't tested anything, only reviewed the changes. But I assume that it is also broken without your changes?

@PikachuEXE
Copy link
Member Author

The integration fails since complains about access key / secret key missing
But If I feed it with incorrect value, AWS return 403 which fails the spec

@PikachuEXE PikachuEXE force-pushed the upgrade/asset_sync/2.0.0 branch from e8deafd to 3f50a11 Compare December 21, 2016 03:17
@PikachuEXE PikachuEXE merged commit 3f50a11 into master Dec 21, 2016
@PikachuEXE PikachuEXE deleted the upgrade/asset_sync/2.0.0 branch December 21, 2016 03:20
@PikachuEXE
Copy link
Member Author

@SuperTux88
2.0.0 released
Have a try!

@j15e j15e mentioned this pull request Mar 1, 2019
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

Successfully merging this pull request may close these issues.

2 participants