V3 beta #255
Merged
V3 beta #255
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
Translations
…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] <author@example.com>
…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.
This commit updates the workflow to build and push the image by digest. It sets the 'push' parameter to true and the 'provenance' parameter to false. The output now includes the image name with push-by-digest and name-canonical properties.
The commit modified the .dockerignore file by removing the pattern for all hidden files. The commit also updated the beta-ci.yml workflow by adding a new job "clear" to clear the digests from the artifacts and added a new step "clear digests" for the job. The detailed commit message lists all the changes made in the commit.
Updated the names of the workflows to accurately reflect their purpose - the "name" field was changed for the "Docker Build and Push" and "Release Docker Image CI" workflows in the `beta-ci.yml` and `ci.yml` files respectively. The updated names now clearly indicate whether the workflow is for the beta or release builds.
This commit modifies the beta CI workflow to include support for multiple platforms, such as linux/386, linux/arm/v5, linux/arm/v7, and more. Additionally, it updates the docker-create script to build the image for these platforms and adds support for caching the build.
- Modify the step name to reflect the intended destination. - Update the tag for the Registry image and remove unnecessary steps. - Improve overall readability and remove duplicate code.
Translations
… script `docker-build.sh`.
…hcr jobs, add build_dh and merge_dh jobs for Docker Hub - Deletion of digests artifact renamed to digests_dh and digests_ghcr - Added build_ghcr job to build digest for GHCR - Added merge_ghcr job to merge digest for GHCR - Added build_dh job to build digest for Docker Hub - Added merge_dh job to merge digest for Docker Hub
added 26 commits
October 14, 2023 03:34
- Update Dockerfile to show build and target platform in Docker log - Added a new run command to echo the build and target platform
…orkflow - Removed duplicate and unnecessary platform configurations in the beta-ci workflow to streamline and simplify the job matrix.
The commit introduces changes to the Docker image build configuration by commenting out the setup of QEMU for both the beta and production workflows. Additionally, it adds cache configuration to improve build performance.
- The commit adds functionality to refresh the JWT token. - It checks if the `current_app` is set within a flask route. - It gets the identity of the user and the JTI of the JWT. - It finds the session in the database where either the access_jti or refresh_jti matches the JTI. - It exchanges the refresh token for a new access token. - It updates the access token in the database. - Finally, it returns the new access token.
- Fixes an issue where the specific libraries were not being properly extracted from the invitation. - Updates the user policy to enable all folders and set the maximum active sessions to 2. - If there are specific libraries specified in the invitation, the user policy will only enable those libraries.
The commit fixes a serialization issue in the MFA API by using the "loads" and "dumps" functions to properly convert the user object to JSON format.
This commit adds a new BooleanField called `tutorial` to the `Accounts` model in the database. The `tutorial` field has a default value of `False`.
This commit adds a 'tutorial' field to the Accounts model in wizarr/accounts.py. The 'tutorial' field is of type BooleanType with a default value of False.
…ject serialization
These changes modify the get_account_by_id, update_account, and delete_account functions to simplify the code and improve readability. The `get_account_by_id` function no longer raises a `ValueError` if the account does not exist; instead, it returns None. The `update_account` function now directly updates the existing account in the database, rather than creating a new account and updating it. The `delete_account` function now uses the `get_or_none` method to retrieve the account, rather than raising a `ValueError` if the account does not exist.
Instead of directly converting section IDs to names, the code now checks if specific libraries exist in the invitation. If they do, it converts section IDs to names. The invite_data variable is created to store the data for inviting the user, including the user's email, server, allow_sync, and sections (if they exist). The invite_method now takes the invite_data as arguments.
This commit adds error logging using socketio_emit function to log any exceptions encountered during the execution of the global_invite_user_to_media_server function. This will help track and monitor any issues that occur during account creation and invitation processes.
This change fixes the display of a welcome message in the authentication module. Instead of using the `||` operator, it now uses the nullish coalescing operator (`??`) to properly handle cases where `user.display_name` is null or undefined.
The 'Back' and 'Next' buttons were incorrectly disabled when the current view was at its respective boundaries. This commit fixes the issue by using a conditional rendering with `v-if` to show/hide the buttons based on the current view index.
… login. Show warning modal and redirect to help page.
This commit adds a confirmation prompt for the user before logging into Plex. If the user doesn't confirm, the login process is aborted. If the user confirms, the authentication token is obtained and emitted to the parent component.
- Add GitHub attribution to the Join view - Handle socket log message by logging it to console
Add the user store to the custom tour guide options in order to access user-specific data during the tour.
Imported the APIUser type as User and updated the UserStoreState and actions to use the User type. Removed the unused import of APIUser. The `setUser` and `updateUser` actions now accept the User type.
- Add user store to the loadRouterTour function in order to check if the user has completed the tutorial before loading the tour on route change. - Use the user store to access the user's tutorial completion status and update it via an API call when the tour is exited. - Update the onAfterExitCallback function to handle the user update and API call. - Remove unnecessary console logs.
- Updated the APIUser interface by adding a new property "tutorial" to represent user's tutorial status.
This commit updates the package-lock.json and package.json files to include the latest versions of the "feather-icons" and "vue-feather" packages. Additionally, it adds the "VueFeather" component to the main.ts file, allowing it to be used in the application. Changes include: - Adding "feather-icons@4.29.1" and "vue-feather@2.0.0" to package.json and package-lock.json - Importing and registering the "VueFeather" component in main.ts
The new code changes include adding support for joining the media server through Plex. This allows users to enter their invite code and join the server directly from Plex. Additionally, an error message has been added to handle any issues that may occur while creating an account.
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.