Development workflow for Heroku?

I used Heroku to push already coded Rails applications.

But now I'm wondering what the workflow will look like if I start coding a new Rails application from scratch.

For example, if I use my add-ons (MongoHQ, Redis, Websolr, Sendgrid, etc.) in my application code, then I think I should not install MongoDB, Redis, Solr, Mail server, etc. in your local environment, t work with my code, right?

So this means that I have to push my application to the Heroku platform in order to be able to run it in a web browser. This means that after changing the lines, I have to lock and push it.

If I’m right, it doesn’t take much time, because before that I just changed the code and I immediately saw the results in the browser. Now I have to insist on every change that I want to see in the browser.

+3
source share
2 answers

You can install all this locally - you will only need to specify different configurations when you work in the production process, and not in development.

For example, using Websolr by adding the following line to your initializer:

Sunspot.config.solr.url = ENV['WEBSOLR_URL'] if ENV['WEBSOLR_URL']

Allows him to work both locally and on Heroku. See the docs for more details .

+3
source

, , , .

, Sendgrid , ActionMailer . - . - ( sendmail smtp-)

( API).

MongoHQ... PostgreSQL? , , PostgreSQL, MySQL.

+1

Source: https://habr.com/ru/post/1769094/


All Articles