{ | |
config, | |
pkgs, | |
options, | |
... | |
}: let | |
hostname = "oatman-pc"; # to alllow per-machine config | |
in { | |
networking.hostName = hostname; |
version: "3.9" | |
volumes: | |
postgres: | |
services: | |
postgres: | |
image: postgres | |
restart: unless-stopped | |
healthcheck: |
# WARNING: This is not how you should use a CI/CD plaftform, use privately and at your own risk | |
name: URL uploader | |
on: | |
workflow_dispatch: | |
inputs: | |
LINK: | |
type: string | |
required: true | |
FILENAME: | |
type: string |
So you want to make a new rpm-ostree desktop variant in Fedora to join Silverblue, Kinoite and Sericea? Here are the steps that you should follow.
First, you should figure out what packages should be installed in your image. To do that, you can start from the base container image (https://quay.io/repository/fedora-ostree-desktops/base) and add packages from the comps group corresponding to your desktop in Fedora : https://pagure.io/fedora-comps
At this point, you should consider which apps are going to be shipped by default, included in the image, and which ones are going to be installed by default as Flatpaks.
Once you've got something working, reproduce that in https://pagure.io/workstation-ostree-config using the comps group and the filter and sync script. Look at other variants for example.
As reported by Fedora CoreOS team, on the AArch64 / ARM64 architecture the new 6.2 kernels will not boot due to older bootloaders in Fedora IoT.
There is now some guidance from the Fedora IoT team on this here. This is probably the better course of action to take than my method below.
https://github.com/recloudstream/cloudstream/
- Free netflix alternative.
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.
There are multiple methods for transmitting authorization values, however, some are outdated and scheduled to be removed.
It's recommend to use the Authorization
header. If header auth isn't an option, the token may be sent through the ApiKey
query parameter. Sending secure data in a query parameter is unsafe as the changes of it leaking (via logs, copy-paste actions or by other means) are high. Only use this method as a last resort.