I also created two functions: a timer trigger and service bus trigger as below: func new -t TimerTrigger -n TimerTriggerįunc new -t ServiceBusQueueTrigger -n ServiceBusTrigger I put together a super simple code just to prove a point and to be able to share here and to create a Function App I went to the terminal and ran: mkdir FunctionsOnMac If you haven't installed the Azure Functions Core Tools yet, do follow the steps from the Microsoft docs. So let's see how it goes.įirst I installed Azurite by running sudo npm install -g azurite, once it was installed I kicked it off by simply running azurite-blob. I was pumped and decided to give another chance for the Mac to be my main work machine again. Time has passed and by accident I found out a community maintained open source storage emulator called Azurite. I WAS SAD I stopped using the Mac for Azure Functions development but life goes on and there's no looking back.
Without the Storage Emulator, I could only run locally Azure Functions with HTTP triggers, and well within my solution that was the trigger I used the least.
I hit a massive road block, I found out that the tooling I needed to develop Azure Functions wasn't available for Mac and that was a deal breaker. NET Core which is cross platform and front end development. I was super excited to have the shiniest laptop in town and I was sure I could do all my work on it since most of what I did was. I started writing this blog post a very long time ago when I switched for the first time in my life to a Mac as my main computer. Finally, we need to resolve the certificate trust process between the application running on the Linux or Mac environment and the Emulator.