Interacting with Production
Read Access
For diagnostic access, use the readonly app (wunder-portal-production-read). This app is a full copy of the production application, but it points to a follower database, to which the app only has read access.
The readonly app does have active API keys for third party services (e.g. Google, Redis, etc.), so it is still possible to cause side effects in some cases.
Write Access
If you need to perform writes in production, the encouraged practice is to add a script app/scripts and getting a review. There is a generator to get started:
rails g script <script class name>
With that said, you do have direct access to wunder-portal-production and can perform writes in the console. If you are doing this for the first time, you should pair with someone on whatever you’re doing.
If you perform a console write, you must document what you’re doing in the #portal-ops channel in Slack. The format is to preface a short summary of the activity with “Console [write],” and then copy and paste the commands you run into the message’s thread.
Changing Heroku Configuration
Similarly, if you need to reconfigure the production app via Heroku (e.g., change an environment variable) then it’s customary to post an update to #portal-ops starting with “Heroku [write].”