BlueFox/SolarControl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: BlueFox:c332701357df71f1a9bcd0bfd4957eb45a42f0c9
Branches Tags
BlueFox:main
BlueFox:v1.1
BlueFox:v1.0
BlueFox:v0.3
BlueFox:v0.2
BlueFox:v0.1
..
compare: BlueFox:cb03e309286a9e6f49abe2a63b4e4b64cbc190db
Branches Tags
BlueFox:main
BlueFox:v1.1
BlueFox:v1.0
BlueFox:v0.3
BlueFox:v0.2
BlueFox:v0.1

No commits in common. "c332701357df71f1a9bcd0bfd4957eb45a42f0c9" and "cb03e309286a9e6f49abe2a63b4e4b64cbc190db" have entirely different histories.
c332701357 ... cb03e30928

2 changed files with 0 additions and 27 deletions
Show Stats Expand all files Collapse all files

7
Dockerfile
View File

@ -1,7 +0,0 @@
FROM python:3.13-slim
RUN useradd --create-home --shell /bin/bash solarcontrol
WORKDIR /script
COPY solarcontrol.py ./
RUN pip install --upgrade pip && pip3 install --no-cache-dir paho-mqtt python-dotenv requests
USER solarcontrol
ENTRYPOINT ["/usr/bin/python3", "solarcontrol.py"]

20
README.md
View File

@ -5,14 +5,6 @@ Enforce a zero export (or whatever consumption you like) policy with an OpenDTU-
## Configuring and usage ## Configuring and usage
### Docker
Todo
### Bare-bone
The script can be configured using the .env file where you can adjust it (hopefully perfect) to your needs. After that, just run the script: The script can be configured using the .env file where you can adjust it (hopefully perfect) to your needs. After that, just run the script:
```bash ```bash
@ -22,18 +14,6 @@ python3 lge320reader.py
Please note: the .env file needs to be in the same folder or any other folder higher up in the directory structure as the script (more specifically, the WORKDIR). It is just a help, actually, the script searches for specific variables in its environment variables. It only loads the .env file so that you do not need to `export` all the files before running (see https://pypi.org/project/python-dotenv/ for more details). This also means that when using it in docker, you can set the docker containers environment file to that .env file and it will be accepted too. Please note: the .env file needs to be in the same folder or any other folder higher up in the directory structure as the script (more specifically, the WORKDIR). It is just a help, actually, the script searches for specific variables in its environment variables. It only loads the .env file so that you do not need to `export` all the files before running (see https://pypi.org/project/python-dotenv/ for more details). This also means that when using it in docker, you can set the docker containers environment file to that .env file and it will be accepted too.
## Building docker
To build the image for docker, simply use the following commands:
```bash
docker login # login to docker hub
docker buildx create --name buildx-multi-arch
docker buildx use buildx-multi-arch
docker buildx build --no-cache --platform linux/amd64,linux/386,linux/arm/v5,linux/arm/v7,linux/arm64/v8,linux/ppc64le,linux/s390x -t bluefox42/solarcontrol:<TAGNAME> . --push
```
## License ## License
This project is licensed under the terms of the GNU General Public License v3.0 or later, see [COPYING](COPYING). This project is licensed under the terms of the GNU General Public License v3.0 or later, see [COPYING](COPYING).