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

some minor editing

Browse Source
This commit is contained in:
Tommy Parnell
2021-07-19 16:18:15 -07:00
parent 0ddf58d2dc
commit d46c44dc97
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.vscode/spellright.dict vendored
View File

@@ -3,3 +3,4 @@ docker
env env
mydocklinting mydocklinting
eslint eslint
webapps

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

@@ -8,7 +8,7 @@ tags:
--- ---
I've been getting back into building scrappy little web apps for my friends. Ontop of this, I recently joined [a startup](https://quala.io) and getting away from Enterprise class software has made me make a huge mindshift. In the recent past when I wanted to build apps I was thinking Kubernetes, Helm Charts, etc. However, in small app, and startup land reducing the barriers to ship is very important. I've been getting back into building scrappy little web apps for my friends. On top of this, I recently joined [a startup](https://quala.io) and getting away from Enterprise class software has made me make a huge mind-shift. In the recent past when I wanted to build apps I was thinking Kubernetes, Helm Charts, etc. However, in small app, and startup land reducing the barriers to ship is very important.
<!-- more --> <!-- more -->
@@ -20,7 +20,7 @@ To host apps on Heroku, you must know the basic *rules of Heroku*
2. Postgres is free (to a point), redis is free, most other things cost money. 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! 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 profile, but in Heroku your app could be moved at any moment
5. Heroku gives you your postgres connection string as `postgres://<username>:<password>@<host>:<port>/<database>` 5. Heroku gives you your Postgres connection string as `postgres://<username>:<password>@<host>:<port>/<database>`
@@ -57,7 +57,7 @@ This configures your app to use SqlLite as a DB, we need to switch this. Luckily
`dotnet add package Npgsql.EntityFrameworkCore.PostgreSQL` `dotnet add package Npgsql.EntityFrameworkCore.PostgreSQL`
Then simply swap the previous code block for the following, which will parse the database url from Heroku and setup a postgres connection. You can use the following docker-compose file and `appsettings.Development.json` for local development. Then simply swap the previous code block for the following, which will parse the database url from Heroku and setup a Postgres connection. You can use the following docker-compose file and `appsettings.Development.json` for local development.
```csharp ```csharp
var databaseUrl = Configuration.GetValue<string>("DATABASE_URL"); var databaseUrl = Configuration.GetValue<string>("DATABASE_URL");
@@ -156,7 +156,7 @@ ENTRYPOINT ["dotnet", "MyApp.dll"]
``` ```
I then found someone had made a *build a docker image and push to Heroku* github action. All I had to do is make this a file in `.github/deployContainerToHeroku.yml`, turn on Github actions, and register my Heroku API key as a secret in github I then found someone had made a *build a docker image and push to Heroku* GitHub action. All I had to do is make this a file in `.github/deployContainerToHeroku.yml`, turn on Github actions, and register my Heroku API key as a secret in GitHub
```yml ```yml