Dreaded_X
9d4c059d29
chore(deps): Update workflow
Build and deploy / Build container and manifests (push) Failing after 10m45s
Build and deploy / build (push) Failing after 10m46s
Build and deploy / Deploy container (push) Skipped
2026-08-26 03:05:56 +02:00
Dreaded_X
ce302b148e
feat: Sync printer light with room light
Build and deploy / build (push) Successful in 18m22s
Build and deploy / Deploy container (push) Successful in 39s
2026-06-20 05:22:59 +02:00
Dreaded_X
9979ab3446
fix: Deploy requires login now
Build and deploy / build (push) Successful in 15m9s
Build and deploy / Deploy container (push) Successful in 1m20s
2026-05-12 05:52:39 +02:00
Dreaded_X
2158bde1c2
chore: Upgraded to new workflow
2025-11-20 04:44:25 +01:00
Dreaded_X
8bb17e1440
feat(config)!: Reworked how configuration is loaded
...
The environment variable `AUTOMATION_CONFIG` has been renamed to
`AUTOMATION__ENTRYPOINT` and can now also be set in `automation.toml` by
specifying:
```
automation = "<path>"
```
Directly accessing the environment variables in lua in no longer
possible. To pass in configuration or secrets you can now instead make
use of the `variables` and `secrets` modules.
To set values in these modules you can either specify them in
`automation.toml`:
```
[variables]
<name> = <value>
[secrets]
<name> = <value>
```
Note that these values will get converted to a string.
You can also specify the environment variables
`AUTOMATION__VARIABLES__<name>` and `AUTOMATION__SECRETS__<name>` to
set variables and secrets respectively. By adding the suffix `__FILE` to
the environment variable name the contents of a file can be loaded into
the variable or secret.
Note that variables and secrets are identical in functionality and the
name difference exists purely to make it clear that secret values are
meant to be kept secret.
2025-09-05 04:48:00 +02:00
Dreaded_X
01e88eeb3b
Use new and improved rust workflow and Dockerfile
2025-08-31 00:38:58 +02:00
Dreaded_X
8f858e9b42
Removed cargo config that is no longer necessary
2025-08-22 23:27:01 +02:00
Dreaded_X
88e31699ad
Removed pre-commit action
...
Build and deploy / Build application (push) Successful in 3m36s
Build and deploy / Build container (push) Successful in 40s
Build and deploy / Deploy container (push) Successful in 32s
I should always run pre-commit locally and currently this just takes to
long to run.
2024-07-30 00:08:10 +02:00
Dreaded_X
fb7af4a8b1
Added caching to pre-commit checks
Build and deploy / Build application (push) Successful in 3m46s
Check / Run checks (push) Successful in 3m53s
Build and deploy / Build container (push) Successful in 46s
Build and deploy / Deploy container (push) Successful in 34s
2024-07-08 23:34:50 +02:00
Dreaded_X
5bf6e6bc3c
Fixed build after gitea update
2024-07-08 23:25:20 +02:00
Dreaded_X
526c82096c
Improved workflow
Build and deploy / Build application (push) Successful in 4m23s
Build and deploy / Build container (push) Successful in 1m0s
Check / Run checks (push) Successful in 3m27s
Build and deploy / Deploy container (push) Successful in 36s
2024-06-15 04:31:27 +02:00
Dreaded_X
113f9f926c
Switched from custom pre-commit script to using the pre-commit tool
Build and deploy automation_rs / Run pre-commit checks (push) Successful in 4m1s
Build and deploy automation_rs / Build automation_rs (push) Successful in 4m31s
Build and deploy automation_rs / Build Docker image (push) Successful in 50s
Build and deploy automation_rs / Deploy Docker container (push) Successful in 32s
2024-05-10 01:28:50 +02:00
Dreaded_X
6e4a63e9d7
Improvement: Job names could be better
Build and deploy automation_rs / Build automation_rs (push) Successful in 4m27s
Build and deploy automation_rs / Build Docker image (push) Successful in 47s
Build and deploy automation_rs / Deploy Docker container (push) Successful in 21s
2023-11-24 00:09:45 +01:00
Dreaded_X
b4427f2140
Fix: Wake On LAN is not working
...
The docker container needs to be created with the network option set to
one of the networks otherwise it will not work.
2023-11-23 23:04:26 +01:00
Dreaded_X
234e891418
Fix: main is used instead of master, only builds for feature/action
...
Build and deploy automation_rs / Build (push) Successful in 4m38s
Build and deploy automation_rs / Create container (push) Successful in 43s
Build and deploy automation_rs / Deploy Docker container (push) Successful in 36s
Accidentally used main instead of master in the workflow.
Also hardcoded feature/action as the only feature branch that triggers a
build, instead any feature branch will now trigger a build.
2023-11-23 00:47:19 +01:00
Dreaded_X
39f9b997ed
Fix: Only master branch should push the docker image
Build and deploy automation_rs / Build (push) Successful in 4m57s
Build and deploy automation_rs / Create container (push) Successful in 57s
Build and deploy automation_rs / Deploy Docker container (push) Has been skipped
2023-11-23 00:26:24 +01:00
Dreaded_X
cdb02eb5dd
Feature: Deploy Docker container after it is created
Build and deploy automation_rs / Build (push) Successful in 4m47s
Build and deploy automation_rs / Create container (push) Successful in 1m2s
Build and deploy automation_rs / Deploy Docker container (push) Has been skipped
2023-11-22 01:17:30 +01:00
Dreaded_X
c77064b5b9
Feature: Use Gitea Actions to build automation_rs
...
Build and deploy automation_rs / Build (push) Successful in 6m39s
Build and deploy automation_rs / Create Docker container (push) Successful in 1m1s
Builds automation_rs and the corresponding docker image.
The binary is uploaded as an artifact and the image is uploaded to the
registry.
In order to improve caching the nightly version is locked using
rust-toolchain.toml
2023-11-22 00:40:05 +01:00