AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Jamf pro server1/31/2024 This has been discussed a lot in the #communitypatch channel in the MacAdmins Slack, but I had been working on a major overhaul meant to address everything that was an issue, and everything that was learned with Beta 2 (the current iteration). I focused during this time on where I wanted to take the project, and what to do once those credits ran their course. I could see the trend and knew what to expect.Īs fortune would have it, the next two years of Community Patch would be funded by AWS through a combination of general use and open source credits I received. The beautiful thing about serverless apps is that consistent workflows scale linearly in price so I was never subject to sticker shock. Over time, with the kind of organic growth it has seen, Community Patch started costing more. Eventually usage went above those limits and the service cost a few dollars per month. I’m really quite proud of how this has grown, and of the value it gave to others.įor the first year of its existence, Community Patch operated entirely within AWS’s free tier. There are ~1,500 active feed subscriptions as of today. It was API driven with the hope to enable better automation, and that did eventually happen as Jamf admins began integrating patch feed updates into their AutoPkg workflows. The vision was to have a place where anyone can create and share patch definitions completely publicly. I launched Community Patch in April of 2018 where it has been serving Jamf admins for three years. It was more proof of concept than production ready service, but everything was there to transform it into a full blown resource for the Jamf community. An S3 bucket for the JSON definitions with an API Gateway to serve and manage them. I wrote the StupidSimplePatchServer that day. It started as a Slack conversation between myself and one of our developers where we identified the need to have a “stupid simple patch server” to allow people to get a cloud hosted external source running without having to do a lot of the upfront work. For more information, see the Migrating to Another Server article.įor those folks who are running on-premise Jamf Pro servers on Macs, I strongly recommend contacting Jamf Support right now and plan a migration if you haven’t already.Community Patch was my first real serverless application. If you want to keep your server on premise, you can migrate your Jamf Pro server to one of the following servers: Red Hat Enterprise Linux, Ubuntu, or Windows. If you want to migrate your Jamf Pro server from macOS to Jamf Cloud, contact Jamf Support. The Jamf Pro utilities that were included in the Jamf Pro Installer for macOS-Composer, Jamf Admin, Jamf Recon, and Jamf Remote-will be made available as a separate download. In addition, the Jamf Pro Installer for macOS will not be available to download. Mac computers with Apple silicon are not supported by the Jamf Pro Installer for macOS. Support Ending for Hosting Jamf Pro Server on macOS-Starting with the release of Jamf Pro 10.37.0, hosting the Jamf Pro server on macOS will no longer be supported. To follow up on my earlier posts on the Jamf Pro Server Installer for macOS being retired, Jamf has added the following to the Deprecations and Removals section of the Jamf Pro 10.36.0 release notes:
0 Comments
Read More
Leave a Reply. |