Merge pull request #309 from tbrlpld/update-readme

Remove staging section

README.md

@@ -155,29 +155,3 @@ The restoration is handled in the `./scripts/release.sh` script.
 Because the release and run command are run in different containers on Heroku, the release commands need to be run in the run script too.
 The initial run of the release commands in the release phase is to make sure that the app is in a releasable state.
 The run of the release commands in the run phase is actually applying the changes to the live environment.
-
-### Scale down Heroku Dynos
-
-Heroku has removed their free plan.
-That means having an idle server that is practically not running will start to cost money.
-This is a bit of a pain, because I was using the free Dyno for a staging server for my site.
-My site is not that important and I could probably do without a staging server, but I like having this stop gap between my local setup and the production one.
-
-It turns out, the paid plans for [Heroku are prorated to the second](https://www.heroku.com/pricing).
-I did not know that because I was only running a single paid app and the was on all the time, I never needed any scaling.
-But now this becomes interesting.
-I hardly need the staging server and I am ok with paying for the few times that I need it.
-To not pay the full month for the staging server that I basically never need, I can just scale it down to 0 instances, with:
-
-```console
-heroku ps:scale web=0 -a lpld-io-staging
-```
-
-If I need to access it, I just need to scale it up again.
-
-```console
-heroku ps:scale web=1 -a lpld-io-staging
-```
-
-Autoscaling if not an option, because that is only available on the more expensive plans.
-But for now I am ok with doing it manually.