Jump to content

Jaime

Members
  • Posts

    2
  • Joined

  • Last visited

  • Days Won

    1

Jaime last won the day on November 11 2022

Jaime had the most liked content!

Jaime's Achievements

Newbie

Newbie (1/14)

  • One Month Later
  • Week One Done
  • Great Content Rare
  • Conversation Starter

Recent Badges

1

Reputation

  1. I've used AutoPKGr to grab the latest version of Chrome and load it into our FileWave server. I've also used it to download Cricut Design Studio, but I've always had to add that into a fileset manually. I know there is a way to make a new autopkg recipe and I know it is possible to include uploading an *.app bundle into a fileset (since the recipe for Chrome does this), but I don't know how. I've tried to read the recipes that already exist and I've looked for documentation, but it hasn't really made sense to me yet. Can anyone point me in the right direction for learning how to make new autopkg recipes that upload to FileWave? Assume that I already have a recipe that can download the DMG file. I just need to figure out how to extract the *.app inside it and put that into a fileset. I can figure out the rest, e.g. association to a smart group, etc.
  2. I showed this to someone on FileWave's tech support and they suggested that I post it here to help others. Almost a year ago, I figured out how to make Let's Encrypt's free SSL certificates work with FileWave 14.x on Linux. I've revised it a bit over the months and then I wrote up the directions on my blog in case anyone else might benefit. https://www.reviewmynotes.com/2022/10/filewave-and-lets-encrypt.html The one side effect I know of (and I just realized this about an hour ago) is that the manually enrollment for iOS devices (https://your.server.here:20443/ios) shows two steps when it only needs to show the second step and not the first. I think this is because I'm "hacking" the certificate into the system on the backend instead of importing it into the system through an officially supported front end. But that side effect is easily worked around by just telling any end users to skip step #1 on that page. I hope this helps someone out there. Enjoy.
×
×
  • Create New...