Local installation of discourse on Centos 7

AI-generated summary

Local Installation of Discourse on Centos 7 Issues

sanek190 is experiencing an error while installing Discourse offline on Centos 7. The error occurs when trying to install Ruby packages from rubygems.org, despite having a local copy of the repository. They have tried copying the local repository to the correct location, but the issue persists.

sam suggests that the problem might be due to the IP address being blocked by rubygems.org and recommends rebuilding the installation.

Hello everyone!

I receive an error installing discourse offline at a step:

[2020-05-05T17:36:59.349388 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4 --verbose'

Retrying fetcher due to error (2/4): Bundler::HTTPError Could not fetch specs from https://rubygems.org/
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle install --retry 3 --jobs 4 --verbose' failed with return #<Process::Status: pid 340 exit 17>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["cp -rv /local-rubygems.org/ruby/* $home/vendor/bundle/ruby/", "su discourse -c 'bundle config set deployment \"true\"'", "su discourse -c 'bundle config set without \"development test\"'", "su discourse -c 'bundle install --retry 3 --jobs 4 --verbose'"]}
6637602e5976e07b9e36197d0f6d55a38d528df1688e7fc87173d30aec4e28a5
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

But I perform this command:

docker run -it -v ~/local/rubygems.org:/local-rubygems local_discourse/app /bin/bash
cp -r /var/www/discourse/vendor/bundle/ruby /local-rubygems 

Shouldn’t it run ruby locally after that? There are no problems with the Internet on the server. What should be turned off and where is it written not to let it to the site?

This is an issue contacting rubygems which is the global repository for all ruby packages on the Internet.

Recommend you rebuild.

Maybe your IP address has been naughty or is in a naughty range and being blocked by rubygems.