Paul Thornthwaite

Having the `--share` command line argument is triggering the assertion error. See https://github.com/AUTOMATIC1111/stable-diffusion-webui/discussions/4065#discussioncomment-4021937 It seems to be set to prevent using extensions when your server may be open and accessible...

Apparently I had not signed up for the Beta, which meant I was unable to select repos to migrate. With that selected, I was able to migrate `fog-brightbox` across. So...

I've no strong opinions in switching to GitHub actions as long as it is consistent so we can see the state of fog in one place. The *pros* for just...

I think that may have been part of their migration strategy. After I noticed performance had become terrible and had looked at alternatives for other work projects, I spotted comments...

I have updated fog/fog-brightbox to use GH actions and removed the Travis config. Although that is running the `rake` minitest specs by default and is not configured to run any...

Also to improve loading, there should be checks possible against each provider/service that is registered checking for dependencies or configuration. ``` Fog::Core::ProviderRegister.providers # => [, ...] provider = Fog::Core::ProviderRegister[:example] provider.dependencies_met?...

I always get pointed back to https://www.ruby-forum.com/topic/3036681 when `autoload` is mentioned. I've not heard any updates so I always think of it as deprecated. Really what I was planning for...

I dug out my old code and moved some bits around. Some of the original names would have clashed with files after the split. I've written tests (fog/fog#3326) to check...

So a quick update on this. I have a simple registry in Fog::Core, a new class for providers to inherit from and a rough prototype of fog-brightbox. I'm erring towards...

I'm not sure. Part of me wonders if it is just bad Rails practice catching people out. Perhaps it's not our problem to solve. Part of me wonders if it...