README.md in pliny-0.8.2 vs README.md in pliny-0.9.0

- old
+ new

@@ -22,11 +22,11 @@ - [Puma](http://puma.io/) as the web server, [configured for optimal performance on Heroku](lib/template/config/puma.rb) - [Rack-test](https://github.com/brynary/rack-test) to test the API endpoints - [Request IDs](lib/pliny/middleware/request_id.rb) - [RequestStore](http://brandur.org/antipatterns), thread safe option to store data with the current request - [Sequel](http://sequel.jeremyevans.net/) for ORM -- [Sequel-PG](https://github.com/jeremyevans/sequel_pg) because we don't like mysql +- [Sequel-PG](https://github.com/jeremyevans/sequel_pg) to talk to the world's most advanced open source database - [Versioning](lib/pliny/middleware/versioning.rb) to allow versioning your API in the HTTP Accept header ## Getting started First make sure the following is installed: @@ -110,12 +110,10 @@ ```bash rake db:create # Create the database rake db:drop # Drop the database rake db:migrate # Run database migrations -rake db:nuke # Nuke the database (drop all tables) -rake db:reset # Reset the database rake db:rollback # Rollback the database rake db:schema:dump # Dump the database schema rake db:schema:load # Load the database schema rake db:schema:merge # Merges migrations into schema and removes them rake db:seed # Seed the database with data @@ -132,9 +130,16 @@ $ foreman run bin/console # IRB/Pry console $ foreman run bin/run 'puts "hello world"' # Run automated code ``` (hint: don't forget `foreman run` in development) + +### Updating + +Use `pliny-update` to update the Pliny app in the current directory. + +This not only bumps the version dependency, but also applies any changes that happened in the template app (for instance: new initializer, tweaks in the base endpoint, etc). + ## Development Run tests: