Translations #270
Merged
Translations #270
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
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".
- 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.
The release workflow has been updated to check if the release is on the master branch. If it is not, the job will succeed and skip further steps.
…_branch" The commit renames the code segment from "main_branch" to "master_branch" in the release.yml workflow file, ensuring consistency with the branch naming convention.
To align with the repository's branch naming convention, this change updates the reference from "main" to "master" in the release.yml file. This ensures consistency and avoids any confusion during the build and release process.
Previously, the CI workflow did not check if changes only applied to README.md, .github, .vscode, resulting in unnecessary builds. With this commit, a new job named "check_changes" has been added to ensure that the workflow does not run if changes are limited to these files. The "build_ghcr" and "build_dh" jobs have also been updated to depend on the "check_changes" job. This improvement helps optimize the CI process and saves resources.
This commit adds a step to checkout the repository using the `actions/checkout` action, which will allow subsequent steps to access the repository's code and files.
The GHCR build workflow has been refactored to improve efficiency and support building on multiple platforms. A matrix strategy has been added to configure the build for both linux/amd64 and linux/arm64 architectures. The workflow now checks for changes that only apply to README.md, .github, and .vscode, and will successfully exit if no other changes are detected.
This commit adds paths to ignore in the push event to avoid triggering workflows for changes that only apply to README.md, .github, and .vscode directories.
This commit adds concurrency group and cancellation to the beta CI workflow. Now, actions in the workflow will be grouped based on the GitHub reference and any in-progress actions will be cancelled before starting a new one.
This commit simplifies the release workflow by renaming a job, removing unnecessary steps, and improving the branch and pre-release checks. The workflow now checks if the release is on the master branch and if it is a pre-release before proceeding with the build steps. It also sets the latest tag to the release tag for both GHCR and Docker Hub builds.
The commit adds a new workflow file for deleting workflow runs and also modifies an existing workflow file to check if a release is a pre-release. The new workflow file defines inputs for the repository, workflow, and what-if parameters. The modified workflow file includes a step to check if the release is a pre-release before continuing the workflow.
Added a new workflow that allows users to delete old workflow runs.
The commit adds the delete-old-workflow-runs action to the workflow. Inputs for repository, workflow, and what-if are required and have appropriate descriptions. Validation is added to ensure the correct input types are used.
Update the workflow to delete old workflow runs. The repository and workflow inputs are now hardcoded as "wizarrrr/wizarr" and ".github/workflows/tailwindcss.yml" respectively. The "what-if" input is set to true.
- Change the runs-on value in beta-ci.yml to "self-hosted" in two jobs - Update the root directory in nginx-main.conf from "/data/frontend" to "/wizarr/frontend"
- Change runs-on value for build_ghcr and build_dh jobs in the beta-ci.yml GitHub Actions workflow from "self-hosted" to "ubuntu-latest" for consistency and reliability. - Update the session file and upload folder paths in the app configuration file to use the definitions from the definitions module for better maintainability. - Update the path to the latest file in the get_current_version function in the migrator module to use the LATEST_FILE definition for clarity and simplicity. - Update the path to the latest file in the get_current_version function in the software_lifecycle module to use the LATEST_FILE definition for consistency and readability. - Add new definitions to the definitions module for ROOT_DIR, LATEST_FILE, and DATABASE_DIR to improve configuration flexibility in different environments. - Update the environment variable names in the Dockerfile for wizarr-backend and wizarr to use DATABASE_DIR and LATEST_FILE for consistency with the definitions module. - Add a new environment variable LATEST_FILE to the Dockerfile for wizarr-frontend for consistency with the other Dockerfiles.
- Replace environment variable check with a direct import from the definitions file. - Update the database file path in the `db_file` variable. - Update the backup location in the `backup_location` variable. - Improvements made to code readability and maintainability.
- Moves the file logger path to refer to the correct database directory - Updates the secret key file path to use the correct database directory.
- Refactored the logging and database directory paths to use a constant from `definitions.py`. - Updated the paths in `logging_api.py`, `globals.py`, and `clear_logs.py` to use the constant. - This change improves code readability and maintainability.
…y. Update the Dockerfile for Wizarr backend to copy package files and install dependencies.
…ng dependencies The commit updates the beta-ci.yml and Dockerfile to specify the use of Node.js 18.18.2 for installing project dependencies. Previously, the actions/setup-node@v2 step did not explicitly set the required Node.js version, resulting in inconsistent dependency installations.
The commit updates the beta-ci.yml file to use Node.js version 18.18.2 for installing dependencies. This ensures consistent development and testing environment.
The .dockerignore file was modified to exclude /tmp, /dockerfiles/wizarr-backend/database, /apps/wizarr-backend/database, **/.venv, venv/, .git, .idea, .buildHelper.txt, and __pycache__ directories, as well as node_modules and Dockerfile from being included in Docker builds.
- Update beta-ci.yml to include Python and Poetry setup - Modify Dockerfile to build wizarr-ci image with updated dependencies and configurations - Add new docker-entrypoint.sh script for running Gunicorn and Nginx
- The Dockerfile for Wizarr CI has been updated to improve the build process. - Changes include setting environment variables, installing dependencies, and building the Wizarr backend and frontend. - System dependencies have been installed and the Wizarr frontend and backend are copied to their respective directories. - The Wizarr backend package is unpacked for further use.
- Update the branch triggering the workflow from 'v3-mono' to 'v3-beta' - Change the image tag from 'v3-mono' to 'v3-beta'
This commit updates the release workflow in the Docker Build and Push Release configuration. It introduces new steps to check if the release is a pre-release or if it is on the master branch. Depending on these conditions, the workflow may continue or be skipped. Additionally, the build process for GHCR and Docker Hub has been modified to include installation of dependencies using Node.js 18.18.2 and Python's Poetry package manager.
Compile translations
…y outside of the previous step.
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.