You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2021-03-23-outlook-spam-rule.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ For me, the easiest way to pull up email rules is to click on the settings icon
26
26
27
27
From here click `Add new rule`. A create rule screen will appear and you can start setting up the rule. I named my rule "Not from {organization} is Junk". Under condition choose `Apply to all messages`. This may seem wrong at first, but it will make more sense in a second.
Copy file name to clipboardExpand all lines: _posts/2021-04-08-asp-net-core-server-setup.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,21 +23,21 @@ First things first, make sure you can remote into the server, and make sure you
23
23
24
24
This step is simple, but sometimes finding the install bundle isn't. Start by going to the [dotnet download page](https://dotnet.microsoft.com/download) where you'll see several available versions. I typically choose the current **LTS** version, but _ultimately the version will need to match whatever version of dotnet your app is running_.
My app currently uses 3.1 LTS, so I'll pick **Download .NET Core Runtime** under that version and then on the next page specifically choose **Download Hosting Bundle**. The hosting bundle is critical because it will install a necessary IIS ISAPI filter for ASP.NET Core. Once you have your bundle, simply install it on the server, and finally restart. To confirm your version is installed, run `dotnet --info` in powershell. The _Host_ section should reflect the version you just installed.
29
29
30
30
> Don't be discouraged if you see a message saying **It was not possible to find any installed .NET Core SDKs**. The SDK is a separate install, and is not required for runtime.
To do this, choose the website that will respond to HTTPS requests from the left menu, often the default, and click bindings on the right menu. Click _Add..._ and select type `https`. For my purposes, IP address is set to `All Unassigned` and the port stays the default 443. Last but not least I select the certificate I want to use below. This should align with whatever your server url will be. As I said before, my certificates came preinstalled, so I just had to choose the right one.
43
43
@@ -46,15 +46,15 @@ Next I add some security minded headers to the default return headers. In the ro
Usually I would add and HSTS header here also, but in IIS for server 2019 there is a new, easy way to manage this. Going back to the website you previously configured to response to https requests, there is now a _HSTS_ button near the bottom of the right hand menu. I enable HSTS and configured max-age to 2628000 (1 Month). I also check `Redirect Http to Https`. Keep in mind, if you're going to make certificate changes or run the app over unsecured HTTP, you'll want to set the max-age low or you will be stuck making TLS requests for the set duration, **even if you change it later**
Next I remove the `Server` and `X-Powered-By` headers. You should have seen `X-Powered-By` in root server options _HTTP Response Headers_. Delete it to remove it from the default response headers. The `Server` header is a bit more tricky. In the root server options, find _Configuration Editor_ in the Management section. Then go to section `system.webServer/security/requestFiltering` and set `removeServerHeader` to `true`. Once you click apply on the right menu, the header should be removed.
IIS should now be upgrading all requests to HTTPS automatically, and a response should only return the desired headers.
60
60
@@ -72,7 +72,7 @@ This is the only way I've found to prevent WebDAV from interfering with PUT and
72
72
73
73
Finally, I always install an [Azure Devops](https://azure.microsoft.com/en-us/services/devops/) agent. In Azure Devops > Organization Settings > Deployment pools, I click new on the top menu. Setting the deployment pool name and projects I want to allow deployments to, I create the new pool. From here, you should see the details tab of the new pool. On the right is the agent install powershell script. I usually check _Use a personal access token in the script for authentication_. You'll need to run this script on the server in an elevated powershell window (as Administrator). Once this is complete, you should see your server appear in the Deployment Pool's Targets tab.
With this one line, I can start a Windows Terminal with both scripts running in tabs. This allows me to keep both together and but also manage the window as one unit. The commands are similar, but the tabs are labeled, so I can quickly jump where I need to look. Also, this is far more expandable if I needed to run other startup scripts together in the future.
Copy file name to clipboardExpand all lines: _posts/2022-12-18-install-pihole-ha.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,11 +46,11 @@ Always enable dark mode in <u>Settings</u> > <u>API / Web interface</u> > <u>Web
46
46
47
47
Because my network sets DNS per client, and not just per gateway, each client will make DNS requests directly to my Pi-hole instance. This is better for logging, but means that Pi-hole needs to be behind a firewall, and must permit all origins. This can be configured in <u>Settings</u> > <u>DNS</u> > <u>Interface Settings</u>
48
48
49
-
0 commit comments