Gatekeeper is a security feature on macOS that is designed to protect your system from malicious software by limiting the apps that can be installed and run on your system. Only allowing apps that are downloaded from either the Mac App Store or from those who have signed their apps with a certificate issued by Apple.
While it’s extremely useful for keeping your macOS environment secure, there are times when a user may need to disable Gatekeeper temporarily.
My organization’s use-case for this is that we have a team of developers who are often running test builds of applications that are unsigned because they’re in development. So we have a process for user’s to go through to disable Gatekeeper temporarily.
However, we want to ensure that there are no gaps and that Gatekeeper will always be re-enabled across the environment.
To accomplish this, we leverage Jamf Pro’s Smart Groups to detect if Gatekeeper is disabled (the status of machines in this group will update after an inventory scan on each device) and a script deployed via a Jamf policy to re-enable it on the machines that show up in our smart group.
I have a large (like, hundreds of GB’s) digital library of comic books that I’ve acquired over a decade of hoarding. Obviously, content has come from all kinds of different sources over the years and so the quality of the metadata ranges wildly, from very detailed to non-existent, from file to file.
It’s an extremely powerful free and open-source program designed for organizing and managing digital comic book collections.
The program provides a set of tools & GUI that allow users to view and edit the metadata of comic book files in various formats such as CBZ, CBR, CB7, and PDF.
It can automatically identify and tag comic books with metadata such as the title, author, publisher, and issue number by scanning Comic Vine’s online database. It also allows users to edit and add their own metadata, such as custom tags, summaries, and notes.
In addition to managing metadata, ComicTagger also has tools for organizing and renaming files, creating custom cover images, and exporting lists of comics. It also offers a batch processing feature (via Auto-Tag) that allows users to apply changes to multiple files at once.
This is especially helpful for removing unnecessary information from files names to ensure that you get the best match when looking for metadata.
On the subject of metadata – while not strictly necessary, it’s recommended by the developers to get a personal Comic Vine API key and use that when tagging with ComicTagger.
This is because Comic Vine implements a per-key limit on API access rates. Since the default application key is shared, it may already be exhausted by other users.
To obtain a Comic Vine API key, you will need to follow these steps:
In the API section, click on the “Get An API Key” button.
You will be asked to provide some information about the intended use of the API key, such as the name of your application and its website or description. Fill in the required information and click the “Submit” button.
Once approved, copy & paste your API key into ComicTagger via File > Settings > Comic Vine > Comic Vine API Key
It’s important to note that Comic Vine limits the number of requests that can be made using the API key. Make sure to read their terms of service and use the API responsibly.
You can read more about ComicTagger and its features here!
A Device Collection is a grouping of devices that share common characteristics or properties, such as hardware or software inventory, operating system, location, and organizational unit. Device collections are used to organize and manage devices in SCCM, and are a key element in deploying software updates, applications, and other software to groups of devices
How to create a Device Collection?
Launch the SCCM Management Console and navigate to the Assets and Compliance workspace.
Expand the Overview node, then expand the Device Collections.
Right click anywhere in the whitespace and click Create New Device Collection
Docker Compose is a tool for defining and running multi-container Docker applications. It allows developers to define the services that make up their application and how they interact with each other, all in a single file. In this article, we’ll cover everything you need to know to get started with creating a Docker Compose file, including examples of how to define services and configure networking.
Some Prerequisites:
Before we dive into creating a Docker Compose file, let’s make sure you have the necessary prerequisites:
A Docker Compose file is a YAML file that defines the services, networks, and volumes for your Docker application.
The beginning of a Compose file always starts with the version key. This key is used to specify the version of the Docker Compose syntax being used in the file. This is important because Docker Compose has gone through several major revisions, and each revision introduces new features or changes to the syntax.
Currently, the latest version of the Docker Compose syntax is version 3.9. When you specify the version tag as “3.9”, Docker Compose will use the latest syntax and recognize all of the latest features and syntax changes.
After defining the version of the Compose file it’s time to define the services that will be run in the containers.
