TerribleDev/blog.terrible.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix blurb

Browse Source
This commit is contained in:
Tommy Parnell
2021-07-19 19:19:55 -07:00
parent d46c44dc97
commit 84356eba1e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/TerribleDev.Blog.Web/Posts/Hosting-dotnet-core-on-heroku.md
View File

@@ -19,7 +19,7 @@ To host apps on Heroku, you must know the basic *rules of Heroku*
1. Your app must listen on `$PORT` or `%PORT%` if you come from windows. Basically, any http listeners must listen to the port defined as an environment variable.
2. Postgres is free (to a point), redis is free, most other things cost money.
3. Logs must go to `stdout` which works well for us since that's the default behavior of asp.net core!
4. In dotnet core authentication cookies are encrypted and the key is usually placed in your profile, but in Heroku your app could be moved at any moment
4. In dotnet core authentication cookies are encrypted and the key is usually placed in your home directory, but in Heroku your app could be moved to any machine at any moment. The filesystem needs to be stateless
5. Heroku gives you your Postgres connection string as `postgres://<username>:<password>@<host>:<port>/<database>`