giuseppe99barchetta
commented
3 days ago Thank you for your valuable suggestions! I have recently made significant updates to the project. A web interface has been implemented to enhance the management of the automation process. Users can now specify a custom cron schedule either through environment variables or directly via the front-end interface, providing greater flexibility in how the script operates.
Additionally, I've added a "Force Run" button on the web page, allowing users to manually initiate the process after setting the environment variables. This feature offers more control over the automation workflow.
Looking ahead, I also plan to implement a welcome message in the terminal output. This will provide users with clear feedback on the script's execution status, helping to clarify any potential confusion regarding its operation.
I appreciate your input and am committed to making the project as user-friendly as possible. If you have any more ideas or questions, feel free to reach out!
Ability to use a environment variable to determine the cronjob in which the script runs. It's very hard to indicate if the script is working without looking at the repository and the Dockerfile to figure out it's cron based.
It may also be worth making it an option to be able to have the script run initially on container start and give people the ability to enable/disable this via an environment variable, as some might like to use docker scripts externally to restart at very bespoke cron timings.
I also suggest making some type of initialisation message too, as people adding this from the unraid store will not have much context as to why things aren't working and believe the app is broken as there is no ouput.