git-scm.com/Gemfile

# frozen_string_literal: true

source "https://rubygems.org"
ruby "3.1.3"

gem "rails", "~> 6.1"

# hacks for rails6 + ruby 3.1
gem 'net-imap', require: false
gem 'net-pop', require: false
gem 'net-smtp', require: false

gem "asciidoctor", "~> 2.0.0"
gem "elasticsearch", "7.13"
gem "iso8601"
gem "octokit"
gem "puma"

gem "diffy"
gem "nokogiri"
gem "rss"

# Assets
gem "sass-rails"
gem "uglifier"

group :development do
  gem "awesome_print"
  gem "better_errors"
  gem "binding_of_caller"
  gem "foreman"
end

group :development, :test do
  gem "dotenv-rails"
  gem "listen"
  gem "pry-byebug"
  gem "rubocop"
  gem "rubocop-discourse"
  gem "rubocop-performance"
  gem "rubocop-rails"
  gem "rubocop-rspec"
  gem "ruby-prof"
  gem "sqlite3"
end

group :test do
  gem "database_cleaner"
  gem "fabrication"
  gem "factory_bot_rails"
  gem "rails-controller-testing"
  gem "rspec-rails"
  gem "shoulda"
  gem "vcr"
  gem "webmock"
end

group :production do
  gem "pg"
  gem "rack-timeout"
  gem "rails_12factor"
  gem "redis-rails"
end
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`# frozen_string_literal: true`

			`source "https://rubygems.org"`
bump ruby to 3.1.3 There's a CVE on 3.1.2. I don't think it affects us (it's for the CGI gem), but this keeps warnings to a minimum. Since it's a minor version bump, I don't anticipate any real problems. 2023-03-16 17:51:24 +03:00			`ruby "3.1.3"`
Update about template 2014-01-22 06:10:44 +04:00
build(deps): bump rails from 6.1.7.3 to 6.1.7.7 Bumps [rails](https://github.com/rails/rails) from 6.1.7.3 to 6.1.7.7. - [Release notes](https://github.com/rails/rails/releases) - [Commits](https://github.com/rails/rails/compare/v6.1.7.3...v6.1.7.7) --- updated-dependencies: - dependency-name: rails dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> 2024-03-19 11:50:13 +03:00			`gem "rails", "~> 6.1"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00
Gemfile: include net-smtp, etc There is a weird interaction with Rails 6 and Ruby 3.1. I imagine what happened is that net-smtp, etc, are no longer in the default gem setup. Looks like Rails 7 has fixed this, but even the most recent version of Rails 6 has not. Details: https://stackoverflow.com/questions/70500220/rails-7-ruby-3-1-loaderror-cannot-load-such-file-net-smtp 2022-10-05 18:10:41 +03:00			`# hacks for rails6 + ruby 3.1`
			`gem 'net-imap', require: false`
			`gem 'net-pop', require: false`
one more pass of rubocop --autocorrect Looks like I managed to introduce 2 new problems in 2 commits. 2022-10-05 22:03:57 +03:00			`gem 'net-smtp', require: false`
Gemfile: include net-smtp, etc There is a weird interaction with Rails 6 and Ruby 3.1. I imagine what happened is that net-smtp, etc, are no longer in the default gem setup. Looks like Rails 7 has fixed this, but even the most recent version of Rails 6 has not. Details: https://stackoverflow.com/questions/70500220/rails-7-ruby-3-1-loaderror-cannot-load-such-file-net-smtp 2022-10-05 18:10:41 +03:00
Gemfile: update asciidoctor version to v2.0.x The version we're using is several years out of date. Upstream has been making more of an effort of late to make sure everything looks the same between asciidoc and asciidoctor, but all the testing is happening with more recent versions. Let's make sure we're using something comparable. 2020-04-23 21:13:37 +03:00			`gem "asciidoctor", "~> 2.0.0"`
Gemfile: :arrow_down: gem 'elasticsearch' Newer versions of the elasticsearch Gem do not communicate with Bonsai as they are not an official Elastic product, and instead raise the following error: /app/vendor/bundle/ruby/3.1.0/gems/elasticsearch-8.15.0/lib/elasticsearch.rb:103:in `verify_elasticsearch': The client noticed that the server is not Elasticsearch and we do not support this unknown product. (Elasticsearch::UnsupportedProductError) Downgrade to the highest supported version per this[1] guide from Bonsai. [1]: https://bonsai.io/docs/ruby-on-rails Singed-off-by: Taylor Blau <me@ttaylorr.com> 2024-09-06 17:59:37 +03:00			`gem "elasticsearch", "7.13"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "iso8601"`
			`gem "octokit"`
			`gem "puma"`

Speed up diff stat in manpages The diff stat is now done by raw analysis of diff command output. For instance for git-config man page we switch from: Completed 200 OK in 7349ms (Views: 7148.4ms \| ActiveRecord: 134.3ms \| Allocations: 5879568) to: Completed 200 OK in 737ms (Views: 590.1ms \| ActiveRecord: 139.2ms \| Allocations: 658373) which is a 10x speed up 2021-01-09 19:38:37 +03:00			`gem "diffy"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "nokogiri"`
Gemfile: add rss gem This is no longer a default gem in 3.1.2, so we have to include it specifically. 2022-10-05 14:44:04 +03:00			`gem "rss"`
rails gen 2012-03-06 20:52:03 +04:00
Clean up Gemfile 2013-10-28 00:58:45 +04:00			`# Assets`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "sass-rails"`
bump ruby and rails versions Our versions are quite old, and cause various headaches. E.g., Travis CI now uses bundler 2.2, many of our gems require something older than 2.0. We've also run into issues with being unable to easily pick security updates from dependabot (which I hope this will resolve). We're very light on what rails and ruby features we actually use, so it shouldn't be that big a deal to make a big jump up from Rails 4 to Rails 6. And likewise to Ruby 2.7.2, which is the latest stable. There's a little fallout here, which I'll fix in the next couple of commits. 2020-12-11 21:29:17 +03:00			`gem "uglifier"`
setting up 2012-03-06 21:15:36 +04:00
			`group :development do`
Clean up Gemfile 2013-10-28 00:58:45 +04:00			`gem "awesome_print"`
Add better_errors gem 2014-07-25 07:18:53 +04:00			`gem "better_errors"`
			`gem "binding_of_caller"`
Use Unicorn 2013-11-24 04:34:29 +04:00			`gem "foreman"`
setting up 2012-03-06 21:15:36 +04:00			`end`
App updates for finding/displaying the right doc * model updates to find the current/specified version of a man page * controller updates to load up the right doc * view updates to display the pregenerated HTML * tests 2012-04-04 04:00:14 +04:00
Use Unicorn 2013-11-24 04:34:29 +04:00			`group :development, :test do`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "dotenv-rails"`
Gemfile: move "listen" gem to development This is for picking up changed asset files; it's not needed in production. 2021-07-13 20:22:47 +03:00			`gem "listen"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "pry-byebug"`
replace rubocop-github gem with vanilla rubocop It doesn't make much sense to use the -github variant, which is designed for GitHub-specific projects (which we are not). Moreover, they depend on an old version of rubocop which doesn't know about our more recent ruby version. So let's just swap it out for the regular rubocop gem. We'll need to add the -rails and -performance dependencies ourselves. And while we're here, we'll bump the targer ruby version in the rubocop file. 2022-10-05 11:39:44 +03:00			`gem "rubocop"`
Gemfile: add rubocop-discourse Again, our CI seems to require it. I'm not clear on why. Guess and check for the win. 2022-10-05 16:37:56 +03:00			`gem "rubocop-discourse"`
replace rubocop-github gem with vanilla rubocop It doesn't make much sense to use the -github variant, which is designed for GitHub-specific projects (which we are not). Moreover, they depend on an old version of rubocop which doesn't know about our more recent ruby version. So let's just swap it out for the regular rubocop gem. We'll need to add the -rails and -performance dependencies ourselves. And while we're here, we'll bump the targer ruby version in the rubocop file. 2022-10-05 11:39:44 +03:00			`gem "rubocop-performance"`
			`gem "rubocop-rails"`
Gemfile: add rubocop-rspec I had earlier tried to avoid this, but it looks like our CI environment insists on having it (perhaps because in the test environment, we load the rspec gem; I didn't investigate further). 2022-10-05 16:35:48 +03:00			`gem "rubocop-rspec"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "ruby-prof"`
Use Unicorn 2013-11-24 04:34:29 +04:00			`gem "sqlite3"`
			`end`

App updates for finding/displaying the right doc * model updates to find the current/specified version of a man page * controller updates to load up the right doc * view updates to display the pregenerated HTML * tests 2012-04-04 04:00:14 +04:00			`group :test do`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "database_cleaner"`
			`gem "fabrication"`
Gemfile: sort grouped entries This appeases rubocop's Bundler/OrderedGems. 2020-12-13 07:06:11 +03:00			`gem "factory_bot_rails"`
			`gem "rails-controller-testing"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "rspec-rails"`
Gemfile: include shoulda Prior to this commit, we just included shoulda-matchers. But with more modern ruby/rails, I get errors like: test/unit/book_test.rb:7:in `<class:BookTest>': undefined method `should' for BookTest:Class (NoMethodError) when running the tests. This clears it up. 2020-12-13 01:58:58 +03:00			`gem "shoulda"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "vcr"`
			`gem "webmock"`
App updates for finding/displaying the right doc * model updates to find the current/specified version of a man page * controller updates to load up the right doc * view updates to display the pregenerated HTML * tests 2012-04-04 04:00:14 +04:00			`end`
Move production gems to their own group 2018-03-11 22:43:53 +03:00
			`group :production do`
Gemfile: drop version in pg dependency This seems to cause problems on Heroku, which otherwise would be using pg 1.1. We don't do anything fancy, so we shouldn't really care either way. 2020-12-13 09:48:59 +03:00			`gem "pg"`
Introduct rubocop with GitHub config 2018-10-29 01:57:57 +03:00			`gem "rack-timeout"`
			`gem "rails_12factor"`
			`gem "redis-rails"`
Move production gems to their own group 2018-03-11 22:43:53 +03:00			`end`