Alexander Balashov's Profile

If you want to use Twitter authentication in https://teatro.io/ first create special stage application in Twitter and then set domain as project-token.ttrcloud.com and authentication urls as http://project-token.ttrcloud.com. It will work on any branch of this project.

If you want to use Facebook authentication in https://teatro.io/ first create special stage application in Facebook and then set domain as project-token.ttrcloud.com and authentication urls as http://project-token.ttrcloud.com. It will work on any branch of this project.

If you want to use sidekiq in https://teatro.io/ you need to create Procfile like this:

web:     bundle exec rails server
sidekiq: bundle exec sidekiq

If you need just staging server you could use https://teatro.io/

It's easy to test UI changes with https://teatro.io/

If you need VPS just for stage you can use https://teatro.io/ instead.

Adding separate env for staging looks like not a good idea, because it will differ from real production. BTW you can use special service for stages https://teatro.io/ that will automate the whole process.

BTW http://teatro.io/ will help you test it

Try https://github.com/evrone/factory_girl-seeds to speed up your tests

Try https://github.com/evrone/factory_girl-seeds to speed up your tests

This gem https://github.com/evrone/factory_girl-seeds helps to minimize total spec run time by preloading records for factory_girl and then use them in spec.

Ryan, FactoryGirl.build implictly creates records in database when it has associations. Maybe it's better to use just Model.new for things like validations instead of build()?