Difference between revisions of "Deploy .NET to Docker"

From MgmtWiki
Jump to: navigation, search
(Solutions)
(Solutions)
Line 10: Line 10:
 
==Solutions==
 
==Solutions==
 
There are two distinct parts fo the dealoyment and maintenance of the application plus a little bit of glue to stick one part to the other.
 
There are two distinct parts fo the dealoyment and maintenance of the application plus a little bit of glue to stick one part to the other.
===Deployibg the App via Github.com===
+
===Deploying the App via Github.com===
 +
# An access token is required from GitHub.
 +
 
 
===Setting up a HTTPS connection===
 
===Setting up a HTTPS connection===
 +
This section shows the the of [[Let's Encrypt]] certificates, which have a life of just 3 months, but is free.  Other sites have a life of one year but charge money. Two year certificates are no longer acceptable to many browsers.
  
 
==References==
 
==References==
  
 
[[Category: Best Practice]]
 
[[Category: Best Practice]]

Revision as of 14:49, 31 December 2021

Full Title or Meme

How to move an application from Visual Studio to a Docker Container on Digital Ocean.

Context

Most Docker solutions work well with Apache or NGINX, some special considerations are needed to get a simple task from from .NET on Visual Studio.

Problems

  • Most sites now use Let's Encrypt Certificates which come with simple scripts for Apache, but no help for Windows.

Solutions

There are two distinct parts fo the dealoyment and maintenance of the application plus a little bit of glue to stick one part to the other.

Deploying the App via Github.com

  1. An access token is required from GitHub.

Setting up a HTTPS connection

This section shows the the of Let's Encrypt certificates, which have a life of just 3 months, but is free. Other sites have a life of one year but charge money. Two year certificates are no longer acceptable to many browsers.

References