This commit addresses two issues in the release workflow:
1. The tag trigger has been reverted to only accept tags matching the `v*.*.*` pattern, as requested by the user.
2. The `grep` command used to extract the version number from `version.json` has been made more robust to prevent errors during the workflow run.
This commit updates the GitHub Actions workflow for releases to be more flexible.
The workflow will now trigger on tags that follow either the 'v*.*.*' pattern or the '*.*.*' pattern. This allows the user to create releases using tags with or without a 'v' prefix (e.g., 'v1.2.3' or '1.2.3').
This change updates the GitHub Actions workflow to implement a versioned Docker tagging strategy, as requested.
- The workflow now reads the version from `version.json`.
- It generates semantic version tags (e.g., `v4.5.0`, `v4.5`, `v4`) for the Docker image, in addition to the `latest` tag.
- This makes the image tagging consistent with the practices of `linuxserver/grocy`.
This change introduces a comprehensive Dockerfile and a GitHub Actions workflow to build and publish a custom Docker image from the project's source code.
- A new `Dockerfile` has been added. It builds the application from the local source, installing all necessary dependencies, ensuring that any modifications to the codebase are included in the final image. This approach is consistent with the build process of `linuxserver/grocy`.
- The Docker image is configured to use Chinese (`zh_CN`) as the default language via the `GROCY_DEFAULT_LOCALE` environment variable.
- A GitHub Actions workflow is added to `.github/workflows/docker-publish.yml`. It automates the process of building and publishing the image to `nishizhen/anticlockwisegrocy` on Docker Hub whenever a push is made to the `master` branch.
- The `README.md` has been updated to reflect the new Docker image and provide correct instructions for its use.
