top of page
Search

Heroku Rails application with Quotaguard Shield proxy server

Writer: Andres Ehrenpreis
Andres Ehrenpreis
Nov 12, 2021
1 min read



Installation

Installing was done completely with tutorials given here: https://devcenter.heroku.com/articles/quotaguardshield#https-proxy-with-qgpass


qgpass

As I also needed the HTTPS to be possible I followed the instructions and installed the qgpass too as described here: https://devcenter.heroku.com/articles/quotaguardshield#https-proxy-with-qgpass


If so far I didn't have to change how the dyno in Heroku is started for my Rails application then now with qgpass active I had to include it in starting the application as well. For that I did the following:

  1. Added a `Procfile` to my project's root path. If this file is not present, Heroku will use the default instructions for starting the dyno. With Procfile present, it will override the startup command with Procfile contents.

  2. Filled the procfile with the following:

web: bin/qgpass bin/rails server -p ${PORT:-5000} -e $RAILS_ENV

Accessing Heroku Rails console with qgpass

If previously you could access your Rails console with just

heroku run -a APP_NAME rails console

then now you have to always include qgpass as well if you should need proxy-server in console. For that instead you should start using the following command:

heroku run -a APP_NAME bin/qgpass rails console

PS! If you liked the article you can buy me a coffee to support me going! :)



Recent Posts

See All

Comments


bottom of page