s3lph

I migrated an instance I'm maintaining from LDAP to OIDC just last week. Basically it boiled down to: - Disable unique user ids in the OIDC provider config - Make...

I think making both the top-level location field and lat/lon optional would cover the most use cases while not introducing an empty `"location": {}`, so I'd agree with https://github.com/SpaceApi/schema/issues/112#issuecomment-2121234970 the...

I'm experiencing the same issue as @lonix1: Some kind of autogenerated name is used, even if a name is set in the woodpecker.yml file. However, I'm observing this behavior with...

Hi @Pixtxa Thanks for your ideas. However, I don't think the SpaceAPI is quite the correct place for this. The Unvereinbarkeitserklärung is a unique CCC thing, so I don't think...

I'm not opposed to implementing this. I also don't think there's many changes needed in the schema - mainly renaming the sensor from `beverage_supply` to `products` and adding additional units....

Are you sure you meant no. 20? That one contains every unit from A·m² (Ampere-squaremeter) to parsec.

It's not an IPv4 vs IPv6 issue. Even from within the validator container I can query both successfully. However, what seems to be happening is that the nginx server hosting...

Hi @mweinelt Thanks for the suggestion, I think it would make a good addition to the schema. I would propose we implement this similar to e.g. the `wind` or `network_traffic`...

I just realized that our space actually has a PM sensor, so I went ahead and implemented my proposal above in our SpaceAPI endpoint: ```shell-session $ curl -s https://spaceapi.kabelsalat.ch |...