You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
🤓
1s and 0s aren't going to put themselves in the right order.
Michael
mredig
🤓
1s and 0s aren't going to put themselves in the right order.
This guide will help you create new releases on GitHub for your Swift Packages that host binary executable assets. This is a multistep process that consists of:
Staging a draft release on Github
Uploading your binary artifacts to the draft release
Updating the Package.swift to point to the uploaded assets in a staging branch
To start using the Jellyfin API, authorization is probably the first thing you'll need to do. Jellyfin's authorization options can be a bit confusing because there are a lot of deprecated options.
Generally there are three ways to authenticate: no authorization, user authorization with an access token or authorization with an API key. The first way is easy, just do nothing. But most often you'll need to use either the access token or API key.
Sending authorization values
There are two methods to send authorization values to the server. The preferred method is by using the Authorization header with the custom MediaBrowser scheme. When a header value is not possible (e.g. URLs send to external applications or due to other constraints) the ApiKey query parameter can be used. The query parameter just takes an access token or API key. We strongly recommend to always use the Authorization hea
SMJobBlessUtil.py for Python3 / Xcode 13.3 / macOS Monterey 12.3 (with workaround for otool arm64 weirdness)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters