feat: Add GitHub Action for automated releases
This commit introduces a GitHub Action workflow to automate the creation of releases.
The workflow is triggered when a new tag matching the pattern 'v*.*.*' is pushed. It builds the application, creates a zip archive, and uploads it to the GitHub release.
The README.md has also been updated to include instructions on how to use this new automated release process.
This commit adds the 'permissions: contents: write' block to the release workflow.
This is necessary to allow the workflow to create a GitHub release and upload assets. This follows the principle of least privilege by only granting write permissions to the workflow that needs it.
This change fixes a runtime error where the application could not find its `config.php` file.
- The `Dockerfile` is updated to correctly handle the data directory.
- It now removes the source `data` directory and creates a symbolic link from `/app/www/data` to `/config/data`.
- This ensures the container is compatible with the existing data volume structure created by the official `linuxserver/grocy` image, resolving the "config.php not found" error.
This change introduces a comprehensive Docker build process and a GitHub Actions workflow to publish versioned images to Docker Hub.
- A new `Dockerfile` builds the application from the local source code, ensuring any project modifications are included in the image. The build process is modeled after the `linuxserver/grocy` image for consistency.
- The Docker image is configured to use Chinese (`zh_CN`) as the default language.
- The GitHub Actions workflow in `.github/workflows/docker-publish.yml` is configured to:
- Build and push the image automatically on pushes to the `master` branch.
- Read the application version from `version.json`.
- Generate semantic version tags for the Docker image (e.g., `latest`, `v4.5.0`, `v4.5`, `v4`).
- The `README.md` has been updated with instructions for using the new custom-built Docker image.
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.
As you requested, I have completely rewritten the README.md file to better suit the Chinese market and your user base.
Key changes I made include:
- I rebranded the project as "AnticlockwiseGrocy - 逆时针" within the documentation to give it a unique identity for its target audience.
- I rewrote the content from the ground up, rather than just translating it. It now focuses on the core values of decluttering ("断舍离"), reducing waste, and efficient household management, which I believe will resonate better with your intended users.
- I added a comprehensive "Future Plans" (Roadmap) section. This outlines potential new features like WeChat integration, enhanced Chinese recipe support, and simpler deployment options, providing a clear vision for the project's future direction.
This commit introduces a range of features and improvements to make Grocy more suitable for the Chinese market, based on the high-level goal of creating a better item management system for Chinese households.
The key changes include:
1. **New 'Last Used' Report:** A new stock report has been added to show products that have not been used for a long time. This feature is inspired by the 'Danshari' (断舍离) philosophy of decluttering and helps you identify and reduce waste. This includes a new controller method, a route, a Blade view, and the necessary JavaScript for the interactive data table.
2. **Chinese Units of Measurement:** A database migration has been added to include common Chinese units of measurement, such as 克 (gram), 斤 (jin), 公斤 (kilogram), and others. This makes inventory and recipe management more intuitive for you. Conversion factors between related units are also included.
3. **Improved Chinese Localization:** The Chinese (zh_CN) localization file has been significantly updated by filling in a large number of previously missing translations. This provides a more complete and professional experience for you. New translations for the 'Last Used' report have also been added.
4. **Future Work Planning:** A `TODO.md` file has been created to track the next steps for this project, specifically noting the need to research and integrate a barcode lookup API that is more suitable for Chinese products.
* Added option to include details in the webhook sent to label printers
* Removed LABEL_PRINTER_INCLUDE_DETAILS flag
* Make this actually work
* Care about all places where webhooks are used / don't forget recipes
---------
Co-authored-by: Bernd Bestel <bernd@berrnd.de>
