🎉 Release of add-on Cloudflared 1.0.5
This commit is contained in:
@@ -86,10 +86,10 @@ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|||||||
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
||||||
SOFTWARE.
|
SOFTWARE.
|
||||||
|
|
||||||
[addon-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/tree/v1.0.4
|
[addon-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/tree/v1.0.5
|
||||||
[addon-doc-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/blob/v1.0.4/README.md
|
[addon-doc-cloudflared]: https://github.com/brenner-tobias/addon-cloudflared/blob/v1.0.5/README.md
|
||||||
[cloudflared-issue]: https://github.com/brenner-tobias/addon-cloudflared/issues
|
[cloudflared-issue]: https://github.com/brenner-tobias/addon-cloudflared/issues
|
||||||
[cloudflared-version-shield]: https://img.shields.io/badge/version-v1.0.4-blue.svg
|
[cloudflared-version-shield]: https://img.shields.io/badge/version-v1.0.5-blue.svg
|
||||||
[cloudflared-aarch64-shield]: https://img.shields.io/badge/aarch64-yes-green.svg
|
[cloudflared-aarch64-shield]: https://img.shields.io/badge/aarch64-yes-green.svg
|
||||||
[cloudflared-amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg
|
[cloudflared-amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg
|
||||||
[cloudflared-armhf-shield]: https://img.shields.io/badge/armhf-yes-green.svg
|
[cloudflared-armhf-shield]: https://img.shields.io/badge/armhf-yes-green.svg
|
||||||
|
|||||||
@@ -1,2 +1,11 @@
|
|||||||
## What’s changed
|
## What’s changed
|
||||||
- ℹ️ Update Cloudflared to version 2022.4.1 @github-actions (#83)
|
- ℹ️ Update Cloudflared to version 2022.5.0 @github-actions (#88)
|
||||||
|
|
||||||
|
## 📚 Documentation
|
||||||
|
|
||||||
|
- Add translations to Add-on configuration page @elcajon (#87)
|
||||||
|
|
||||||
|
## ⬆️ Dependency updates
|
||||||
|
|
||||||
|
- Update yq from 4.14.1-r0 to 4.14.1-r1 @elcajon (#85)
|
||||||
|
- Bump docker/setup-buildx-action from 1.6.0 to 1.7.0 @dependabot (#84)
|
||||||
|
|||||||
@@ -40,4 +40,4 @@ schema:
|
|||||||
- str?
|
- str?
|
||||||
slug: cloudflared
|
slug: cloudflared
|
||||||
url: https://github.com/brenner-tobias/addon-cloudflared/
|
url: https://github.com/brenner-tobias/addon-cloudflared/
|
||||||
version: 1.0.4
|
version: 1.0.5
|
||||||
|
|||||||
@@ -0,0 +1,65 @@
|
|||||||
|
---
|
||||||
|
configuration:
|
||||||
|
log_level:
|
||||||
|
name: Log Level
|
||||||
|
description: >-
|
||||||
|
Defines the log level for add-on and the Cloudflare service.
|
||||||
|
external_hostname:
|
||||||
|
name: External Homeassistant Hostname
|
||||||
|
description: >-
|
||||||
|
Set this to your domain name or a subdomain that you want to use to
|
||||||
|
access Home Assistant.
|
||||||
|
tunnel_name:
|
||||||
|
name: Cloudflare Tunnel Name
|
||||||
|
description: >-
|
||||||
|
Defines the name of the tunnel created for the communication between
|
||||||
|
this service and the Cloudflare edge server. The default value should
|
||||||
|
be fine in most use cases.
|
||||||
|
additional_hosts:
|
||||||
|
name: Additional Hosts
|
||||||
|
description: >-
|
||||||
|
Define a list of additional hosts to be routed by the Cloudflare tunnel.
|
||||||
|
catch_all_service:
|
||||||
|
name: Catch-All Service
|
||||||
|
description: >-
|
||||||
|
Define a catch-all service which will be called for services not
|
||||||
|
configured directly.
|
||||||
|
nginx_proxy_manager:
|
||||||
|
name: Enable Catch-All Nginx-Proxy-Manager
|
||||||
|
description: >-
|
||||||
|
Sets the catch-all service to the "Nginx-Proxy-Manager Community Add-Ons"
|
||||||
|
Add-On.
|
||||||
|
quick_tunnel:
|
||||||
|
name: Enable Quick Tunnel
|
||||||
|
description: >-
|
||||||
|
Enables the Cloudflare Quick Tunnel for this instance. All other options
|
||||||
|
will be ignored.
|
||||||
|
reset_cloudflared_files:
|
||||||
|
name: Reset Cloudflared files
|
||||||
|
description: >-
|
||||||
|
When enabled, the add-on configuration will be resetted upon next add-on
|
||||||
|
start.
|
||||||
|
data_folder:
|
||||||
|
name: Custom Data Folder
|
||||||
|
description: >-
|
||||||
|
Set custom data folder to store Cloudflare configuration.
|
||||||
|
custom_config:
|
||||||
|
name: Enable Custom Configuration
|
||||||
|
description: >-
|
||||||
|
You can provide your own Cloudflare ingress configuration when this
|
||||||
|
option is enabled.
|
||||||
|
warp_enable:
|
||||||
|
name: Enable Cloudflare Warp
|
||||||
|
description: >-
|
||||||
|
This option enables Cloudflare Warp functionality. Warp allows you to
|
||||||
|
route your whole network through the Cloudflare tunnel.
|
||||||
|
warp_routes:
|
||||||
|
name: Define Cloudflare Warp routes
|
||||||
|
description: >-
|
||||||
|
Define networks to route through your Cloudflare tunnel if Warp function
|
||||||
|
is enabled.
|
||||||
|
warp_reset:
|
||||||
|
name: Reset Cloudflare Warp
|
||||||
|
description: >-
|
||||||
|
When enabled, the Cloudflare Warp related add-on configuration will
|
||||||
|
be resetted upon next add-on start.
|
||||||
Reference in New Issue
Block a user