* Upgrade to Ruby 2.7.0
* Upgrade Travis's Ruby as well
* Fix conflict
* Silence all Ruby 2.7 deprecation warnings in dev mode
* Silence dev and test unless CI
I was unable to fully use pry using the docker version of dev.to.
For instance while trying to examine certain variables or trying to use
`caller` to checkout the backtrace, I would run into the a `multi-call binary error` with
`BusyBox`.
On looking up this error, discovered https://github.com/pry/pry/issues/1248 which also
had the fix which was simply to install less for the docker image.
Verified locally that pry's full functionality works.
* The previous Dockerfile was using and outdated format and was causing
heavy load times.
The number of the lines in the Dockerfile are defined as layer, with more
layers more time and bigger is the final image.
There were many things that were able to be delegated to the official ruby
docker image.
* - Use yarn community package
- Don't create the workdir directory since is created by docker if doesn't exists
- Remove config/application.yml from .dockerignore
* Update Dockerfile
Co-Authored-By: Abenet Tamiru <mail@abenet.me>
* Update Dockerfile
Co-Authored-By: Abenet Tamiru <mail@abenet.me>
* Add directory copy, and user correct folder in compose
* Update docker-compose and Dockerfile
* Fix typo
Co-Authored-By: Mac Siri <krairit.siri@gmail.com>
* Update wording
Co-Authored-By: Mac Siri <krairit.siri@gmail.com>
* Upgrade to Ruby 2.6.0
* Change Ruby version in guides and in travis
* Upgrade Rubocop
* Change Rubocop version for code climate
* Update .codeclimate.yml
* Update badge
I just tried going through the Docker installation guide and I got the following warning:
> Warning: the running version of Bundler (1.16.3) is older than the version that created the lockfile (1.16.6). We suggest you upgrade to the latest version of Bundler by running `gem install bundler`.
This way the build should always use the latest version of Bundler
