rails-assets.org is down again again

[huangyq23]

 Bundler::HTTPError Could not fetch specs from https://rails-assets.org/

[eveevans]

Same here...

[kelsonpw]

Also getting this error

[Awatatah]

same

[shouta-dev]

same

[Awatatah]

@joshjordan

[wkaskie]

329 suggests a mirror site. Any progress on that?

[victorlcampos]

Any suggests?

[nathanhinchey]

There's a build error in the google search results, so at least that suggests that the domain isn't expired (like in #450).

(PS: #451, so that this issue shows up in that one)

[asymptotik]

I can't afford these outages. Will be looking to dump this dependency ASAP.

[gabrielrdrguez]

Down here too

[wkaskie]

Any suggests?

• Dupe the site at another domain with another host e.g rails-assets.io
• Get a more reliable host (I'm not sure what the current host is, but AWS is a solid option)
• A more complicated solution would again require an AWS-like service, but spin up multiple servers and configure auto cutover and auto-rollback on critical failures

[victorlcampos]

Sry, I’m not the maintainer, I asked for a workaround suggestion

[johnmcauley]

Down for us also, any ideas?

[inertia186]

https://www.spritle.com/blogs/2015/09/25/three-ways-to-manage-assets-in-rails/

[gabrielrdrguez]

@victorlcampos May not work right now as it's already down, but you may use a repo manager like https://www.sonatype.com/nexus-repository-oss to act as a proxy / cache for gems

[Awatatah]

3 hours and still down...

[codeodor]

Is there any reason to not do this?

#source 'https://rails-assets.org' do
  gem 'rails-assets-tether', '>= 1.1.0'
#end

[johnmcauley]

Is there any reason to not do this?

#source 'https://rails-assets.org' do
  gem 'rails-assets-tether', '>= 1.1.0'
#end

I wont find them as there is no source.

[johnmcauley]

If you are having issues you can bundler show rails-assets-tether, copy the gem into the vendor directory and reference using https://bundler.io/v2.0/man/gemfile.5.html#PATH. Then you can deploy safely - I hope.

[victorlcampos]

We are trying bundle package to deploy safety ... I hope this work

[codeodor]

@johnmcauley

In my scenario, I was assuming source 'https://rubygems.org' would also be in the gemfile, and it would fall back to that.

So to be more clear, is there any reason not to use source 'https://rubygems.org' instead of source 'https://rails-assets.org'?

[johnmcauley]

@johnmcauley

In my scenario, I was assuming source 'https://rubygems.org' would also be in the gemfile, and it would fall back to that.

So to be more clear, is there any reason not to use source 'https://rubygems.org' instead of source 'https://rails-assets.org'?

Reference the vendor dir - see how it’s done here: https://bundler.io/v2.0/man/gemfile.5.html#PATH

[owen-c]

@johnmcauley

In my scenario, I was assuming source 'https://rubygems.org' would also be in the gemfile, and it would fall back to that.

So to be more clear, is there any reason not to use source 'https://rubygems.org' instead of source 'https://rails-assets.org'?

Yes the reason is it would not work. The rails-assets-* gems do not exist in rubygems.org

It may appear to work on your local machine b/c you have all the rails-assets-* gems installed already, but if you try to bundle install on a clean machine it will fail to find them.

[joshjordan]

Working on recovering.

On Tue, Jan 21, 2020 at 6:50 PM Owen Cummings notifications@github.com wrote:

@johnmcauley https://github.com/johnmcauley

In my scenario, I was assuming source 'https://rubygems.org' would also be in the gemfile, and it would fall back to that.

So to be more clear, is there any reason not to use source ' https://rubygems.org' instead of source 'https://rails-assets.org'?

Yes the reason is it would not work. The rails-assets-* gems do not exist in rubygems.org

It may appear to work on your local machine b/c you have all the rails-assets-* gems installed already, but if you try to bundle install on a clean machine it will fail to find them.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tenex/rails-assets/issues/462?email_source=notifications&email_token=AAD7LSSNVPWFVPF72KSMQSTQ66C2VA5CNFSM4KJYSZOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJRWX7I#issuecomment-576941053, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAD7LSV5NF37VMAXMS6CPSDQ66C2VANCNFSM4KJYSZOA .

[nonatojunior]

I'm not able to run the bundle install. This makes my project impossible to progress.

[thadeu]

seems to be down me too

[joshjordan]

Yes, when its down its down for everyone :) Working on a bit of a complex logistical issue with Digital Ocean support, I'm afraid. Will update this thread ASAP when I have more info.

[EnriqueCanals]

@joshjordan If there's anything I can do to help you resolve this issue, please don't hesitate to send over a DM. I definitely appreciate the effort put into maintaining this service, so I'm more than glad to provide any assistance I can to help resolve this outage.

[joshjordan]

@EnriqueCanals accept my request on twitter and I'll hit you up for help.

[joshjordan]

Everyone, we're at a bit of a roadblock and it may be a few hours until we've resolved it. In the meantime, this is a great chance to switch to webpacker or vendor your javascript libs to reduce your dependency footprint! Also working on a solution to host another instance of Rails Assets and repoint the DNS at that. Will let you all know, once again, when I have more to share.

[joshjordan]

We're probably about an hour away from getting this fixed.

[richpeck]

How much does it cost to keep it online?

[krazyjakee]

Is there a docker image so I can run rails-assets on my own servers? The readme has a development guide but how can I run this for production?

[madoleary]

Still down.

[HariShankarS]

Any work around ?

[jaredsohn]

Was able to work around this by removing or replacing gems that use rails-assets (could tell by looking at the list of the source 'https://rails-assets.org' section of the Gemfile). Fortunately it was only one gem and it wasn't critical. (It was just timezone detection and we used that only to set the default timezone for new users.)

[ksbek]

I use 5 rails-assets gems in my RoR project. For temporary solution, I created git repo on my github account and upload those gems to it. https://github.com/ksbek/rails-assets

And set gem path in the Gemfile like this. gem 'rails-assets-chartist', github: 'ksbek/rails-assets', branch: 'chartist' gem 'rails-assets-jquery', github: 'ksbek/rails-assets', branch: 'jquery' gem 'rails-assets-momentjs', github: 'ksbek/rails-assets', branch: 'momentjs' gem 'rails-assets-notifyjs', github: 'ksbek/rails-assets', branch: 'notifyjs' gem 'rails-assets-timeago', github: 'ksbek/rails-assets', branch: 'timeago'

[BlackAppl3]

Is there any update?

[sharshenov]

As temporary workaround might work:

1. Get server (referral link! to get credit for 2 months)
2. Spin up your own gemserver docker run -d --restart unless-stopped -p 80:9292 -P -h geminabox --name geminabox -e USERNAME=myuser -e PASSWORD=mypassword spoonest/geminabox:latest
3. Go to your bundler cache dir cd $GEM_HOME/cache
4. Push gems to your server gen inabox rails-assets-somegem-1.0.gem -g http://myuser:mypassword@yourserveraddress
5. Replace https://rails-assets.org with http://yourserveraddress in Gemfile

Then think about migrating to Webpacker or other solution

UPD: added referral link to get temporary server in case if it might be helpful to somebody

[joshjordan]

@krazyjakee I don't think so. @richpeck its not terrible, but cost isn't the primary issue right now.

If anyone is able to help out with temporary hosting, please contact me so we can work out a plan. The short of the situation is that we're locked out the Digital Ocean right now, and unable to get in to resolve the issue. Working closely with them on it.

Edit: fix wording to remove confusion.

[miguelbernadi]

@joshjordan We are willing to provide temporary hosting. Please contact me for details on setup.

[joshjordan]

Thanks for your patience, all. This is resolved. Please confirm you're able to bundle again.

[bcardiff]

As a workaround while this was being solved, I attempt to create the packages locally for vendoring.

If someone wants to go that way I dropped the following gist https://gist.github.com/bcardiff/3916e61bcce03959748468e89b53d19a

[eveevans]

I don't when this was solved, but now it is working again :)