Compare commits

..

4 Commits

Author SHA1 Message Date
c3224fbd48 updated config socks5 2025-11-03 08:32:27 +00:00
271b80c980 restarting 2025-11-03 08:31:32 +00:00
b8e26e1963 restarting 2025-11-03 08:30:00 +00:00
3eb23a5daa Update README.md 2025-11-03 07:52:18 +00:00
3 changed files with 67 additions and 9 deletions

View File

@@ -1,2 +1,44 @@
# ha-addons
# ZTSW HA Add-Ons
Add-on documentation: <https://developers.home-assistant.io/docs/add-ons>
[![Open your Home Assistant instance and show the add add-on repository dialog with a specific repository URL pre-filled.](https://my.home-assistant.io/badges/supervisor_add_addon_repository.svg)](https://my.home-assistant.io/redirect/supervisor_add_addon_repository/?repository_url=https%3A%2F%2Fgit.ztsw.de%2Fpedan%2Fha-addons)
## Add-ons
This repository contains the following add-ons
### [HA-Socks5-Proxy](./ha-socks5-proxy)
![Supports aarch64 Architecture][aarch64-shield]
![Supports amd64 Architecture][amd64-shield]
![Supports armhf Architecture][armhf-shield]
![Supports armv7 Architecture][armv7-shield]
![Supports i386 Architecture][i386-shield]
_Example add-on to use as a blueprint for new add-ons._
<!--
Notes to developers after forking or using the github template feature:
- While developing comment out the 'image' key from 'example/config.yaml' to make the supervisor build the addon
- Remember to put this back when pushing up your changes.
- When you merge to the 'main' branch of your repository a new build will be triggered.
- Make sure you adjust the 'version' key in 'example/config.yaml' when you do that.
- Make sure you update 'example/CHANGELOG.md' when you do that.
- The first time this runs you might need to adjust the image configuration on github container registry to make it public
- You may also need to adjust the github Actions configuration (Settings > Actions > General > Workflow > Read & Write)
- Adjust the 'image' key in 'example/config.yaml' so it points to your username instead of 'home-assistant'.
- This is where the build images will be published to.
- Rename the example directory.
- The 'slug' key in 'example/config.yaml' should match the directory name.
- Adjust all keys/url's that points to 'home-assistant' to now point to your user/fork.
- Share your repository on the forums https://community.home-assistant.io/c/projects/9
- Do awesome stuff!
-->
[aarch64-shield]: https://img.shields.io/badge/aarch64-yes-green.svg
[amd64-shield]: https://img.shields.io/badge/amd64-yes-green.svg
[armhf-shield]: https://img.shields.io/badge/armhf-yes-green.svg
[armv7-shield]: https://img.shields.io/badge/armv7-yes-green.svg
[i386-shield]: https://img.shields.io/badge/i386-yes-green.svg

View File

@@ -0,0 +1,4 @@
build_from:
aarch64: ghcr.io/home-assistant/aarch64-base:latest
amd64: ghcr.io/home-assistant/amd64-base:latest
armv7: ghcr.io/home-assistant/armv7-base:latest

View File

@@ -1,20 +1,32 @@
name: "SOCKS5 Proxy"
version: "1.0.0"
version: "1.0.1"
slug: "socks5_proxy"
description: "SOCKS5 Proxy Server für Firefox und andere Anwendungen"
description: "SOCKS5 Proxy Server für Firefox"
arch:
- armhf
- armv7
- aarch64
- amd64
- i386
- armv7
ports:
1080/tcp: 1080
environment:
PROXY_USER: ""
PROXY_PASSWORD: ""
PROXY_PORT: "1080"
options:
proxy_user: ""
proxy_password: ""
proxy_port: 1080
schema:
proxy_user: str?
proxy_password: password?
proxy_port: port
proxy_user: "str?"
proxy_password: "password?"
proxy_port: "port"
map:
- type: env
key: proxy_user
value: PROXY_USER
- type: env
key: proxy_password
value: PROXY_PASSWORD
- type: env
key: proxy_port
value: PROXY_PORT