V3 beta #260
Merged
V3 beta #260
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently translated at 100.0% (268 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/de/
Currently translated at 100.0% (268 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/es/
Currently translated at 91.7% (246 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/zh_Hant/
Currently translated at 45.5% (122 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/vi/
Currently translated at 91.4% (245 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/vi/
Translations
Currently translated at 90.6% (243 of 268 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/vi/
…lumns in the database. - Added columns "duration", "plex_allow_sync", "specific_libraries" to the "invitations" table with their respective default values. - Added columns "expires" and "created" to the "users" table with their respective default values. - Fixed column "code" from 'None' to null in the "users" table. - Added migration scripts for upgrading people from all versions before 2.2.1. Run migration scripts to update the database accordingly. - Added migration script to update rows in the "invitations" table that have the "expires" column with value "None" to actual null. - Added migration script to drop all values in the "settings" table that are not null. Run migration scripts to update the database accordingly. - Added migration script to migrate old V2 settings to new V3 settings, creating a new account using the old credentials. - Added migration script to remove the "admin_key" from the "settings" table. - Added migration script to create new requests using old request data. - Added migration script to rename the "api_key" column to "server_api_key" in the "settings" table. - Added migration script to create a new "discord" entry in the "discord" table using old "discord_id" value. Run migration scripts to update the database accordingly. - Added migration script to move libraries from the "settings" table to the "libraries" table. - Added migration script to scan libraries from the server and add them to the database. Run migration scripts to update the database accordingly.
In this commit, the code changes add functionality for running migrations in the application. The `run_migrations` function handles the migration process by checking the current version in the database and the current version from the version file. It then runs the newer migrations that are not yet in the database, updating the database version accordingly. A new `migrator` package is also added, containing the `run_migrations` function that orchestrates the migration process.
- Implement a script that creates a migration file based on a template. - The script reads the current version from a file and generates the filename using the current date and time. - The template file is filled with the current date, filename, and version. - The modified content is written to the new file. - Finally, the script prints the filename of the created migration file. This commit introduces the `create.py` script and the `template.py` file that is used as a placeholder for the generated migrations.
- A new file `migrations.py` was added in the `backend/app/models/database` directory. - The file contains a new model class called `Migrations`. - The `Migrations` model has fields for `id`, `name`, and `created`. - The `Migrations` model inherits from the `BaseModel` class. - The `created` field has a default constraint set to the current datetime. Note: The commit message may be adjusted slightly to fit within 50 characters.
…in jellyfin.py and plex.py In jellyfin.py, the unused import of `get_libraries_ids` has been removed. In plex.py, the unused import of `get_libraries_name` has been removed. Additionally, the logic for retrieving libraries has been simplified in both files by directly setting sections as an empty list.
…d tag - Refactored the translation in the header section of the home page to use a localization function - Updated the Docker image name to "wizarrrr/wizarr" and the tag to "v3-beta" - Removed unnecessary platforms from the Docker build command
Update README.md
This commit adds a new workflow called "beta-test.yml" for Docker build and push by digest. The workflow is triggered on push to the "v3-beta" branch and can also be manually triggered. The workflow includes steps to clear digests, build the image for multiple platforms, get metadata from the Docker image, set up QEMU and Docker Buildx, login to GHCR, build and push the image, export the digest, and upload the digest as an artifact. There is also a merge step that downloads the digests, sets up Docker Buildx, gets metadata from the Docker image, logs in to GHCR, creates a manifest list, and inspects the image.
The commit updates `.github/workflows/beta-test.yml` to use the `v3-beta-test` image tag instead of `v3-beta`. This ensures that the correct image tag is used throughout the workflow.
…t workflow The previous code had an issue where the push by digest functionality was not working as expected. This commit fixes the issue by updating the outputs section in the workflow file. Additionally, the image name formatting has been updated to include the sha256 digest in the image name. This ensures that the correct image is pulled when necessary.
The buildx imagetools create command in the beta-test.yml file is updated to include the --tag option for creating the manifest list and pushing the image to the specified registry. This fix ensures the correct tagging of the image using the specified environment variables.
…t list creation and pushing. - Remove unsupported platforms for beta testing. - Login to Docker Hub as a part of the workflow. - Update the script for creating and pushing the manifest list to GHCR and Docker Hub. - Add labels for authors and description in Dockerfile. Note: The labels have been added for Open Containers Initiative (OCI) compliance.
…st and push to both GHCR and Docker Hub registries. - Change `REGISTRY` variable to `GHCR_REGISTRY` and add `DH_REGISTRY` variable. - Update references to `REGISTRY` in workflow steps with `GHCR_REGISTRY`. - Build the image to the local registry instead of pushing immediately. - Create tags for both GHCR and Docker Hub registries. - Push the image to both GHCR and Docker Hub registries using the image digest. - Export the digest for later use. - Create and push a manifest list to both GHCR and Docker Hub registries. - Inspect the images in both GHCR and Docker Hub registries.
…est. This change updates the beta-test.yml workflow to include image tagging and pushing by digest. It adds a step to retag the images with the digest, and another step to push the images using the digest. Additionally, it exports the digest for later use.
Add the step to retag the images with the digest so that we can push them using the digest as reference.
…gest. Export the digest for later use.
- Instead of pushing individual images, refactor the code to push images by digest using the `outputs` field. - Remove the unnecessary steps for retagging and pushing images. - Update the creation of the manifest list and push it for both GHCR and DockerHub. - Inspect the image as part of the workflow. Co-authored-by: [Author Name] <[email protected]>
…e tag - Updated the image tag from "v3-beta-test" to "v3-beta" in `.github/workflows/beta-test.yml` file. - Removed the login to Docker Hub step from the workflow. - Added new steps to checkout the repository and get the release version from the latest file. - Modified the step for creating the manifest list and pushing the image to include the release version in the image tag.
Update workflow to install necessary dependencies for frontend and execute translation compilation before committing and pushing changes using a GitHub Action.
Currently translated at 100.0% (279 of 279 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/es/
Currently translated at 100.0% (279 of 279 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/fr/
Currently translated at 100.0% (279 of 279 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/de/
Currently translated at 100.0% (279 of 279 strings) Translation: Wizarr V3/Wizarr Translate-URL: https://hosted.weblate.org/projects/wizarr-v3/wizarr/fr/
This commit adds the Membership interface, which includes properties for `created`, `id`, `token`, `email`, and `user_id`. This interface has been generated using a code generation tool.
- Adds the membership API to the list of routes in the __init__.py file in the backend/api/routes directory.
This commit adds a new file "membership_api.py" under the "api/routes" directory. The file contains API routes and operations related to membership. It defines a Flask namespace called "Membership" with a path "/membership". Within this namespace, there are three route methods: GET, POST, and DELETE. The GET route retrieves the membership status for the current user. It queries the database and returns the membership details if found, otherwise returns a 404 error. The POST route sets the membership status for the current user. It checks if the membership status exists and updates it if found, otherwise creates a new membership status. It saves the changes to the database and returns the updated membership details. The DELETE route deletes the membership status for the current user. It checks if the membership status exists and deletes it if found, otherwise returns a 404 error. These changes enable the application to handle membership-related operations through the API.
This commit adds a new column called 'tutorial' to the users table in the database. The column is a boolean field and has a default value of False. Additionally, a migration script is included to perform the necessary database alteration. The migration is completed successfully and a confirmation message is printed.
The commit adds a new Licenses model to the backend application. This model includes fields for id, membership_id, key, and created. The Licenses model inherits from the BaseModel.
This commit adds a new file `memberships.py` which contains the database model definition for memberships. The model includes fields for `id`, `user_id`, `token`, `email`, and `created`.
- Create a new method `handleMembershipUpdate` in the `Auth` class to handle membership updates. - Retrieve the membership from the server using an API call to "/api/membership". - If the response is successful, set the membership in the user store. - If the response is not successful, return null. - Updated the `Auth` class to await the router push in the `logout` method to ensure redirection to the login page is complete. - Updated the documentation with comments to explain the purpose of the `handleMembershipUpdate` method and its implementation.
The DefaultValues.ts file has been modified to include the membership_api and livechat_api URLs. These new values will be used to connect to the respective APIs in the Wizarr application.
- Adds a new file `Register.vue` for the registration form component in the Membership module. - Sets up the form template with input fields for first name, last name, email, password, and invitation code. - Implements form validation for each input field. - Defines the `register` method to handle the form submission and make a request to the membership registration API. - Sets up event listeners for form submission and initializes the `membership_api` variable. - Displays success or error toast messages based on the registration response.
This commit adds a new file "Membership.vue" to the settings module. The component defines the layout and functionality for the Membership page. The page allows users to login, register, and logout of their membership. The component includes form inputs for email and password, as well as buttons for login and registration. The component also displays information about the user's current membership status and provides a message about ongoing development.
This commit adds live support functionality to the Support page. Users can now initiate a support session by clicking the "Start Support Session" button. The support session is facilitated by a Wizarr assistant who will guide users through any issues or questions they may have. Paying members can access this feature. If a user is not a paying member, they will be redirected to the membership page. The support session can be ended by closing the widget or submitting the offline form.
The commit adds a new route for the Membership page in the settings router file. The page allows users to view Wizarr Cloud membership information.
- The import statement in axios.ts has been fixed to import the necessary types and interfaces correctly. - Added a new function `useRawAxios` in axios.ts that creates a rawAxios instance. - Added `$rawAxios` property to `PiniaCustomProperties` and `ComponentCustomProperties` interfaces. - Initialized and assigned `rawAxios` instance to `$rawAxios` property in piniaPluginAxios and vuePluginAxios. - Updated the beforeSend function in sentry.ts to handle event exceptions correctly by displaying the error message.
This commit introduces the `Membership` type to the user store and adds getter and setter methods. The `setMembership` method allows setting the membership value, and the `updateMembership` method allows updating specific fields of the membership object. fix: Update RocketChat server URL This commit updates the RocketChat server URL in the config object of the RocketChat utility class. The new URL is "https://chat.wizarr.dev/livechat".
Translations update from Hosted Weblate
Update docker-compose.yml
Update docker-compose.yml
Translations
- Modify the migration script to add a new column called "tutorial" to the "users" table in the database. The column is of type BOOLEAN and has a default value of False. This change ensures that the tutorial information is properly stored for each user. - Remove the unnecessary check for existing tutorial column in the "accounts" table, as the new column will always be added regardless.
- The `ci.yml` workflow file has been deleted. - A new workflow file `release.yml` has been created for building and pushing releases. - The new workflow file `release.yml` includes various steps for building, pushing, and merging docker images. - The `test` job has been removed in the `build` workflow. - The `git-auto-commit-action` is used to automatically commit and push changes to the `latest` file in the `update_latest` job. - The `prerelease` job checks if the release is not a pre-release and skips the job if it is. - The `main_branch` job checks if the release is on the main branch and skips the job if it is not. - The `build_ghcr` job builds and pushes the image to GHCR by digest. - The `merge_ghcr` job merges the digest for GHCR by creating a manifest list and pushing it to the registry. - The workflow includes various login actions and setup actions for Docker.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.