Michael D.’s Post

View profile for Michael D., graphic

"Making the world a better place"™

Originally posted on X: https://lnkd.in/gkx-5DHf starbeam.one Daily Status - The oofness continued yesterday but a little less offness-y. I was able to locally test the new withdrawal functionality and direct the user to the refund if they have one available. I am feeling good about that and now it's time to deploy to a place where others can test it. This brings up another issue in my world with Azure deployments and I started additional work around this. There is an issue with Azure where resources will hang if deployments are deployed, deleted, and then deployed again. Azure states the resources are deleted, but they really are not. It's not a bug either, just ask the support ticket that I have had open for over 4 months now. 🙄 The "recommendation" is to generate a suffix to add to the resources deployed so that the names used are different for each deployment. I started this work yesterday and have the key pieces in place, but there is some further work to be done around it. Unfortunately I also have personal errands today with this morning getting a treadmill replaced. This means dismantling the old one and preparing for the new one which is a 300lb monster. That will take my morning and then I have a few meetings this afternoon. I doubt I will get much if any work done today on sb1 but we'll see if I can get lucky here. #StarbeamOne #sb1 #DailyDeveloper #Startup #Status #azure #blazor #csharp #dotnet #buildinpublic #buildinginpublic

Mike-E-angelo @ starbeam.one (@Mike_E_angelo) on X

Mike-E-angelo @ starbeam.one (@Mike_E_angelo) on X

twitter.com

To view or add a comment, sign in

Explore topics