truecharts / charts Goto Github PK

HomeAssistant using docker should be quite viable and would provide a much more stable platfom than the current TrueNAS Core plugin.

As discussed here:
https://github.com/jailmanager/jailman/issues/18#issuecomment-748687627

Describe the bug
After installing the traefik chart, clicking on the button portal brings me to (server-ip):443 which gives me a 404 error code.

To Reproduce
It happens every time I create the traefik chart.
The options I chose when creating the chart are:

• web ingress enabled
• wildcard certificate
• host I set to my full domain (example.com)
• wildcard domain I set to my full domain
• certmanager cloudflare

Expected behavior
I would expect the portal button brings me to the traefik web dashboard.

Screenshots

Add a zwavejs2mqtt app as requested by @tprelog

I'd love to see this app, makes beginners to easy create certificates and reverse proxy their selfhosted apps!
Here is the link of the project
https://github.com/jc21/nginx-proxy-manager
https://nginxproxymanager.com/

This issue provides visibility into Renovate updates and their statuses. Learn more

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update docker general non-major (ghcr.io/truecharts/mongodb, kopia/kopia, tccr.io/truecharts/baserow, tccr.io/truecharts/clamav, tccr.io/truecharts/cyberchef, tccr.io/truecharts/deconz, tccr.io/truecharts/docker-in-docker, tccr.io/truecharts/ghost, tccr.io/truecharts/inventree, tccr.io/truecharts/minecraft-java11, tccr.io/truecharts/minecraft-java8-openj9, tccr.io/truecharts/n8n, tccr.io/truecharts/nginx, tccr.io/truecharts/odoo, tccr.io/truecharts/paperless-ng, tccr.io/truecharts/picoshare, tccr.io/truecharts/prowlarr, tccr.io/truecharts/wikijs)
• chore(deps): update helm chart common to v9.3.7
• chore(deps): update helm chart common to v9.3.7

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update container image tccr.io/truecharts/nextcloud to v24.0.0

• Check this box to trigger a request for Renovate to run again on this repository

See:
https://github.com/travisghansen/external-auth-server

As suggested by @travisghansen

Required for using ozwdaemon with Home Assistant

As suggested by @travisghansen

As suggested by @travisghansen

Currently most common-based charts do not support nodeport and only work using traefik.
This needs some work, because we at least want feature-parity with official charts

We have a lot "simple" containers, that just require some storage, a port and can't be run HA anyway.
These containers might be more maintainable if we move them to a "common library chart" like done by @k8s-at-home

Please and Thank You

yeah, more or less the same as Sonarr but is a fork of the old sickage/sickgear stuff, and anime a little better

https://pymedusa.com/

As suggested by @travisghansen

Add ESPHome app as requested by @tprelog

Yes, this is already in upstream.
But Upstream is missing a lot of features we (might) want:

• CustomDB urls
• Redis Support
• Seperating the different kinds of Nextcloud files (most importantly: data)
• Ingress support

We can trickle some of those back into upstream.
But we do want to include ingress support and it's easier to fork it than to try and find a middleground on upstream. Because upstream hasn't decided on a ingress format yet and ours is mostly done.

I would like to suggest https://www.firefly-iii.org
Install:
https://docs.firefly-iii.org/firefly-iii/installation/docker/
https://docs.firefly-iii.org/firefly-iii/installation/k8n/

The third-party helper apps consist only of single Docker containers, so the existing tool can be used.

This is required for using the OpenZWave (beta) integration in Home Assistant

https://github.com/OpenZWave/qt-openzwave

Currently the common chart only supports one webbased (https) ingress.
It would be nice if we could abstract this away and enable setting multiple tcp, udp or web ingress(routes) for traefik.

I similair structure as we currently use for storage for the common library, but for ingress instead.

Yes, this is already in upstream.
But we want to include ingress support and it's easier to fork it than to try and find a middleground on upstream. Because upstream hasn't decided on a ingress format yet and ours is mostly done.

To be clear:
Adding more entrypoints, is part of the implementation of the Apps requiring those Entrypoints.
Not the Traefik App.

Hence this can move forward to the next stage, even when some Apps still require custom Entrypoints

As suggested by @travisghansen