Release v2.0 #526
Merged
Release v2.0 #526
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pg-search-la-buena Switch from elasticsearch to PostgreSQL text search
… we are not ready yet)
fix features specs + upgrade some "group :test" gems
Install correct Bundler version on Travis CI
New translations
Revert full text search
…onse to make tests work with the combo Rails 4.2 & Ruby 2.6)
Ubuntu Bionic
I got the following strange error ``` /home/timeoverflow/.rbenv/versions/2.6.3/lib/ruby/gems/2.6.0/gems/net-ssh-2.9.2/lib/net/ssh/transport/kex/diffie_hellman_group1_sha1.rb:118:in `generate_key': undefined method `p=' fo r #<OpenSSL::PKey::DH:0x000055d6c5685910> (NoMethodError) Did you mean? p (Backtrace restricted to imported tasks) cap aborted! NoMethodError: undefined method `p=' for #<OpenSSL::PKey::DH:0x000055d6c5685910> Did you mean? p ``` and updating fixed it.
Update Capistrano from 3.4.0 to 3.4.1
It was added in the very beginning of the project in commit `e37eb7d` but it doesn't seem to be used anywhere. Leftovers of an old copy-paste?
No need to install this extension used by full-text search until we don't replace ElasticSearch with it. Still, it was added in `f514c35` in the early days (2013) for user search but it doesn't seem to be used. You @enricostano and @markets might now better.
Remove pg_trgm PostgreSQL extension
Remove plpgsql PostgreSQL extension
Add spec for brand logo case when no user is signed in
improve readability
This is the upgraded server we are setting up to host the app. Time to deploy and start testing! 🎉 The Capistrano environment is tightly coupled with Rails environments so we need to add a new one called `next`.
This needed when deploying to a server for the first time or when you want to wipe out a database. The issue I'm fixing is this. Things have evolved and in https://github.com/coopdevs/timeoverflow-provisioning we no longer set things up to enable PostgreSQL extensions such as `pg_trgm`. Because Capistrano runs `db:migrate` when deploying very old migrations like `db/migrate/00000000000002_setup_pg_trgm.rb` don't work anymore. I prefer to make this step explicit in the code and with some context rather than having to do this manually in the server and let the dev in charge figure it out every time. Apparently, from capistrano/rails#118 I see this is a known issue for which there's no provided solution. I copied a solution proposed by a capistrano/rails member so should be good. Just run it as follows: ``` $ bundle exec cap staging deploy COLD=1 ```
Add next.timeoverflow.org Capistrano deploy
It comes installed in Travis CI boxes. This might fix the service start, which is currently timing out. See details: #525 (comment)
Do not reinstall PostgreSQL 9.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Creating a new release that includes the following changes: