Can a day be good and bad?
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
This reminds me of the argument between a husband and wife. She was talking about mixed feelings, but her husband insisted that the concept was nonsense, because everything was ultimately positive or negative. "Out of all your friends", she replied, "you have the biggest dick."
<p><a href="https://github.com/GregUtas/robust-services-core/blob/master/README.md">Robust Services Core</a>
<em>The fox knows many things, but the hedgehog knows one big thing.</em></p> -
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
This reminds me of the argument between a husband and wife. She was talking about mixed feelings, but her husband insisted that the concept was nonsense, because everything was ultimately positive or negative. "Out of all your friends", she replied, "you have the biggest dick."
-
I had the exact same thing happen...seemed to be something with SSRS bindings.
"Go forth into the source" - Neal Morse
At least I can rule out that as my problem.
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
A day can be both good and bad. - A lawyer dies in an horrible accident. - Another hip-hop/rapper becomes a "star". This is a typical good day/bad day situation.
- I would love to change the world, but they won’t give me the source code.
Forogar wrote:
- A lawyer dies in an horrible accident.
That reminded me of: A huge tyrannosaurus ate our lawyer Well, I suppose that proves they're really not all bad[^] :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
You take the good. You take the bad. You take them both...
And that's how it is.
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
-
This reminds me of the argument between a husband and wife. She was talking about mixed feelings, but her husband insisted that the concept was nonsense, because everything was ultimately positive or negative. "Out of all your friends", she replied, "you have the biggest dick."
Better than the opposite.
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
yes
-
My day started with some bugs from previous days (that seemed to pile up) and all but one have been resolved. That one bug seems to be out of my league though, and I've spent so much time on it already that I can't charge the customer for it anymore... 1. Web app wouldn't start - Fixed (some weird issue with Application Insights, so I just disabled AI). 2. AI would be reinstalled upon deployment and web app wouldn't start again as a result - Fixed. 3. The Lets Encrypt extension wouldn't install correctly from an ARM template - Fixed. 4. Lets Encrypt wouldn't install an initial certificate - Fixed (by doing that by hand, I'm assuming the certificate will be automatically renewed in 60 days). 5. Lets Encrypt won't install an initial certificate at all for a WCF service I'm running - PULLING MY FREAKING HAIRS OUT ON THIS ONE!!! :mad: Alright, so I admit 1 through 4 have some shortcuts with disabling AI and manual labor, but I need to be practical too. It's still some nasty issues that I don't have to worry about for now (AI can be turned back on later when I know why it didn't work). But that number 5 is really ruining my day. I'm getting some 403 Forbidden status and I really don't know why. I can't really find any differences with my ASP.NET Core web services... My Google-fu is leaving me hanging as well. Ah well, let's stay positive, 4 out of 5 isn't bad :sigh: Perhaps I'll wake up in the middle of the night and I'll have my answer. At least the websites work with a custom domain name and a valid certificate. The third party application that talks to the WCF service doesn't even check whether a valid certificate is installed so I guess that's just a nice to have anyway :laugh:
Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
to the extent you waste your time over-analyzing it, and posting on the Lounge about it: yes :wtf:
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
