chore(deps): update dependency mypy to v1.11.1 (#3963)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

.devcontainer/Dockerfile

@@ -38,3 +38,6 @@ RUN apt-get update \
     libwebp-dev \
     libsasl2-dev libldap2-dev libssl-dev \
     gnupg gnupg2 gnupg1
+
+# create directory used for Docker Secrets
+RUN mkdir -p /run/secrets

.devcontainer/devcontainer.json

@@ -27,6 +27,7 @@
         "python.formatting.yapfPath": "/usr/local/py-utils/bin/yapf",
       },
       "extensions": [
+        "charliermarsh.ruff",
         "dbaeumer.vscode-eslint",
         "matangover.mypy",
         "ms-python.black-formatter",

.dockerignore

@@ -26,7 +26,7 @@ venv
 */node_modules
 */dist
 */data/db
-*/mealie/test 
+*/mealie/test
 */mealie/.temp
 
 model.crfmodel

.gitattributes

@@ -1,2 +1,2 @@
 *.css linguist-detectable=false
-*.html linguist-detectable=false
+*.html linguist-detectable=false

.github/DISCUSSION_TEMPLATE/oauth-provider-example.yaml

@@ -5,5 +5,5 @@ body:
   attributes:
     label: Configuration Example
     description: Add your example configuration. You can provide code blocks, screenshots, and links.
-  validations: 
+  validations:
     required: true

.github/pull_request_template.md

@@ -1,12 +1,12 @@
 <!--
   This template provides some ideas of things to include in your PR description.
-  
+
   To start, try providing a short summary of your changes in the Title above. We follow Conventional Commits syntax, please ensure your title is prefixed with one of:
   - `feat: `
   - `fix: `
   - `docs: `
   - `chore: `
-  
+
   If a section of the PR template does not apply to this PR, then delete that section.
 
   PLEASE READ:

.github/workflows/codeql.yml

@@ -49,7 +49,7 @@ jobs:
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@v2
+      uses: github/codeql-action/init@v3
       with:
         languages: ${{ matrix.language }}
         # If you wish to specify custom queries, you can do so here or in a config file.
@@ -63,7 +63,7 @@ jobs:
     # Autobuild attempts to build any compiled languages (C/C++, C#, Go, Java, or Swift).
     # If this step fails, then you should remove it and run the build manually (see below)
     - name: Autobuild
-      uses: github/codeql-action/autobuild@v2
+      uses: github/codeql-action/autobuild@v3
 
     # ℹ️ Command-line programs to run using the OS shell.
     # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
@@ -76,6 +76,6 @@ jobs:
     #     ./location_of_script_within_repo/buildscript.sh
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v2
+      uses: github/codeql-action/analyze@v3
       with:
         category: "/language:${{matrix.language}}"

.github/workflows/release.yml

@@ -61,10 +61,15 @@ jobs:
       - name: Checkout 🛎
         uses: actions/checkout@v4
 
+      - name: Extract Version From Tag Name
+        run: echo "VERSION_NUM=$(echo ${{ github.event.release.tag_name }} | sed 's/^v//')" >> $GITHUB_ENV
+
       - name: Modify version strings
         run: |
-          sed -i 's/:v[0-9]*.[0-9]*.[0-9]*/:${{ github.event.release.tag_name }}/' docs/docs/documentation/getting-started/installation/sqlite.md
-          sed -i 's/:v[0-9]*.[0-9]*.[0-9]*/:${{ github.event.release.tag_name }}/' docs/docs/documentation/getting-started/installation/postgres.md
+          sed -i 's/:v[0-9]*.[0-9]*.[0-9]*/:v${{ env.VERSION_NUM }}/' docs/docs/documentation/getting-started/installation/sqlite.md
+          sed -i 's/:v[0-9]*.[0-9]*.[0-9]*/:v${{ env.VERSION_NUM }}/' docs/docs/documentation/getting-started/installation/postgres.md
+          sed -i 's/^version = "[^"]*"/version = "${{ env.VERSION_NUM }}"/' pyproject.toml
+          sed -i 's/^\s*"version": "[^"]*"/"version": "${{ env.VERSION_NUM }}"/' frontend/package.json
 
       - name: Create Pull Request
         uses: peter-evans/create-pull-request@v6

.github/workflows/scheduled-checks.yml

@@ -0,0 +1,32 @@
+name: Scheduled Checks
+
+on:
+  schedule:
+    # Every monday at 7 AM
+    - cron: 0 7 * * 1
+
+jobs:
+  update:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout 🛎
+        uses: actions/checkout@v4
+
+      - name: Update pre-commit Hooks
+        uses: vrslev/pre-commit-autoupdate@v1.0.0
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v6
+        # This doesn't currently work for us because it creates the PR but the workflows don't run.
+        # TODO: Provide a personal access token as a parameter here, that solves that problem.
+        # https://github.com/peter-evans/create-pull-request
+        with:
+          commit-message: "Update pre-commit hooks"
+          branch: "fix/update-pre-commit-hooks"
+          delete-branch: true
+          base: mealie-next
+          title: "fix(auto): Update pre-commit hooks"
+          body: "Auto-generated by `.github/workflows/scheduled-checks.yml`"

.pre-commit-config.yaml

@@ -1,6 +1,6 @@
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v2.3.0
+    rev: v4.6.0
     hooks:
       - id: check-yaml
         exclude: "mkdocs.yml"
@@ -12,6 +12,6 @@ repos:
         exclude: ^tests/data/
   - repo: https://github.com/astral-sh/ruff-pre-commit
     # Ruff version.
-    rev: v0.4.3
+    rev: v0.5.5
     hooks:
       - id: ruff-format

README.md

@@ -1,10 +1,10 @@
 [![Latest Release][latest-release-shield]][latest-release-url]
 [![Contributors][contributors-shield]][contributors-url]
-[![Forks][forks-shield]][forks-url]
 [![Stargazers][stars-shield]][stars-url]
 [![Issues][issues-shield]][issues-url]
 [![AGPL License][license-shield]][license-url]
-[![Docker Pulls][docker-pull]][docker-pull]
+[![Docker Pulls][docker-pull]][docker-url]
+[![GHCR Pulls][ghcr-pulls]][ghcr-url]
 
 <!-- PROJECT LOGO -->
 <br />
@@ -88,16 +88,17 @@ Thanks to Depot for providing build instances for our Docker image builds.
 <!-- MARKDOWN LINKS & IMAGES -->
 <!-- https://www.markdownguide.org/basic-syntax/#reference-style-links -->
 [contributors-shield]: https://img.shields.io/github/contributors/mealie-recipes/mealie.svg?style=flat-square
-[docker-pull]: https://img.shields.io/docker/pulls/hkotel/mealie
+[docker-pull]: https://img.shields.io/docker/pulls/hkotel/mealie?style=flat-square
+[docker-url]: https://hub.docker.com/r/hkotel/mealie
+[ghcr-pulls]: https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fraw.githubusercontent.com%2Fipitio%2Fghcr-pulls%2Fmaster%2Findex.json&query=%24%5B%3F(%40.owner%3D%3D%22mealie-recipes%22%20%26%26%20%40.repo%3D%3D%22mealie%22%20%26%26%20%40.image%3D%3D%22mealie%22)%5D.pulls&style=flat-square&label=ghcr%20pulls
+[ghcr-url]: https://github.com/mealie-recipes/mealie/pkgs/container/mealie
 [contributors-url]: https://github.com/mealie-recipes/mealie/graphs/contributors
-[forks-shield]: https://img.shields.io/github/forks/mealie-recipes/mealie.svg?style=flat-square
-[forks-url]: https://github.com/mealie-recipes/mealie/network/members
 [stars-shield]: https://img.shields.io/github/stars/mealie-recipes/mealie.svg?style=flat-square
 [stars-url]: https://github.com/mealie-recipes/mealie/stargazers
 [issues-shield]: https://img.shields.io/github/issues/mealie-recipes/mealie.svg?style=flat-square
 [issues-url]: https://github.com/mealie-recipes/mealie/issues
 [latest-release-shield]: https://img.shields.io/github/v/release/mealie-recipes/mealie?style=flat-square&label=latest%20release
-[latest-release-url]: https://img.shields.io/github/v/release/mealie-recipes/mealie
+[latest-release-url]: https://github.com/mealie-recipes/mealie/releases
 [license-shield]: https://img.shields.io/github/license/mealie-recipes/mealie.svg?style=flat-square
 [license-url]: https://github.com/mealie-recipes/mealie/blob/mealie-next/LICENSE
 [linkedin-shield]: https://img.shields.io/badge/-LinkedIn-black.svg?style=flat-square&logo=linkedin&colorB=555

Taskfile.yml

@@ -148,7 +148,7 @@ tasks:
       - poetry run python mealie/app.py
 
   py:migrate:
-    desc: generates a new migration file e.g. task py:migrate:generate "add new column"
+    desc: generates a new database migration file e.g. task py:migrate -- "add new column"
     cmds:
       - poetry run alembic revision --autogenerate -m "{{ .CLI_ARGS }}"
       - task: py:format

alembic/README

@@ -1 +1 @@
-Generic single-database configuration.
+Generic single-database configuration.

alembic/versions/2023-02-14-20.45.41_5ab195a474eb_add_normalized_search_properties.py

@@ -13,7 +13,7 @@ from text_unidecode import unidecode
 
 import mealie.db.migration_types
 from alembic import op
-from mealie.db.models._model_utils import GUID
+from mealie.db.models._model_utils.guid import GUID
 
 # revision identifiers, used by Alembic.
 revision = "5ab195a474eb"

alembic/versions/2024-03-18-02.28.15_d7c6efd2de42_migrate_favorites_and_ratings_to_user_.py

@@ -6,7 +6,7 @@ Create Date: 2024-03-18 02:28:15.896959
 
 """
 
-from datetime import datetime
+from datetime import datetime, timezone
 from textwrap import dedent
 from typing import Any
 from uuid import uuid4
@@ -34,7 +34,7 @@ def new_user_rating(user_id: Any, recipe_id: Any, rating: float | None = None, i
     else:
         id = "%.32x" % uuid4().int
 
-    now = datetime.now().isoformat()
+    now = datetime.now(timezone.utc).isoformat()
     return {
         "id": id,
         "user_id": user_id,

alembic/versions/2024-06-22-10.17.03_32d69327997b_add_staple_flag_to_foods.py

@@ -0,0 +1,48 @@
+"""Add staple flag to foods
+
+Revision ID: 32d69327997b
+Revises: 7788478a0338
+Create Date: 2024-06-22 10:17:03.323966
+
+"""
+
+import sqlalchemy as sa
+from sqlalchemy import orm
+
+from alembic import op
+
+
+# revision identifiers, used by Alembic.
+revision = "32d69327997b"
+down_revision = "7788478a0338"
+branch_labels = None
+depends_on = None
+
+
+def is_postgres():
+    return op.get_context().dialect.name == "postgresql"
+
+
+def upgrade():
+    with op.batch_alter_table("ingredient_foods") as batch_op:
+        batch_op.add_column(sa.Column("on_hand", sa.Boolean(), nullable=True, default=False))
+
+    bind = op.get_bind()
+    session = orm.Session(bind=bind)
+
+    with session:
+        if is_postgres():
+            stmt = "UPDATE ingredient_foods SET on_hand = FALSE;"
+        else:
+            stmt = "UPDATE ingredient_foods SET on_hand = 0;"
+
+        session.execute(sa.text(stmt))
+
+    # forbid nulls after migration
+    with op.batch_alter_table("ingredient_foods") as batch_op:
+        batch_op.alter_column("on_hand", nullable=False)
+
+
+def downgrade():
+    with op.batch_alter_table("ingredient_foods") as batch_op:
+        batch_op.drop_column("on_hand")

dev/code-generation/templates/test_data.py.j2

@@ -4,4 +4,4 @@ CWD = Path(__file__).parent
 
 {% for f in data.children %}
 {{ f.var }} = CWD / "{{ f.path }}"
-{% endfor %}
+{% endfor %}

dev/data/templates/recipes.md

@@ -6,11 +6,11 @@
 {{ recipe.description }}
 
 ## Ingredients
-{% for ingredient in recipe.recipeIngredient %} 
+{% for ingredient in recipe.recipeIngredient %}
 - [ ] {{ ingredient }} {% endfor %}
 
 ## Instructions
-{% for step in recipe.recipeInstructions %} 
+{% for step in recipe.recipeInstructions %}
 - [ ] {{ step.text }} {% endfor %}
 
 {% for note in recipe.notes %}
@@ -21,4 +21,4 @@
 
 Tags: {{ recipe.tags }}
 Categories: {{ recipe.categories }}
-Original URL: {{ recipe.orgURL }}
+Original URL: {{ recipe.orgURL }}

docker/Dockerfile

@@ -92,6 +92,9 @@ RUN apt-get update \
     libldap-2.5 \
     && rm -rf /var/lib/apt/lists/*
 
+# create directory used for Docker Secrets
+RUN mkdir -p /run/secrets
+
 # copying poetry and venv into image
 COPY --from=builder-base $POETRY_HOME $POETRY_HOME
 COPY --from=builder-base $PYSETUP_PATH $PYSETUP_PATH
@@ -104,7 +107,6 @@ COPY --from=crfpp /usr/local/bin/crf_test /usr/local/bin/crf_test
 # copy backend
 COPY ./mealie $MEALIE_HOME/mealie
 COPY ./poetry.lock ./pyproject.toml $MEALIE_HOME/
-COPY ./gunicorn_conf.py $MEALIE_HOME
 
 # Alembic
 COPY ./alembic $MEALIE_HOME/alembic

docker/docker-compose.yml

@@ -25,12 +25,6 @@ services:
       POSTGRES_PORT: 5432
       POSTGRES_DB: mealie
 
-      # =====================================
-      # Web Concurrency
-      WEB_GUNICORN: "false"
-      WORKERS_PER_CORE: 0.5
-      MAX_WORKERS: 1
-      WEB_CONCURRENCY: 1
       # =====================================
       # Email Configuration
       # SMTP_HOST=

docker/entry.sh

@@ -37,14 +37,8 @@ init() {
 
 change_user
 init
-GUNICORN_PORT=${API_PORT:-9000}
 
 # Start API
 HOST_IP=`/sbin/ip route|awk '/default/ { print $3 }'`
 
-if [ "$WEB_GUNICORN" = 'true' ]; then
-    echo "Starting Gunicorn"
-    exec gunicorn mealie.app:app -b 0.0.0.0:$GUNICORN_PORT --forwarded-allow-ips=$HOST_IP -k uvicorn.workers.UvicornWorker -c /app/gunicorn_conf.py --preload
-else
-    exec python /app/mealie/main.py
-fi
+exec python /app/mealie/main.py

docs/docs/assets/other/n8n/n8n-mealie-backup.json

@@ -0,0 +1,386 @@
+{
+  "name": "Mealie Backup",
+  "nodes": [
+    {
+      "parameters": {
+        "rule": {
+          "interval": [
+            {}
+          ]
+        }
+      },
+      "id": "2ec440b4-0668-4bc0-aa66-4023d6379f28",
+      "name": "Schedule Trigger",
+      "type": "n8n-nodes-base.scheduleTrigger",
+      "typeVersion": 1.1,
+      "position": [
+        240,
+        660
+      ]
+    },
+    {
+      "parameters": {
+        "method": "POST",
+        "url": "https://mealie.example/api/admin/backups",
+        "authentication": "genericCredentialType",
+        "genericAuthType": "httpHeaderAuth",
+        "options": {}
+      },
+      "id": "235f26f7-0f45-479e-a7e3-bf8cda7c8426",
+      "name": "Run Backup ",
+      "type": "n8n-nodes-base.httpRequest",
+      "typeVersion": 4.1,
+      "position": [
+        520,
+        520
+      ],
+      "notesInFlow": false,
+      "credentials": {
+        "httpHeaderAuth": {
+          "id": "GSL12tNi3MPvTZux",
+          "name": "Mealie API"
+        }
+      },
+      "notes": "Send an API call to run the backup"
+    },
+    {
+      "parameters": {
+        "method": "POST",
+        "url": "https://ntfy.example/backups",
+        "sendHeaders": true,
+        "headerParameters": {
+          "parameters": [
+            {
+              "name": "Title",
+              "value": "Meale Backup Failure"
+            },
+            {
+              "name": "Priority",
+              "value": "urgent"
+            },
+            {
+              "name": "Tags",
+              "value": "warning"
+            },
+            {
+              "name": "Actions",
+              "value": "view, Open Mealie, https://mealie.example/admin/backups; view, Open n8n, https://n8n.example"
+            }
+          ]
+        },
+        "sendBody": true,
+        "contentType": "raw",
+        "body": "\"Full Panic!\"",
+        "options": {}
+      },
+      "id": "40ba81a5-5741-4b15-98af-1a9e6b34f997",
+      "name": "Ntfy Warning",
+      "type": "n8n-nodes-base.httpRequest",
+      "typeVersion": 4.1,
+      "position": [
+        1000,
+        520
+      ],
+      "onError": "continueRegularOutput"
+    },
+    {
+      "parameters": {
+        "url": "https://mealie.example/api/admin/backups",
+        "authentication": "genericCredentialType",
+        "genericAuthType": "httpHeaderAuth",
+        "options": {}
+      },
+      "id": "b75571d0-d926-440c-897f-55b89c6a5080",
+      "name": "Get all backups",
+      "type": "n8n-nodes-base.httpRequest",
+      "typeVersion": 4.1,
+      "position": [
+        520,
+        820
+      ],
+      "credentials": {
+        "httpHeaderAuth": {
+          "id": "GSL12tNi3MPvTZux",
+          "name": "Mealie API"
+        }
+      }
+    },
+    {
+      "parameters": {
+        "fieldToSplitOut": "imports",
+        "options": {}
+      },
+      "id": "943d0e83-682b-4500-9faf-53284cfb02c6",
+      "name": "Split Out",
+      "type": "n8n-nodes-base.splitOut",
+      "typeVersion": 1,
+      "position": [
+        720,
+        820
+      ]
+    },
+    {
+      "parameters": {
+        "jsCode": "// Get input data\nconst inputData = items.map(item => item.json);\n\n// Sort the data based on the 'date' field in descending order\ninputData.sort((a, b) => new Date(b.date) - new Date(a.date));\n\n// Get all records except the latest 7\nconst allExceptLatest7 = inputData.slice(7);\n\n// Map the output data back to the required format\nreturn allExceptLatest7.map(record => ({ json: record }));\n"
+      },
+      "id": "64eae81d-fdb6-44f7-9a2d-eff8d1763281",
+      "name": "Code",
+      "type": "n8n-nodes-base.code",
+      "typeVersion": 2,
+      "position": [
+        860,
+        820
+      ]
+    },
+    {
+      "parameters": {
+        "method": "DELETE",
+        "url": "=https://mealie.example/api/admin/backups/{{ $json.name }}",
+        "authentication": "genericCredentialType",
+        "genericAuthType": "httpHeaderAuth",
+        "options": {}
+      },
+      "id": "1148eeb8-4860-46df-8f61-0e85ea1e0e89",
+      "name": "Delete Oldies",
+      "type": "n8n-nodes-base.httpRequest",
+      "typeVersion": 4.1,
+      "position": [
+        1040,
+        820
+      ],
+      "credentials": {
+        "httpHeaderAuth": {
+          "id": "GSL12tNi3MPvTZux",
+          "name": "Mealie API"
+        }
+      }
+    },
+    {
+      "parameters": {
+        "content": "Sends API Call to run backup",
+        "height": 225,
+        "width": 226,
+        "color": 4
+      },
+      "id": "cd2cb5db-87c1-40d8-a746-e61ace231987",
+      "name": "Sticky Note",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        460,
+        460
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Is there an error?",
+        "height": 225,
+        "width": 231,
+        "color": 3
+      },
+      "id": "0bebecbe-903e-4a69-bb1a-35619e68b540",
+      "name": "Sticky Note1",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        700,
+        460
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Send alert to NTFY",
+        "height": 225,
+        "width": 229
+      },
+      "id": "0b732adb-8a84-456d-b26d-5fc5ee5a4cae",
+      "name": "Sticky Note2",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        940,
+        460
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Gets all backups in Mealie",
+        "height": 225,
+        "width": 226,
+        "color": 4
+      },
+      "id": "99c6886b-6a07-4b51-b395-d4bbcbde7d18",
+      "name": "Sticky Note3",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        460,
+        760
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Splits the data, and parses the output",
+        "height": 225,
+        "width": 281
+      },
+      "id": "549555f8-0aed-42c0-9693-9c0d93902796",
+      "name": "Sticky Note4",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        700,
+        760
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Deletes all but the last 7 backups",
+        "height": 225,
+        "width": 229
+      },
+      "id": "bcc5f0ba-73e9-42d7-b01b-c32f9f69f2f7",
+      "name": "Sticky Note5",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        1000,
+        760
+      ]
+    },
+    {
+      "parameters": {
+        "content": "Run every day a 01:00",
+        "height": 225,
+        "width": 226,
+        "color": 4
+      },
+      "id": "ce797062-d727-43e3-a27f-e29b13ad3c9a",
+      "name": "Sticky Note6",
+      "type": "n8n-nodes-base.stickyNote",
+      "typeVersion": 1,
+      "position": [
+        180,
+        600
+      ]
+    },
+    {
+      "parameters": {
+        "conditions": {
+          "options": {
+            "caseSensitive": true,
+            "leftValue": "",
+            "typeValidation": "strict"
+          },
+          "conditions": [
+            {
+              "id": "8b00bb85-827f-4f2f-813e-db0d25e927d3",
+              "leftValue": "={{ $json.error }}",
+              "rightValue": "",
+              "operator": {
+                "type": "boolean",
+                "operation": "true",
+                "singleValue": true
+              }
+            }
+          ],
+          "combinator": "and"
+        },
+        "options": {}
+      },
+      "id": "fefd3e8b-9b71-490a-82e3-25e5468a4135",
+      "name": "Error?",
+      "type": "n8n-nodes-base.filter",
+      "typeVersion": 2,
+      "position": [
+        760,
+        520
+      ]
+    }
+  ],
+  "pinData": {},
+  "connections": {
+    "Schedule Trigger": {
+      "main": [
+        [
+          {
+            "node": "Run Backup ",
+            "type": "main",
+            "index": 0
+          },
+          {
+            "node": "Get all backups",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    },
+    "Run Backup ": {
+      "main": [
+        [
+          {
+            "node": "Error?",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    },
+    "Get all backups": {
+      "main": [
+        [
+          {
+            "node": "Split Out",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    },
+    "Split Out": {
+      "main": [
+        [
+          {
+            "node": "Code",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    },
+    "Code": {
+      "main": [
+        [
+          {
+            "node": "Delete Oldies",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    },
+    "Error?": {
+      "main": [
+        [
+          {
+            "node": "Ntfy Warning",
+            "type": "main",
+            "index": 0
+          }
+        ]
+      ]
+    }
+  },
+  "active": false,
+  "settings": {
+    "executionOrder": "v1"
+  },
+  "versionId": "68e3e469-3ddb-4838-b09d-3c69fdd851f5",
+  "meta": {
+    "templateCredsSetupCompleted": true,
+    "instanceId": "630eefaa8c490b9c5221d83a182af6450c2c3efaf4b580b8ac348631abfe1aeb"
+  },
+  "id": "whloxeXkdBWWi2Uj",
+  "tags": []
+}

docs/docs/assets/svg/open-in-new.svg

@@ -1,3 +1,3 @@
 <svg xmlns="http://www.w3.org/2000/svg" width="12" height="12" viewBox="0 0 24 24">
 <path fill="rgb(229,131,37)" d="M14,3V5H17.59L7.76,14.83L9.17,16.24L19,6.41V10H21V3M19,19H5V5H12V3H5C3.89,3 3,3.9 3,5V19A2,2 0 0,0 5,21H19A2,2 0 0,0 21,19V12H19V19Z" />
-</svg>
+</svg>

docs/docs/changelog/v0.1.0.md

@@ -1,88 +0,0 @@
-# v0.1.0 - Initial Beta
-
-### Bug Fixes
-  - Fixed Can't delete recipe after changing name - Closes Closes #67
-  - Fixed No image when added by URL, and can't add an image - Closes Closes #66
-  - Fixed Images saved with no way to delete when add recipe via URL fails - Closes Closes #43
-
-### Features
-  - Additional Language Support
-  - Improved deployment documentation
-  - Additional database! SQlite is now supported! - Closes #48
-  - All site data is now backed up.
-  - Support for Prep Time, Total Time, and Cook Time field - Closes #63
-  - New backup import process with support for themes and site settings
-  - **BETA** ARM support! - Closes #69
-
-### Code / Developer Improvements
-  - Unified Database Access Layers
-  - Poetry / pyproject.toml support over requirements.txt
-  - Local development without database is now possible!
-  - Local mkdocs server added to docker-compose.dev.yml
-  - Major code refactoring to support new database layer
-  - Global variable refactor
-
-### Breaking Changes
-
-- Internal docker port is now 80 instead of 9000. You MUST remap the internal port to connect to the UI. 
-
-!!! error "Breaking Changes"
-    As I've adopted the SQL database model I find that using 2 different types of databases will inevitably hinder development. As such after release v0.1.0 support for mongoDB will no longer be available. Prior to upgrading to v0.2.0 you will need to export your site and import after updating. This should be a painless process and require minimal intervention on the users part. Moving forward we will do our best to minimize changes that require user intervention like this and make updates a smooth process. 
-
-
-## v0.0.2 - Pre-release Second Patch
-A quality update with major props to [zackbcom](https://github.com/zackbcom) for working hard on making the theming just that much better!
-
-### Bug Fixes
-  - Fixed empty backup failure without markdown template
-  - Fixed opacity issues with marked steps - [mtoohey31](https://github.com/mtoohey31)
-  - Fixed hot-reloading development environment - [grssmnn](https://github.com/grssmnn)
-  - Fixed recipe not saving without image - Closes #7 + Closes #54
-  - Fixed parsing error on image property null - Closes #43
-
-### General Improvements
-  - Added Confirmation component to deleting recipes - [zackbcom](https://github.com/zackbcom)
-  - Updated Theme backend - [zackbcom](https://github.com/zackbcom)
-  - Added Persistent storage to vuex - [zackbcom](https://github.com/zackbcom)
-  - General Color/Theme Improvements
-      - More consistent UI
-      - More minimalist coloring
-  - Added API key extras to Recipe Data - [See Documentation](/api/api-usage/)
-      - Users can now add custom json key/value pairs to all recipes via the editor for access in 3rd part applications. For example users can add a "message" field in the extras that can be accessed on API calls to play a message over google home. 
-  - Improved image rendering (nearly x2 speed)
-  - Improved documentation + API Documentation
-  - Improved recipe parsing - Closes #51
-  - User feedback on backup importing
-
-## v0.0.1 - Pre-release Patch
-### General
-  - Updated Favicon
-  - Renamed Frontend Window
-  - Added Debug folder to dump scraper data prior to processing. 
-
-### Recipes
-  - Added user feedback on bad URL
-  - Better backend data validation for updating recipes, avoid small syntax errors corrupting database entry. [Closes #8](https://github.com/mealie-recipes/mealie/issues/8)
-  - Fixed spacing Closes while editing new recipes in JSON
-
-## v0.0.0 - Initial Pre-release
-The initial pre-release. It should be semi-functional but does not include a lot of user feedback You may notice errors that have no user feedback and have no idea what went wrong. 
-
-### Recipes
-  - Automatic web scrapping for common recipe platforms
-  - Interactive API Documentation thanks to [FastAPI](https://fastapi.tiangolo.com/) and [Swagger](https://petstore.swagger.io/)
-  - UI Recipe Editor
-  - JSON Recipe Editor in browser
-  - Custom tags and categories
-  - Rate recipes
-  - Add notes to recipes
-  - Migration From Other Platforms
-    - Chowdown
-### Meal Planner
-  - Random Meal plan generation based off categories
-  - Expose notes in the API to allow external applications to access relevant information for meal plans
-  
-### Database Import / Export
-  - Easily Import / Export your recipes from the UI
-  - Export recipes in markdown format for universal access
-    - Use the default or a custom jinja2 template

docs/docs/changelog/v0.2.0.md

@@ -1,72 +0,0 @@
-# v0.2.1 - Hot Fixes!
-
-### Features and Improvements
-  - Fixes upload image error when no photo was scrapped
-  - Fixes no last_recipe.json not updating
-  - Added markdown rendering for notes
-  - New notifications
-  - Minor UI improvements
-  - Recipe editor refactor
-  - Settings/Theme models refactor
-
-### Development / Misc
-  - Added async file response for images, downloading files.
-  - Breakup recipe view component
-
-# v0.2.0 - Now with Test!
-This is, what I think, is a big release! Tons of new features and some great quality of life improvements with some additional features. You may find that I made promises to include some fixes/features in v0.2.0. The short of is I greatly underestimated the work needed to refactor the database to a usable state and integrate categories in a way that is useful for users. This shouldn't be taken as a sign that I'm dropping those feature requests or ignoring them. I felt it was better to push a release in the current state rather than drag on development to try and fulfil all of the promises I made. 
-
-!!! warning "Upgrade Process"
-    Database Breaks! I have not yet implemented a database migration service. As such, upgrades cannot be done by simply pulling the image. You must first export your recipes, update your deployment, and then import your recipes. This pattern is likely to be how upgrades take place prior to v1.0. After v1.0 migrations will be done automatically.
-
-### Bug Fixes
-  - Remove ability to save recipe with no name
-  - Fixed data validation error on missing parameters
-  - Fixed failed database initialization at startup - Closes #98
-  - Fixed misaligned text on various cards
-  - Fixed bug that blocked opening links in new tabs - Closes #122
-  - Fixed router link bugs - Closes #122
-  - Fixed navigation on keyboard selection - Closes #139
-
-### Features and Improvements
-  - 🐳 Dockerfile now 1/5 of the size!
-  - 🌎 UI Language Selection + Additional Supported Language
-  - **Home Page**
-    - By default your homepage will display only the recently added recipes. You can configured sections to show on the home-screen based of categories on the settings page. 
-    - A new sidebar is now shown on the main page that lists all the categories in the database. Clicking on them navigates into a page that shows only recipes. 
-    - Basic Sort functionality has been added. More options are on the way! 
-  - **Meal Planner**
-    - Improved Search (Fuzzy Search)
-    - New Scheduled card support 
-  - **Recipe Editor**
-    - Ingredients are now sortable via drag-and-drop
-    - Known categories now show up in the dropdown - Closes 83
-    - Initial code for data validation to prevent errors
-  - **Migrations**
-    - Card based redesign
-    - Upload from the UI
-    - Unified Chowdown / Nextcloud import process. (Removed Git as a dependency)
-  - **API**
-    - Category and Tag endpoints added
-    - Major Endpoint refactor
-    - Improved API documentation
-    - Link to your Local API is now on your `/settings/site`. You can use it to explore your API. 
-
-  - **Style**
-    - Continued work on button/style unification
-    - Adding icons to buttons
-    - New Color Theme Picker UI
-
-### Development
-  - Fixed Vetur config file. Autocomplete in VSCode works!
-  - File/Folder restructuring 
-  - Added Prettier config
-  - Fixed incorrect layout code
-  - FastAPI Route tests for major operations - WIP (shallow testing)
-
-### Breaking Changes 
-
-!!! error "Breaking Changes"
-    - API endpoints have been refactored to adhere to a more consistent standard. This is a WIP and more changes are likely to occur. 
-    - Officially Dropped MongoDB Support
-    - Database Breaks! We have not yet implemented a database migration service. As such, upgrades cannot be done by simply pulling the image. You must first export your recipes, update your deployment, and then import your recipes. This pattern is likely to be how upgrades take place prior to v1.0. After v1.0 migrations will be done automatically. 

docs/docs/changelog/v0.3.0.md

@@ -1,29 +0,0 @@
-# v0.3.0
-
-### Bug Fixes
-  - Fixed open search on `/` when in input. - Closes #174
-  - Error when importing recipe: KeyError: '@type' - Closes #145
-  - Fixed Import Issue - bhg.com - Closes #138
-  - Scraper not working with recipe containing HowToSection - Closes #73
-
-### Features and Improvements
-  - Improved Nextcloud Imports
-  - Improved Recipe Parser!
-  - Open search with `/` hotkey! 
-  - Database and App version are now split
-  - Unified and improved snackbar notifications
-  - New Category/Tag endpoints to filter all recipes by Category or Tag
-  - Category sidebar now has show/hide behavior on mobile
-  - Settings menu on mobile is improved
-  - **Meal Planner**
-    - You can now restrict recipe categories used for random meal-plan creation in the settings menu
-    - Recipe picker dialog will now display recipes when the search bar is empty
-    - Minor UI improvements
-    - **Shopping lists!** Shopping list can now be generated from a meal plan. Currently ingredients are split by recipes or there is a beta feature that attempts to sort them by similarity.
-  - **Recipe Viewer**
-    - Categories, Tags, and Notes will now be displayed below the steps on smaller screens
-  - **Recipe Editor**
-    - Text areas now auto grow to fit content
-    - Description, Steps, and Notes support Markdown! This includes inline html in Markdown. 
-  - **Imports**
-    - A revamped dialog has been created to provide more information on restoring backups. Exceptions on the backend are now sent to the frontend and are easily viewable to see what went wrong when you restored a backup. This functionality will be ported over to the migrations in a future release. 

docs/docs/changelog/v0.4.0.md

@@ -1,86 +0,0 @@
-# v0.4.0 Whoa, What a Release!
-
-**App Version: v0.4.0**
-
-**Database Version: v0.4.0**
-
-## Breaking Changes
-
-!!! error "Breaking Changes"
-
-    #### Database
-    A new database will be created. You must export your data and then import it after upgrading.
-
-    #### Site Settings
-    With the addition of group settings and a re-write of the database layer of the application backend, there is no migration path for your current site settings. Webhooks Settings, Meal Plan Categories are now managed by groups. Site settings, mainly homepage settings, are now site specific and managed by administrators. When upgrading be sure to uncheck the settings when importing your old data. 
-
-    #### ENV Variables
-    Names have been changed to be more consistent with industry standards. See the [Installation Page](/mealie/getting-started/install/) for new parameters.  
-
-## Bug Fixes
-- Fixed Search Results Limited to 100 - #198
-- Fixed recipes from marmiton.org not fully scrapped  - #196
-- Fixed Unable to get a page to load - #194
-- Fixed Recipe's from Epicurious don't upload. - #193
-- Fixed Edited blank recipe in meal plan is not saved - #184
-- Fixed Create a new meal plan allows selection of an end date that is prior to the start date - #183
-- Fixed Original URL not saved to imported recipe in 0.3.0-dev - #183
-- Fixed "IndexError: list index out of range" when viewing shopping list for meal plan containing days without a recipe selected - #178
-
-## Features and Improvements
-
-### General
-  - Documentation Rewrite
-  - [New Demo Site!](https://mealie-demo.hay-kot.dev/)
-  - New Documentation
-    - Landing Page
-    - Custom Caddy Configuration
-    - User Management 
-    - Introduction
-  - Updated Documentation
-    - Everything!
-  - The API Reference is now better embedded inside of the docs
-  - New default external port in documentation (Port 9000 -> 9925). This is only the port exposed by the host to the docker image. It doesn't change any existing functionality. 
-
-### User Authentication 
-  - Authentication! Tons of stuff went into creating a flexible authentication platform for a lot of different use cases. Review the documentation for more information on how to use the authentication, and how everything works together. More complex management of recipes and user restrictions are in the works, but this is a great start! Some key features include
-    - Sign Up Links
-    - Admin and User Roles
-    - Password Change
-    - Group Management
-    - Create/Edit/Delete Restrictions
-
-### Custom Pages
-  - You can now create custom pages that are displayed on the homepage sidebar to organize categories of recipes into pages. For example, if you have several categories that encompass "Entrée" you can group all those categories together under the "Entrée" page. See [Building Pages](/mealie/site-administration/building-pages/) for more information.
-!!! tip 
-    Note that this replaces the behavior of automatically adding categories to the sidebar.
-
-### UI Improvements
-  - Completed Redesign of the Admin Panel
-    - Profile Pages
-    - Side Panel Menu
-  - Improved UI for Recipe Search
-  - Language selector is now displayed on all pages and does not require an account
-
-### Recipe Data
-  - Recipe Database Refactoring. Tons of new information is now stored for recipes in the database. Not all is accessible via the UI, but it's coming.
-    - Nutrition Information
-      - calories
-      - fatContent
-      - fiberContent
-      - proteinContent
-      - sodiumContent
-      - sugarContent
-    - recipeCuisine has been added
-    - "categories" has been migrated to "recipeCategory" to adhere closer to the standard schema
-    - "tool" - a list of tools used for the recipe
-
-### Behind the Scenes
-  - Removed CDN dependencies
-  - Database Model Refactoring
-  - Import/Export refactoring
-  - File/Folder Name Refactoring
-  - Development is now easier with a makefile
-  - Mealie is now a proper package using poetry 
-  - Test refactoring
-  - Test Coverage 83% up from 75%!

docs/docs/changelog/v0.4.1.md

@@ -1,35 +0,0 @@
-# v0.4.1
-
-**App Version: v0.4.1**
-
-**Database Version: v0.4.0**
-
-!!! error "Breaking Changes"
-
-    #### Recipe Images
-    While it *shouldn't* be a breaking change, I feel it is important to note that you may experience issues with the new image migration. Recipe images are now minified, this is done on start-up, import, migration, and when a new recipe is created. The initial boot or load may be a bit slow if you have lots of recipes but you likely won't notice. What you may notice is that if your recipe slug and the image name do not match, you will encounter issues with your images showing up. This can be resolved by finding the image directory and rename it to the appropriate slug. I did fix multiple edge cases, but it is likely more exists. As always make a backup before you update! 
-
-    On the plus side, this comes with a huge performance increase! 🎉
-
-- Add markdown support for ingredients - Resolves #32
-- Ingredients editor improvements
-- Fix Tags/Categories render problems on recipes
-- Tags redirect to new tag pages
-- Categories redirect to category pages
-- Fix Backup download blocked by authentication
-- Random meal-planner will no longer duplicate recipes unless no other options
-- New Quick Week button to generate next 5 day week of recipe slots.
-- Minor UI tweaks
-- Recipe Cards now display 2 recipe tags
-- Recipe images are now minified. This comes with a serious performance improvement. On initial startup you may experience some delays. Images are migrated to the new structure on startup, depending on the size of your database this can take some time. 
-    - Note that original images are still kept for large displays like on the individual recipe pages.
-    - A smaller image is used for recipe cards
-    - A 'tiny' image is used for search images. 
-- Advanced Search Page. You can now use the search page to filter recipes to include/exclude tags and categories as well as select And/Or matching criteria. 
-- Added link to advanced search on quick search
-- Better support for NextCloud imports
-    - Translate keywords to tags
-    - Fix rollback on failure
-- Recipe Tag/Category Input components have been unified and now share a single way to interact. To add a new category in the recipe editor you need to click to '+' icon next to the input and fill out the form. This is the same for adding a Tag. 
-
-

docs/docs/changelog/v0.4.2.md

@@ -1,34 +0,0 @@
-# v0.4.2
-
-**App Version: v0.4.2**
-
-**Database Version: v0.4.0**
-
-!!! error "Breaking Changes"
-    1. With a recent refactor some users been experiencing issues with an environmental variable not being set correct. If you are experiencing issues, please provide your comments [Here](https://github.com/mealie-recipes/mealie/issues/281).
-
-    2. If you are a developer, you may experience issues with development as a new environmental variable has been introduced. Setting `PRODUCTION=false` will allow you to develop as normal.
-
-## Bug Fixes
-- Fixed Initialization script (v0.4.1a Hot Fix) - Closes #274
-- Fixed nested list error on recipe scrape - Closes #306
-- Fixed ingredient checkboxes - Closes #304
-- Removed link on recent - Closes #297
-- Categories sidebar is auto generated if no pages are created - Closes #291
-- Fix tag issues on creating custom pages - Closes #290
-- Validate paths on export - Closes #275
-- Walk Nextcloud import directory - Closes #254
-
-## General Improvements
-- Improved Nextcloud Migration. Mealie will now walk the directories in a zip file looking for directories that match the pattern of a Nextcloud Recipe. Closes #254
-    - Rewrite Keywords to Tag Fields
-    - Rewrite url to orgURL
-- Improved Chowdown Migration
-- Migration report is now similar to the Backup report
-- Tags/Categories are now title cased on import "dinner" -> "Dinner"
-- Depreciate `ENV` variable to `PRODUCTION`
-- Set `PRODUCTION` env variable to default to true
-- Unify Logger across the backend
-- mealie.log and last_recipe.json are now downloadable from the frontend from the /admin/about
-- New download schema where you request a token and then use that token to hit a single endpoint to download a file. This is a notable change if you are using the API to download backups. 
-- Recipe images can now be added directly from a URL - [See #117 for details](https://github.com/mealie-recipes/mealie/issues/117)

docs/docs/changelog/v0.4.3.md

@@ -1,14 +0,0 @@
-# v0.4.3
-
-**App Version: v0.4.3**
-
-**Database Version: v0.4.0**
-
-## Bug Fixes
-- Fix Upload error for Migrations
-- Fixes #315 - Cannot select another language
-- Fixes #314 - case-sensitive emails
-- Fixes #312 - Profile Image Reload
-
-## Improvements
-- New TOKEN_TIME and DEFAULT_EMAIL env variables

docs/docs/changelog/v0.5.0.md

@@ -1,129 +0,0 @@
-# v0.5.0 Too Many Changes! 
-
-**App Version: v0.5.0**
-
-**Database Version: v0.5.0**
-
-## Breaking Changes
-
-!!! error "Breaking Changes"
-
-    #### Database
-    Database version has been bumped from v0.4.x -> v0.5.0. You will need to export and import your data. Moving forward, we will be using database migrations (BETA) to do this automatically. Note that you still must backup your data. If you don't, it's entirely possible something may go wrong and you could lose your data on upgrade. 
-
-    #### Image Directory
-    the /data/img directory has been depreciated. All images are now stored in the /recipes/{slug}/image directory. Images should be migrated automatically, but you may experience issues related to this change. 
-
-    #### API Usage
-    If you have been using the API directly, many of the routes and status codes have changed. You may experience issues with directly consuming the API.
-
-    #### Arm/v7 Support
-    Mealie will no longer build in CI/CD due to a issue with the rust compiler on 32 bit devices. You can reference [this issue on the matrix-org/synapse](https://github.com/matrix-org/synapse/issues/9403) Github page that are facing a similar issue. You may still be able to build the docker image you-self. 
-
-!!! warning "Potential Data Loss"
-    With this release comes a major rework of how files are stored on disk and where things belong. Migration of files should be done automatically. We have tested extensively with many different backups and user bases and have found that no one experienced data-loss. HOWEVER, with all the major changes that have occurred, it is vital that to prevent any data-loss you must create a backup and store that backup outside of your mealie instance. If you do not do this, you may lose your data. 
-
-## Bug Fixes
-- Fixed #25 - Allow changing rating without going into edit
-- Fixed #475 - trim whitespace on login
-- Fixes #435 - Better Email Regex
-- Fixed #428 - Meal Planner now works on iOS devices
-- Fixed #419 - Typos
-- Fixed #418 - You can now "export" shopping lists
-- Fixed #356 - Shopping List items are now grouped
-- Fixed #329 - Fixed profile image not loading
-- Fixed #461 - Proper JSON serialization on webhooks
-- Fixed #332 - Language settings are saved for one browser
-- Fixes #281 - Slow Handling of Large Sets of Recipes
-- Fixed #356 - Shopping lists generate duplicate items
-- Fixed #271 - Slow handling of larger data sets
-- Fixed #472, #469, #458, #456 - Improve Recipe Parser
-
-## Features and Improvements
-
-### Highlights
-- Recipe Parser
-  - Recipes can now be imported with a bookmarklet!
-  - Significant improvement in supported sites with the new [Recipe Scraper Library](https://github.com/hhursev/recipe-scrapers)
-  - UI Debugging now available at `/recipes/debugger`
-  - Better error messages on failure
-  - ⚠️ last_recipe.json is now depreciated
-- Beta Support for Postgres! 🎉 See the getting started page for details
-- Recipe Features
-    - New button bar for editors with improved accessibility and performance
-    - Step Sections now supported
-    - Recipe Assets
-    - Add Asset image to recipe step
-    - Additional View Settings. 
-    - Better print support
-- New Toolbox Page!
-    - Bulk assign categories and tags by keyword search
-    - Title case all Categories or Tags with 1 click
-    - Create/Rename/Delete Operations for Tags/Categories
-    - Remove Unused Categories or Tags with 1 click
-- Recipe Cards now have a menu button for quick actions!
-    - Edit
-    - Delete
-    - Integrated Share with supported OS/Browsers
-    - Print
-- New Profile Dashboard!
-    - Edit Your Profile
-    - Create/Edit Themes
-    - View other users in your Group
-    - See what's for dinner
-    - Manage Long Live API Tokens (New)
-- New Admin Dashboard! 🎉
-    - Now you can get some insight on your application with application statistics and events.
-    - See uncategorized/untagged recipes and organize them!
-    - Backup/Restore right from your dashboard
-    - See server side events. Now you can know who deleted your favorite recipe! 
-- New Event Notifications through the Apprise Library
-    - Get notified when specific server side events occur
-
-### Meal Planner
-- Multiple Recipes per day
-- Supports meals without recipes (Enter title and description)
-- Generate share-link from created meal-planners
-- Shopping lists can be directly generated from the meal plan
-
-### General
-- User can now favorite recipes
-- New 'Dark' Color Theme Packaged with Mealie
-- Updated Recipe Card Sections Toolbar
-    - New Sort Options (They work this time!) 
-        - Alphabetical
-        - Rating
-        - Created Date
-        - Updated Date
-        - Shuffle (Random Sort)
-    - New 'Random' Recipe button on recipe sections. Random recipes are selected from the filtered results below. For example, on the "Cakes" category page, you will only get recipes in the "Cakes" category. 
-- Rating can be updated without entering the editor - Closes #25
-- Updated recipe editor styles and moved notes to below the steps. 
-- Redesigned search bar
-- 'Dinner this week' shows a warning when no meal is planned yet
-- 'Dinner today' shows a warning when no meal is planned yet
-- More localization
-- Start date for Week is now selectable
-- Languages are now managed through Crowdin
-- Application Bar was Rewritten
-    - Sidebar can now be toggled everywhere. 
-    - New and improved mobile friendly bottom bar
-    - Improved styling for search bar in desktop
-    - Improved search layout on mobile
-- Profile image now shown on all sidebars
-- Switched from Flash Messages to Snackbar (Removed dependency)
-
-### Performance
-- Images are now served up by the Caddy increase performance and offloading some loads from the API server
-- Requesting all recipes from the server has been rewritten to refresh less often and manage client side data better.
-- All images are now converted to .webp for better compression
-
-### Behind the Scenes
-- The database layer has been added for future recipe scaling. 
-- Black and Flake8 now run as CI/CD checks
-- New debian based docker image
-- Unified Sidebar Components
-- Refactor UI components to fit Vue best practices (WIP)
-- The API returns more consistent status codes
-- The API returns error code instead of error text when appropriate 
-    - ⚠️ May cause side-effects if you were directly consuming the API

docs/docs/changelog/v0.5.1.md

@@ -1,11 +0,0 @@
-# v0.5.1
-
-**App Version: v0.5.1**
-
-**Database Version: v0.5.0**
-
-
-## Bug Fixes
-- Fixed #538 - Missing Ingredients on Editor
-- Fixed error on webhooks for new groups
-- Fixed various icons references

docs/docs/changelog/v0.5.2.md

@@ -1,65 +0,0 @@
-# v0.5.2 - DRAFT
-
-**App Version: v0.5.2**
-
-**Database Version: v0.5.0**
-
-## Bug Fixes
-- Fixed #617 - Section behavior when adding a step
-- Fixed #615 - Recipe Settings are not available when creating new recipe
-- Fixed #625 - API of today's image returns strange characters
-- Fixed [#590](https://github.com/mealie-recipes/mealie/issues/590) - Duplicate Events when using Gunicorn Workers
-
-## Features and Improvements
-
-### General
-- Recipe Instructions now collapse when checked
-- Default recipe settings can be set through ENV variables
-- Recipe Ingredient lists can now container ingredient sections. 
-- You can now download and upload individual recipes
-
-
-### Localization
-
-Huge thanks to [@sephrat](https://github.com/sephrat) for all his work on the project. He's very consistent in his contributions to the project and nearly every release has had some of his code in it! Here's some highlights from this release
-
-  - Lazy Load Translations (Huge Performance Increase!)
-  - Tons of localization additions all around the site.
-  - All of the work that goes into managing and making Crowdin a great feature the application
-
-#### Here a list of contributors on Crowding who make Mealie possible in different locals
-
-| Name                         | Languages          | Translated (Words) | Target Words |
-| ---------------------------- | ------------------ | :----------------: | :----------: |
-| retmas-gh                    | Polish             |        550         |     625      |
-| startos                      | Italian            |        310         |     322      |
-| CMBoii                       | Spanish            |        256         |     291      |
-| sephrat                      | French             |        255         |     296      |
-| Daniel Tildeman (tildeman)   | Swedish            |        233         |     228      |
-| Rourke                       | Dutch              |        216         |     214      |
-| Andreas Waschinski (Wascha)  | German             |        207         |     202      |
-| wengtad                      | Chinese Simplified |        176         |     343      |
-| Matthias Borremans (MrBorri) | Dutch              |         96         |      89      |
-| Adam Syndoman (pypckompsite) | Polish             |         68         |      65      |
-| JonasSchubert                | German             |         22         |      23      |
-| ThrawnJL                     | Danish             |         7          |      7       |
-| NicholasBrody                | Dutch              |         7          |      7       |
-| Giel Janssens (gieljnssns)   | Dutch              |         4          |      4       |
-| kentora                      | Danish             |         3          |      2       |
-
-
-
-### Docker 
-
-#### Huge thanks to [@wengtad](https://github.com/wengtad) for all his work on improving the deployment with docker. 
-
-  - Optimize Docker Dev Size (Frontend: from ~1.52GB to ~429MB | API: from ~657MB to ~380MB)
-  - Optimize Docker Prod Size (from ~542MB to ~373MB)
-  - Add Gunicorn
-  - Add Gunicorn and Webworkers to Dockerfile #550
-  - Add Docs for Gunicorn
-  - Add PUID/PGID to Docker. Fixes Initialization scripts fail to run when not executing as root user inside container #350,
-  - Not able to run correctly in docker if user permissions are specified #429
-  - Merge Dockerfile.dev into Dockerfile (dev shared same base together with prod)
-  - Add Docs for PUID/PGID
-  - Add Docker healthcheck (for this is not necessary, I could remove if you want)

docs/docs/changelog/v1.0.0.md

@@ -1,178 +0,0 @@
-## v1.0.0b - 2022-05-22
-
-- Bump Dependencies
-    - Recipe Scrapers to 13.28
-    - Jinja2 to 3.1.2
-    - FastAPI to 0.78.0
-
-- Recipe Ingredient Editor
-    - [#1140](https://github.com/mealie-recipes/mealie/issues/1140) - Error in processing the quantity of ingredients #1140 - UI Now prevents entering not-allowed characters in quantity field
-    - UI now allows no value to be set in addition to a zero (0) value.
-    - [#1237](https://github.com/mealie-recipes/mealie/issues/1237) - UI: Saving a 0 quantity ingredient displays 0 until the page is refreshed #1237 - UI Now properly reacts to changes in the quantity field.
-
-- Fix Mealie v0.5.x migration issue [#1183](https://github.com/mealie-recipes/mealie/issues/1183)
-- Consolidated Frontend Types thanks to [@PFischbeck](https://github.com/Fischbeck)
-- Added support for SSL/No Auth Email [@nkringle](https://github.com/nkringle)
-- [Implement several notifications for server actions ](https://github.com/mealie-recipes/mealie/pull/1234)[@miroito](https://github.com/Miroito)
-- Fix display issue for shared recipe rendering on server [@PFischbeck](https://github.com/Fischbeck)
-
-## v1.0.0b - 2022-05-09
-
-- Change MIT license to AGPLv3
-
-## v1.0.0b - 2022-05-08
-
-- Rewrote the registration flow for new users.
-- Added support for seed data at anytime through the user interface.
-- Improved security for sanitizing HTML inputs for user input.
-- Added support for importing keywords as tags during scraping - [@miroito](https://github.com/Miroito)
-- Changed default recipe settings to "disable_amount=True" for new groups.
-- Add support for merging food, and units.
-- Allow tags, category, and tool creation - [@miroito](https://github.com/Miroito)
-- Added additional and more comprehensive filter options for cookbooks
-- Fixed bookmarklets error
-
-## v1.0.0b - 2022-03-29
-
-- Mealie now stores the original text from parsed ingredients, with the ability to peak at the original text from a recipe. [@miroito](https://github.com/Miroito)
-- Added some management / utility functions for administrators to manage data and cleanup artifacts from the file system.
-- Fix clear url action in recipe creation [#1101](https://github.com/mealie-recipes/mealie/pull/1101) [@miroito](https://github.com/Miroito)
-- Add group statistics calculations and data storage measurements
-    - No hard limits are currently imposed on groups - though this may be implemented in the future.
-
-## v1.0.0b - 2022-03-25
-
-- Mealie now packages the last git commit as the build ID
-- Admin section now has a "Maintenance" page where you can check some health metrics like data directory size, logs file size, and if there are some non compliant directories or images. You can also perform clean-up operations to resolve some of these issues.
-- Dropped 2 dependencies and moved to using our own base model within the project
-- Removed lots of dead backup code
-- Recipe names will now be auto-incremented when a conflict is found. So if you're adding a recipe named "Tomato Soup" and that recipe name already exists in your database one will be created with the name "Tomato Soup (1)". Currently this is done in a loop until a suitable name is found, however it will error out after 10 attempts so it's best to find a more descriptive name for your recipe.
-- Fixed broken PWA where it wouldn't render any content
-- Added database connection retry loop to ensure that the database is available prior to starting
-- Reorganized group routes to be more consistent with the rest of the application
-
-## v1.0.0b Beta Release!
-
-!!! error "Breaking Changes"
-    As you may have guessed, this release comes with some breaking changes. If you are/were consuming the API you will need to validate all endpoints as nearly all of them have changed.
-
-    To import your data into Mealie v1 from the most recent previous release, you'll need to export and import your data using the built in method. **Note that only your recipes will be usable in the migration**.
-
-### ✨ What's New (What isn't?!?!)
-
-#### 🥳 General
-
-- Mealie will by default only be accessible to users. Future plans are to create spaces for non-users to access a specific group.
-- Mealie has gone through a big redesign and has tried to standardize it's look a feel a bit more across the board.
-- User/Group settings are now completely separated from the Administration page.
-- All settings and configurations pages now have some sort of self-documenting help text. Additional text or descriptions are welcome from PRs
-- New experimental banner for the site to give users a sense of what features are still "in development" and provide a link to a github issue that provides additional context.
-- Groups now offer full multi-tenant support so you can all groups have their own set of data.
-
-##### ⚙️ Site Settings Page
-
-- Site Settings has been completely revamped. All site-wide settings at defined on the server as ENV variables. The site settings page now only shows you the non-secret values for reference. It also has some helpers to let you know if something isn't configured correctly.
-    - Server Side Bare URL will let you know if the BASE_URL env variable has been set
-    - Secure Site let's you know if you're serving via HTTPS or accessing by localhost. Accessing without a secure site will render some of the features unusable.
-    - Email Configuration Status will let you know if all the email settings have been provided and offer a way to send test emails.
-
-#### 👨‍👩‍👧‍👦 Users and Groups
-
-- All members of a group can generate invitation tokens for other users to join their group
-- Users now a have "Advanced" setting to enable/disable features like Webhooks and API tokens. This will also apply to future features that are deemed as advanced.
-- "Pages" have been dropped in favor of Cookbooks which are now group specific so each group can have it's own set of cookbooks
-- Default recipe settings can now be set by the group instead of environmental variables.
-- Password reset via email
-- Invitation to group by email
-- Manage group member permissions
-
-#### 📦 Data Migrations
-
-- Migrations have been moved from the Admin Page to a Group Migration page. Migrations from applications (or previous versions of Mealie) can now be imported into Mealie via the Group Migration pages where all recipes will be imported into the group.
-- **Supported Migrations**
-    - Mealie Pre v1.0.0
-    - Nextcloud Recipes
-    - Chowdown
-
-#### 🛒 Shopping Lists
-
-- Shopping Lists has been completely revamped to be more flexible and user friendly.
-    - Add recipe ingredients to a shopping list
-    - Manually add item/ingredient to shopping list
-    - Copy as markdown or plain text
-    - Sort by food/item Labels
-    - Checked items are now hidden
-    - Uncheck all Items
-    - Delete all checked items
-
-#### 📢 Apprise Integration
-
-- Server based Apprise notifications have been deprecated. An effort has been made to improve logging overall in the application and make it easier to monitor/debug through the logs.
-- The Apprise integration has been updated to the latest version and is now used asynchronously.
-- Notifiers now support a wider variety of events.
-- Notifiers can now be managed by-group instead of by the server.
-
-#### 🗓 Meal Plans
-
-- Meal plans have been completely redesigned to use a calendar approach so you'll be able to see what meals you have planned in a more traditional view
-- Drag and Drop meals between days
-- Add Recipes or Notes to a specific day
-- New context menu action for recipes to add a recipe to a specific day on the meal-plan
-- New rule based meal plan generator/selector. You can now create rules to restrict the addition of recipes for specific days or meal types (breakfast, lunch, dinner, side). You can also create rules that match against "all" days or "all" meal types to create global rules based around tags and categories. This gives you the most flexibility in creating meal plans.
-
-#### 🥙 Recipes
-
-##### 🔍 Search
-
-- Search now includes the ability to fuzzy search ingredients
-- Search now includes an additional filter for "Foods" which will filter (Include/Exclude) matches based on your selection.
-
-##### 🍴 Recipe General
-
-- Recipe Pages now implement a screen lock on supported devices to keep the screen from going to sleep.
-- Recipes are now only viewable by group members
-- Recipes can be shared with share links
-- Shared recipes can now render previews for the recipe on sites like Twitter, Facebook, and Discord.
-- Recipes now have a `tools` attribute that contains a list of required tools/equipment for the recipe. Tools can be set with a state to determine if you have that tool or not. If it's marked as on hand it will show checked by default.
-- Recipe Extras now only show when advanced mode is toggled on
-- You can now import multiple URLs at a time pre-tagged using the bulk importer. This task runs in the background so no need to wait for it to finish.
-- Foods/Units for Ingredients are now supported (toggle inside your recipe settings)
-- Common Food and Units come pre-packaged with Mealie
-- Landscape and Portrait views are now available
-- Users with the advanced flag turned on will now be able to manage recipe data in bulk and perform the following actions:
-    - Set Categories
-    - Set Tags
-    - Delete Recipes
-    - Export Recipes
-- Recipes now have a `/cook` page for a simple view of the recipe where you can click through each step of a recipe and it's associated ingredients.
-- The Bulk Importer has received many additional upgrades.
-    - Trim Whitespace: automatically removes leading and trailing whitespace
-    - Trim Prefix: Removes the first character of each line. Useful for when you paste in a list of ingredients or instructions that have 1. or 2. in front of them.
-    - Split By Numbered Line: Attempts to split a paragraph into multiple lines based on the patterns matching '1.', '1:' or '1)'.
-
-##### 🍞 Recipe Ingredients
-
-- Recipe ingredients can now be scaled when the food/unit is defined
-- Recipe ingredients can now be copied as markdown lists
-    - example `- [ ] 1 cup of flour`
-- You can now use Natural Language Processing (NLP) to process ingredients and attempt to parse them into amounts, units, and foods. There is an additional "Brute Force" processor that can be used as pattern matching parser to try and determine ingredients. **Note** if you are processing a Non-English language you will have terrible results with the NLP and will likely need to use the Bruce Force processor.
-
-##### 📜 Recipe Instructions
-
-- Can now be merged with the above step automatically through the action menu
-- Recipe Ingredients can be linked directly to recipe instructions for improved display
-    - There is an option in the linking dialog to automatically link ingredients. This works by using a key-word matching algorithm to find the ingredients. It's not perfect so you'll need to verify the links after use, additionally you will find that it doesn't work for non-english languages.
-- Recipe Instructions now have a preview tab to show the rendered markdown before saving.
-
-#### ⚠️ Other things to know...
-
-- Themes have been deprecated for specific users. You can still set specific themes for your site through ENV variables. This approach should yield much better results for performance and some weirdness users have experienced.
-- If you've experienced slowness in the past, you may notice a significant improvement in the "All Recipes" and "Search" pages, or wherever large payloads of recipes are being displayed. This is due to not validating responses from the database, as such if you are consuming these API's you may get extra values that are unexpected.
-
-#### 👨‍💻 Backend/Development Goodies
-
-- Codebase is significantly more organized both Frontend and Backend
-- We've moved to Nuxt for SSR and Typescript for better type safety and less bugs 🎉
-- Backend now using a Class based architecture to maximize code reuse
-- Tons of performance improvements across the board
-- Significant work was done by [@PFischbeck](https://github.com/PFischbeck) to improve type safety on the frontend server and fix many type related errors/bugs!

docs/docs/changelog/v1.0.0beta-2.md

@@ -1,29 +0,0 @@
-### Bug Fixes
-
-- Bump isomorphic-dompurify from 0.18.0 to 0.19.0 in /frontend ([#1257](https://github.com/mealie-recipes/mealie/issues/1257))
-- Bump @nuxtjs/auth-next in /frontend ([#1265](https://github.com/mealie-recipes/mealie/issues/1265))
-- Bad dev dependency ([#1281](https://github.com/mealie-recipes/mealie/issues/1281))
-- Add touch support for mealplanner delete ([#1298](https://github.com/mealie-recipes/mealie/issues/1298))
-
-### Documentation
-
-- Add references for VSCode dev containers ([#1299](https://github.com/mealie-recipes/mealie/issues/1299))
-- Docker-compose.dev.yml is currently not functional ([#1300](https://github.com/mealie-recipes/mealie/issues/1300))
-
-### Features
-
-- Add reports to bulk recipe import (url) ([#1294](https://github.com/mealie-recipes/mealie/issues/1294))
-- Rewrite print implementation to support new ing ([#1305](https://github.com/mealie-recipes/mealie/issues/1305))
-
-### Miscellaneous Tasks
-
-- Github stalebot changes ([#1271](https://github.com/mealie-recipes/mealie/issues/1271))
-- Bump eslint-plugin-nuxt in /frontend ([#1258](https://github.com/mealie-recipes/mealie/issues/1258))
-- Bump @vue/runtime-dom in /frontend ([#1259](https://github.com/mealie-recipes/mealie/issues/1259))
-- Bump nuxt-vite from 0.1.3 to 0.3.5 in /frontend ([#1260](https://github.com/mealie-recipes/mealie/issues/1260))
-- Bump vue2-script-setup-transform in /frontend ([#1263](https://github.com/mealie-recipes/mealie/issues/1263))
-- Update dev dependencies ([#1282](https://github.com/mealie-recipes/mealie/issues/1282))
-
-### Refactor
-
-- Split up recipe create page ([#1283](https://github.com/mealie-recipes/mealie/issues/1283))

docs/docs/changelog/v1.0.0beta-3.md

@@ -1,36 +0,0 @@
-### Bug Fixes
-
-- Update issue links in v1.0.0beta-2 changelog ([#1312](https://github.com/mealie-recipes/mealie/issues/1312))
-- Bad import path ([#1313](https://github.com/mealie-recipes/mealie/issues/1313))
-- Printer page refs ([#1314](https://github.com/mealie-recipes/mealie/issues/1314))
-- Consolidate stores to fix mismatched state
-- Bump @vue/composition-api from 1.6.1 to 1.6.2 in /frontend ([#1275](https://github.com/mealie-recipes/mealie/issues/1275))
-- Shopping list label editor  ([#1333](https://github.com/mealie-recipes/mealie/issues/1333))
-
-### Features
-
-- Default unit fractions to True
-- Add unit abbreviation support ([#1332](https://github.com/mealie-recipes/mealie/issues/1332))
-- Attached images by drag and drop for recipe steps ([#1341](https://github.com/mealie-recipes/mealie/issues/1341))
-
-### Docs
-
-- Render homepage social media link images at 32x32 size ([#1310](https://github.com/mealie-recipes/mealie/issues/1310))
-
-### Miscellaneous Tasks
-
-- Init git-cliff config
-- Bump @types/sortablejs in /frontend ([#1287](https://github.com/mealie-recipes/mealie/issues/1287))
-- Bump @babel/eslint-parser in /frontend ([#1290](https://github.com/mealie-recipes/mealie/issues/1290))
-
-### Refactor
-
-- Unify recipe-organizer components ([#1340](https://github.com/mealie-recipes/mealie/issues/1340))
-
-### Security
-
-- Delay server response whenever username is non existing ([#1338](https://github.com/mealie-recipes/mealie/issues/1338))
-
-### Wip
-
-- Pagination-repository ([#1316](https://github.com/mealie-recipes/mealie/issues/1316))

docs/docs/changelog/v1.0.0beta-4.md

@@ -1,126 +0,0 @@
-### Security
-
-#### v1.0.0beta-3 and Under - Recipe Scraper: Server Side Request Forgery Lead To Denial Of Service
-
-!!! error "CWE-918: Server-Side Request Forgery (SSRF)"
-    In this case if a attacker try to load a huge file then server will try to load the file and eventually server use its all memory which will dos the server
-
-##### Mitigation
-
-HTML is now scraped via a Stream and canceled after a 15 second timeout to prevent arbitrary data from being loaded into the server.
-
-#### v1.0.0beta-3 and Under - Recipe Assets: Remote Code Execution
-
-!!! error "CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine"
-    As a low privileged user, Create a new recipe and click on the "+" to add a New Asset.
-    Select a file, then proxy the request that will create the asset.
-
-    Since mealie/routes/recipe/recipe_crud_routes.py:306 is calling slugify on the name POST parameter, we use $ which slugify() will remove completely.
-
-    Since mealie/routes/recipe/recipe_crud_routes.py:306 is concatenating raw user input from the extension POST parameter into the variable file_name, which ultimately gets used when writing to disk, we can use a directory traversal attack in the extension (e.g. ./../../../tmp/pwn.txt) to write the file to arbitrary location on the server.
-
-    As an attacker, now that we have a strong attack primitive, we can start getting creative to get RCE. Since the files were being created by root, we could add an entry to /etc/passwd, create a crontab, etc. but since there was templating functionality in the application that peaked my interest. The PoC in the HTTP request above creates a Jinja2 template at /app/data/template/pwn.html. Since Jinja2 templates execute Python code when rendered, all we have to do now to get code execution is render the malicious template. This was easy enough.
-
-##### Mitigation
-
-We've added proper path sanitization to ensure that the user is not allowed to write to arbitrary locations on the server.
-
-!!! warning "Breaking Change Incoming"
-    As this has shown a significant area of exposure in the templates that Mealie was provided for exporting recipes, we'll be removing this feature in the next Beta release and will instead rely on the community to provide tooling around transforming recipes using templates. This will significantly limit the possible exposure of users injecting malicious templates into the application. The template functionality will be completely removed in the next beta release v1.0.0beta-5
-
-#### All version Markdown Editor: Cross Site Scripting
-
-!!! error "CWE-79: Cross-site Scripting (XSS) - Stored"
-    A low privilege user can insert malicious JavaScript code into the Recipe Instructions which will execute in another person's browser that visits the recipe.
-
-    `<img src=x onerror=alert(document.domain)>`
-
-##### Mitigation
-
-This issues is present on all pages that allow markdown input. This error has been mitigated by wrapping the 3rd Party Markdown component and using the `domPurify` library to strip out the dangerous HTML.
-
-#### v1.0.0beta-3 and Under - Image Scraper: Server-Side Request Forgery
-
-!!! error "CWE-918: Server-Side Request Forgery (SSRF)"
-    In the recipe edit page, is possible to upload an image directly or via an URL provided by the user. The function that handles the fetching and saving of the image via the URL doesn't have any URL verification, which allows to fetch internal services.
-
-    Furthermore, after the resource is fetch, there is no MIME type validation, which would ensure that the resource is indeed an image. After this, because there is no extension in the provided URL, the application will fallback to jpg, and original for the image name.
-
-    Then the result is saved to disk with the original.jpg name, that can be retrieved from the following URL: http://<domain>/api/media/recipes/<recipe-uid>/images/original.jpg. This file will contain the full response of the provided URL.
-
-    **Impact**
-
-    An attacker can get sensitive information of any internal-only services running. For example, if the application is hosted on Amazon Web Services (AWS) platform, its possible to fetch the AWS API endpoint, https://169.254.169.254, which returns API keys and other sensitive metadata.
-
-##### Mitigation
-
-Two actions were taken to reduce exposure to SSRF in this case.
-
-1. The application will not prevent requests being made to local resources by checking for localhost or 127.0.0.1 domain names.
-2. The mime-type of the response is now checked prior to writing to disk.
-
-If either of the above actions prevent the user from uploading images, the application will alert the user of what error occurred.
-
-### Bug Fixes
-
-- For erroneously-translated datetime config ([#1362](https://github.com/mealie-recipes/mealie/issues/1362))
-- Fixed text color on RecipeCard in RecipePrintView and implemented ingredient sections ([#1351](https://github.com/mealie-recipes/mealie/issues/1351))
-- Ingredient sections lost after parsing ([#1368](https://github.com/mealie-recipes/mealie/issues/1368))
-- Increased float rounding precision for CRF parser ([#1369](https://github.com/mealie-recipes/mealie/issues/1369))
-- Infinite scroll bug on all recipes page ([#1393](https://github.com/mealie-recipes/mealie/issues/1393))
-- Fast fail of bulk importer ([#1394](https://github.com/mealie-recipes/mealie/issues/1394))
-- Bump @mdi/js from 5.9.55 to 6.7.96 in /frontend ([#1279](https://github.com/mealie-recipes/mealie/issues/1279))
-- Bump @nuxtjs/i18n from 7.0.3 to 7.2.2 in /frontend ([#1288](https://github.com/mealie-recipes/mealie/issues/1288))
-- Bump date-fns from 2.23.0 to 2.28.0 in /frontend ([#1293](https://github.com/mealie-recipes/mealie/issues/1293))
-- Bump fuse.js from 6.5.3 to 6.6.2 in /frontend ([#1325](https://github.com/mealie-recipes/mealie/issues/1325))
-- Bump core-js from 3.17.2 to 3.23.1 in /frontend ([#1383](https://github.com/mealie-recipes/mealie/issues/1383))
-- All-recipes page now sorts alphabetically ([#1405](https://github.com/mealie-recipes/mealie/issues/1405))
-- Sort recent recipes by created_at instead of date_added ([#1417](https://github.com/mealie-recipes/mealie/issues/1417))
-- Only show scaler when ingredients amounts enabled ([#1426](https://github.com/mealie-recipes/mealie/issues/1426))
-- Add missing types for API token deletion ([#1428](https://github.com/mealie-recipes/mealie/issues/1428))
-- Entry nutrition checker ([#1448](https://github.com/mealie-recipes/mealie/issues/1448))
-- Use == operator instead of is_ for sql queries ([#1453](https://github.com/mealie-recipes/mealie/issues/1453))
-- Use `mtime` instead of `ctime` for backup dates  ([#1461](https://github.com/mealie-recipes/mealie/issues/1461))
-- Mealplan pagination ([#1464](https://github.com/mealie-recipes/mealie/issues/1464))
-- Properly use pagination for group event notifies ([#1512](https://github.com/mealie-recipes/mealie/pull/1512))
-
-### Documentation
-
-- Add go bulk import example ([#1388](https://github.com/mealie-recipes/mealie/issues/1388))
-- Fix old link
-- Pagination and filtering, and fixed a few broken links ([#1488](https://github.com/mealie-recipes/mealie/issues/1488))
-
-### Features
-
-- Toggle display of ingredient references in recipe instructions ([#1268](https://github.com/mealie-recipes/mealie/issues/1268))
-- Add custom scaling option ([#1345](https://github.com/mealie-recipes/mealie/issues/1345))
-- Implemented "order by" API parameters for recipe, food, and unit queries ([#1356](https://github.com/mealie-recipes/mealie/issues/1356))
-- Implement user favorites page ([#1376](https://github.com/mealie-recipes/mealie/issues/1376))
-- Extend Apprise JSON notification functionality with programmatic data ([#1355](https://github.com/mealie-recipes/mealie/issues/1355))
-- Mealplan-webhooks ([#1403](https://github.com/mealie-recipes/mealie/issues/1403))
-- Added "last-modified" header to supported record types ([#1379](https://github.com/mealie-recipes/mealie/issues/1379))
-- Re-write get all routes to use pagination ([#1424](https://github.com/mealie-recipes/mealie/issues/1424))
-- Advanced filtering API ([#1468](https://github.com/mealie-recipes/mealie/issues/1468))
-- Restore frontend sorting for all recipes ([#1497](https://github.com/mealie-recipes/mealie/issues/1497))
-- Implemented local storage for sorting and dynamic sort icons on the new recipe sort card ([1506](https://github.com/mealie-recipes/mealie/pull/1506))
-- create new foods and units from their Data Management pages ([#1511](https://github.com/mealie-recipes/mealie/pull/1511))
-
-### Miscellaneous Tasks
-
-- Bump dev deps ([#1418](https://github.com/mealie-recipes/mealie/issues/1418))
-- Bump @vue/runtime-dom in /frontend ([#1423](https://github.com/mealie-recipes/mealie/issues/1423))
-- Backend page_all route cleanup ([#1483](https://github.com/mealie-recipes/mealie/issues/1483))
-
-### Refactor
-
-- Remove depreciated repo call ([#1370](https://github.com/mealie-recipes/mealie/issues/1370))
-
-### Hotfix
-
-- Tame typescript beast
-
-### UI
-
-- Improve parser ui text display ([#1437](https://github.com/mealie-recipes/mealie/issues/1437))
-
-<!-- generated by git-cliff -->

docs/docs/changelog/v1.0.0beta-5.md

@@ -1,3 +0,0 @@
-### NOTICE:
-
-Release changelogs are now published on github releases. This file is kept for historical purposes.

docs/docs/contributors/developers-guide/database-changes.md

@@ -0,0 +1,85 @@
+# Development: Database Changes
+
+This document is open to improvement; please share any insights you have/develop.
+
+## Overview
+
+When modifying the database, you will most likely need to change the files under `/mealie/db/models/`.
+How exactly you need to modify it is of course highly contextual to the change you're making.
+
+## Using Alembic to generate upgrade script
+
+In your dev container you can run something like (change the message) `task py:migrate -- "Add creation tag to group preferences"` to have Alembic generate an upgrade script for you.
+
+The script Alembic generates, will be limited! (Perhaps there's a way to resolve that? Haven't looked into it yet)
+For example, Alembic generated a script _similar_ to this (it has been modified already to have accurate foreign key names, for instance):
+
+```Python
+"""Add creation tag to group preferences
+
+Revision ID: 0ea6eb8eaa44
+Revises: ba1e4a6cfe99
+Create Date: 2024-01-04 12:40:03.062671
+
+"""
+import sqlalchemy as sa
+
+import mealie.db.migration_types
+from alembic import op
+
+# revision identifiers, used by Alembic.
+revision = "0ea6eb8eaa44"
+down_revision = "ba1e4a6cfe99"
+branch_labels = None
+depends_on = None
+
+
+def upgrade():
+    ### commands auto generated by Alembic - please adjust! ###
+    op.add_column(
+        "group_preferences", sa.Column("recipe_creation_tag", mealie.db.migration_types.GUID(), nullable=True)
+    )
+    op.create_foreign_key("fk_groupprefs_tags", "group_preferences", "tags", ["recipe_creation_tag"], ["id"])
+    ### end Alembic commands ###
+
+
+def downgrade():
+    ### commands auto generated by Alembic - please adjust! ###
+    op.drop_constraint("fk_groupprefs_tags", "group_preferences", type_="foreignkey")
+    op.drop_column("group_preferences", "recipe_creation_tag")
+    ### end Alembic commands ###
+```
+
+But when trying to actually use that upgrade script, it becomes clear that our SQLite database doesn't like them. The minor modification needed looks like:
+
+```Python
+"""Add creation tag to group preferences
+
+Revision ID: 0ea6eb8eaa44
+Revises: ba1e4a6cfe99
+Create Date: 2024-01-04 12:40:03.062671
+
+"""
+import sqlalchemy as sa
+
+import mealie.db.migration_types
+from alembic import op
+
+# revision identifiers, used by Alembic.
+revision = "0ea6eb8eaa44"
+down_revision = "ba1e4a6cfe99"
+branch_labels = None
+depends_on = None
+
+
+def upgrade():
+    with op.batch_alter_table("group_preferences", schema=None) as batch_op:
+        batch_op.add_column(sa.Column("recipe_creation_tag", mealie.db.migration_types.GUID(), nullable=True))
+        batch_op.create_foreign_key("fk_groupprefs_tags", "tags", ["recipe_creation_tag"], ["id"])
+
+
+def downgrade():
+    with op.batch_alter_table("group_preferences", schema=None) as batch_op:
+        batch_op.drop_constraint("fk_groupprefs_tags", type_="foreignkey")
+        batch_op.drop_column("recipe_creation_tag")
+```

docs/docs/contributors/guides/ingredient-parser.md

@@ -1,20 +1,19 @@
 # Improving the Ingredient Parser
 
-Mealie uses Conditional Random Fields (CRFs) for parsing and processing ingredients. The model used for ingredients is based off a data set of over 100,000 ingredients from a dataset compiled by the New York Times. I believe that the model used is sufficient enough to handle most of the ingredients, therefore, more data to train the model won't necessarily help improve the model. 
+Mealie uses Conditional Random Fields (CRFs) for parsing and processing ingredients. The model used for ingredients is based off a data set of over 100,000 ingredients from a dataset compiled by the New York Times. I believe that the model used is sufficient enough to handle most of the ingredients, therefore, more data to train the model won't necessarily help improve the model.
 
 ## Improving The CRF Parser
 
-To improve results with the model, you'll likely need to focus on improving the tokenization and parsing of the original string to aid the model in determine what the ingredient is. Data science is not my forte, but I have done some tokenization to improve the model. You can find that code under `/mealie/services/parser_services/crfpp` along with some other utility functions to aid in the tokenization and processing of ingredient strings. 
+To improve results with the model, you'll likely need to focus on improving the tokenization and parsing of the original string to aid the model in determine what the ingredient is. Data science is not my forte, but I have done some tokenization to improve the model. You can find that code under `/mealie/services/parser_services/crfpp` along with some other utility functions to aid in the tokenization and processing of ingredient strings.
 
 The best way to test on improving the parser is to register additional test cases in  `/mealie/tests/unit_tests/test_crfpp_parser.py` and run the test after making changes to the tokenizer. Note that the test cases DO NOT run in the CI environment, therefore you will need to have CRF++ installed on your machine. If you're using a Mac the easiest way to do this is through brew.
 
-When submitting a PR to improve the parser it is important to provide your test cases, the problem you were trying to solve, and the results of the changes you made. As the tests don't run in CI, not providing these details may delay your PR from being merged. 
+When submitting a PR to improve the parser it is important to provide your test cases, the problem you were trying to solve, and the results of the changes you made. As the tests don't run in CI, not providing these details may delay your PR from being merged.
 
 ## Alternative Parsers
-Alternatively, you can register a new parser by fulfilling the `ABCIngredientParser` interface. Satisfying this single method interface allows us to register additional parsing strategies at runtime and gives the user several options when trying to parse a recipe. 
+Alternatively, you can register a new parser by fulfilling the `ABCIngredientParser` interface. Satisfying this single method interface allows us to register additional parsing strategies at runtime and gives the user several options when trying to parse a recipe.
 
 
 ## Links
 - [Pretrained Model](https://github.com/mealie-recipes/mealie-nlp-model)
 - [CRF++ (Forked)](https://github.com/hay-kot/crfpp)
-

docs/docs/contributors/non-coders.md

@@ -9,8 +9,8 @@ We love your input! We want to make contributing to this project as easy and tra
 - Becoming a maintainer
 - Help translate to a new language or improve current translations
 
-[Remember to join the Discord and stay in touch with other developers working on the project](https://discord.gg/QuStdQGSGK)! 
+[Remember to join the Discord and stay in touch with other developers working on the project](https://discord.gg/QuStdQGSGK)!
 
-Additionally, you can buy me a coffee and support the project. When I get financial support it helps me know that there's real interest in the project and that it's worth the time to keep developing. 
+Additionally, you can buy me a coffee and support the project. When I get financial support it helps me know that there's real interest in the project and that it's worth the time to keep developing.
 
-<a href="https://www.buymeacoffee.com/haykot" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-green.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a>
+<a href="https://www.buymeacoffee.com/haykot" target="_blank"><img src="https://cdn.buymeacoffee.com/buttons/v2/default-green.png" alt="Buy Me A Coffee" style="height: 60px !important;width: 217px !important;" ></a>

docs/docs/documentation/community-guide/bulk-url-import.md

@@ -93,4 +93,3 @@ mealie_url="http://localhost:9000"
 token = authentication(mail, password, mealie_url)
 import_from_file(input_file, token, mealie_url)
 ```
-

docs/docs/documentation/community-guide/n8n-backup-automation.md

@@ -0,0 +1,80 @@
+# Automating Backups with n8n
+
+!!! info
+This guide was submitted by a community member. Find something wrong? Submit a PR to get it fixed!
+
+> [n8n](https://github.com/n8n-io/n8n) is a free and source-available fair-code licensed workflow automation tool. Alternative to Zapier or Make, allowing you to use a UI to create automated workflows.
+
+This example workflow:
+
+1. Backups Mealie every morning via an API call
+2. Deletes all but the last 7 backups
+
+> [!CAUTION]
+> This only automates the backup function, this does not backup your data to anywhere except your local instance. Please make sure you are backing up your data to an external source.
+
+---
+
+![screenshot](../../assets/img/n8n/n8n-mealie-backup.png)
+
+# Setup
+
+## Deploying n8n
+
+Follow the relevant guide in the [n8n Documentation](https://docs.n8n.io/)
+
+## Importing n8n workflow
+
+1. In n8n, add a new workflow
+2. In the top right hit the 3 dot menu and select 'Import from URL...'
+
+![screenshot](../../assets/img/n8n/n8n-workflow-import.png)
+
+3. Paste `https://github.com/mealie-recipes/mealie/blob/mealie-next/docs/docs/assets/other/n8n/n8n-mealie-backup.json` and click Import
+4. Click through the nodes and update the URLs for your environment
+
+## API Credentials
+
+#### Generate Mealie API Token
+
+1. Head to https://mealie.example.com/user/profile/api-tokens
+   > If you dont see this screen make sure that "Show advanced features" is checked under https://mealie.example.com/user/profile/edit
+2. Under token name, enter the name of the token i.e. 'n8n' and hit Generate
+3. Copy and keep this API Token somewhere safe, this is like your password!
+
+> You can use your normal user for this, but assuming you're an admin you could also choose to create a user named n8n and generate the API key against that user.
+
+#### Setup Credentials in n8n
+
+> [n8n Docs](https://docs.n8n.io/credentials/add-edit-credentials/)
+
+1. Create a new "Header Auth" Credential
+
+![screenshot](../../assets/img/n8n/n8n-cred-app.png)
+
+2. In the connection screen set - Name as `Authorization` - Value as `Bearer {INSERT MEALIE API KEY}`
+
+![screenshot](../../assets/img/n8n/n8n-cred-connection.png)
+
+3. In the workflow you created, for the "Run Backup", "Get All backups", and "Delete Oldies" nodes, update:
+   - Authentication to `Generic Credential Type`
+   - Generic Auth Type to `Header Auth`
+   - Header Auth to `Mealie API` or whatever you named your credentials
+
+![screenshot](../../assets/img/n8n/n8n-workflow-auth.png)
+
+## Notification Node
+
+> Please use error notifications of some kind. It's very easy to set and forget an automation, then have the worst happen and lose data.
+
+[ntfy](https://github.com/binwiederhier/ntfy) is a great open source, self-hostable tool for sending notifications.
+
+If you want to use ntfy, you will need to install it on your environment, or sign up for their service, and configure it with the webhook URL.
+
+If you want to use another notification service, you can create a new node in n8n that sends the notification using whatever method you like.
+
+- For example, if you want to send a push notification via [Pushover](https:/pushover.net/) you could create a new node that uses the Pushover API and sends the notification.
+- You can use the [Send Email](https://docs.n8n.io/integrations/builtincore-nodes/n8n-nodes-base.sendemail/) node in n8n as an example of how to create your own custom node.
+- You can send it off to InfluxDB, Slack, Discord etc. Go nuts.
+
+If you're using another method for backups we'd love to hear about it. Pop in [Discord](https://discord.gg/QuStdQGSGK) and say hi!

docs/docs/documentation/community-guide/swag.md

@@ -48,7 +48,7 @@ services:
     restart: unless-stopped
 ```
 
-Don't forget to change the <code>mydomain.duckns</code> into your personal domain and the <code>duckdnstoken</code> into your token and remove the brackets.
+Don't forget to change the <code>mydomain.duckdns</code> into your personal domain and the <code>duckdnstoken</code> into your token and remove the brackets.
 
 ## Step 3: Change the config files
 

docs/docs/documentation/getting-started/faq.md

@@ -2,14 +2,14 @@
 
 ## How do I enable "smart" ingredient handling?
 
-You might have noticed that scaling up a recipe or making a shopping list doesn't by default handle the ingredients in a way you might expect. Depending on your settings, scaling up might yield things like `2 1 cup broth` instead of `2 cup broth`. And making shopping lists from reciepes that have shared ingredients can yield multiple lines of the same ingredient. **But**, mealie has a mechanism to intelligently handle ingredients and make your day better. How?
+You might have noticed that scaling up a recipe or making a shopping list doesn't by default handle the ingredients in a way you might expect. Depending on your settings, scaling up might yield things like `2 1 cup broth` instead of `2 cup broth`. And, making shopping lists from recipes that have shared ingredients can yield multiple lines of the same ingredient. **But**, Mealie has a mechanism to intelligently handle ingredients and make your day better. How?
 ### Set up your Foods and Units
 Do the following just **once**. Doing this applies to your whole group, so be careful.
 
 1. Click on your name in the upper left corner to get to your settings
 2. In the bottom right, select `Manage Data`
 3. In the Management page, make sure that a little orange button says `Foods`
-4. If your Foods database is empty, click `Seed` and choose your language. You should end up with a list of foods. (Wait  bit for seeding to happen, and try not to seed more than once or you will have duplicates)
+4. If your Foods database is empty, click `Seed` and choose your language. You should end up with a list of foods. (Wait a bit for seeding to happen, and try not to seed more than once or you will have duplicates)
 5. Click the little orange `Foods` button and now choose `Units`.
 6. Click `Seed` and choose your language. You should end up with a list of units (e.g. `tablespoon`)
 
@@ -33,9 +33,9 @@ Do the following for each recipe you want to intelligently handle ingredients.
 
 Scaling up this recipe or adding it to a Shopping List will now smartly take care of ingredient amounts and duplicate combinations.
 
-## Is it Safe to Upgrade Mealie?
+## Is it safe to upgrade Mealie?
 
-Yes. If you are using the v1 branches (including beta), you can upgrade to the latest version of Mealie without performing a site Export/Restore. This process was required in previous versions of Mealie, however we've automated the database migration process to make it easier to upgrade. Not that if you were using the v0.5.x version, you CANNOT upgrade to the latest version automatically. You must follow the migration instructions in the documentation.
+Yes. If you are using the v1 branches (including beta), you can upgrade to the latest version of Mealie without performing a site Export/Restore. This process was required in previous versions of Mealie, however we've automated the database migration process to make it easier to upgrade. Note that if you were using the v0.5.x version, you CANNOT upgrade to the latest version automatically. You must follow the migration instructions in the documentation.
 
 - [Migration From v0.5.x](./migrating-to-mealie-v1.md)
 
@@ -45,7 +45,7 @@ You can change the theme by settings the environment variables.
 
 - [Backend Config - Themeing](./installation/backend-config.md#themeing)
 
-## How can I change the Login Session Timeout?
+## How can I change the login session timeout?
 
 Login session can be configured by setting the `TOKEN_TIME` variable on the backend container.
 
@@ -53,7 +53,7 @@ Login session can be configured by setting the `TOKEN_TIME` variable on the back
 
 ## Can I serve Mealie on a subpath?
 
-No. Due to limitations from the Javascript Framework, mealie doesn't support serving Mealie on a subpath.
+No. Due to limitations from the JavaScript Framework, Mealie doesn't support serving Mealie on a subpath.
 
 ## Can I install Mealie without docker?
 
@@ -130,8 +130,8 @@ stateDiagram-v2
 
 For more information, check out the [Permissions and Public Access guide](./usage/permissions-and-public-access.md).
 
-## Can I use fail2ban with mealie?
-Yes, mealie is configured to properly forward external IP addresses into the `mealie.log` logfile. Note that due to restrictions in docker, IP address forwarding only works on Linux.
+## Can I use fail2ban with Mealie?
+Yes, Mealie is configured to properly forward external IP addresses into the `mealie.log` logfile. Note that due to restrictions in docker, IP address forwarding only works on Linux.
 
 Your fail2ban usage should look like the following:
 ```
@@ -139,11 +139,11 @@ Use      datepattern : %d-%b-%y %H:%M:%S : Day-MON-Year2 24hour:Minute:Second
 Use   failregex line : ^ERROR:\s+Incorrect username or password from <HOST>
 ```
 
-## Why An API?
-An API allows integration into applications like [Home Assistant](https://www.home-assistant.io/) that can act as notification engines to provide custom notifications based on Meal Plan data to remind you to defrost the chicken, marinade the steak, or start the CrockPot. Additionally, you can access nearly any backend service via the API giving you total control to extend the application. To explore the API spin up your server and navigate to http://yourserver.com/docs for interactive API documentation.
+## Why an API?
+An API allows integration into applications like [Home Assistant](https://www.home-assistant.io/) that can act as notification engines to provide custom notifications based on Meal Plan data to remind you to defrost the chicken, marinate the steak, or start the CrockPot. Additionally, you can access nearly any backend service via the API giving you total control to extend the application. To explore the API spin up your server and navigate to http://yourserver.com/docs for interactive API documentation.
 
-## Why a Database?
-Some users of static-site generator applications like ChowDown have expressed concerns about their data being stuck in a database. Considering this is a new project, it is a valid concern to be worried about your data. Mealie specifically addresses this concern by provided automatic daily backups that export your data in json, plain-text markdown files, and/or custom Jinja2 templates. **This puts you in control of how your data is represented** when exported from Mealie, which means you can easily migrate to any other service provided Mealie doesn't work for you.
+## Why a database?
+Some users of static-site generator applications like ChowDown have expressed concerns about their data being stuck in a database. Considering this is a new project, it is a valid concern to be worried about your data. Mealie specifically addresses this concern by providing automatic daily backups that export your data in json, plain-text markdown files, and/or custom Jinja2 templates. **This puts you in control of how your data is represented** when exported from Mealie, which means you can easily migrate to any other service provided Mealie doesn't work for you.
 
 As to why we need a database?
 

docs/docs/documentation/getting-started/installation/backend-config.md

@@ -4,22 +4,22 @@
 
 ### General
 
-| Variables                     |        Default        | Description                                                                         |
-| ----------------------------- | :-------------------: | ----------------------------------------------------------------------------------- |
-| PUID                          |          911          | UserID permissions between host OS and container                                    |
-| PGID                          |          911          | GroupID permissions between host OS and container                                   |
-| DEFAULT_GROUP                 |         Home          | The default group for users                                                         |
-| BASE_URL                      | http://localhost:8080 | Used for Notifications                                                              |
-| TOKEN_TIME                    |          48           | The time in hours that a login/auth token is valid                                  |
-| API_PORT                      |         9000          | The port exposed by backend API. **Do not change this if you're running in Docker** |
-| API_DOCS                      |         True          | Turns on/off access to the API documentation locally.                               |
-| TZ                            |          UTC          | Must be set to get correct date/time on the server                                  |
-| ALLOW_SIGNUP<super>\*</super> |         false         | Allow user sign-up without token                                                    |
-| LOG_CONFIG_OVERRIDE           |                       | Override the config for logging with a custom path                                  |
-| LOG_LEVEL                     |         info          | Logging level (e.g. critical, error, warning, info, debug, trace)                   |
-| DAILY_SCHEDULE_TIME           |        23:45          | The time of day to run the daily tasks.                                             |
+| Variables                     |        Default        | Description                                                                                               |
+| ----------------------------- | :-------------------: | --------------------------------------------------------------------------------------------------------- |
+| PUID                          |          911          | UserID permissions between host OS and container                                                          |
+| PGID                          |          911          | GroupID permissions between host OS and container                                                         |
+| DEFAULT_GROUP                 |         Home          | The default group for users                                                                               |
+| BASE_URL                      | http://localhost:8080 | Used for Notifications                                                                                    |
+| TOKEN_TIME                    |          48           | The time in hours that a login/auth token is valid                                                        |
+| API_PORT                      |         9000          | The port exposed by backend API. **Do not change this if you're running in Docker**                       |
+| API_DOCS                      |         True          | Turns on/off access to the API documentation locally                                                      |
+| TZ                            |          UTC          | Must be set to get correct date/time on the server                                                        |
+| ALLOW_SIGNUP<super>\*</super> |         false         | Allow user sign-up without token                                                                          |
+| LOG_CONFIG_OVERRIDE           |                       | Override the config for logging with a custom path                                                        |
+| LOG_LEVEL                     |         info          | Logging level (e.g. critical, error, warning, info, debug, trace)                                         |
+| DAILY_SCHEDULE_TIME           |         23:45         | The time of day to run daily server tasks, in HH:MM format. Use the server's local time, *not* UTC        |
 
-<super>\*</super> Starting in v1.4.0 this was changed to default to `false` as apart of a security review of the application.
+<super>\*</super> Starting in v1.4.0 this was changed to default to `false` as part of a security review of the application.
 
 ### Security
 
@@ -56,12 +56,9 @@
 
 Changing the webworker settings may cause unforeseen memory leak issues with Mealie. It's best to leave these at the defaults unless you begin to experience issues with multiple users. Exercise caution when changing these settings
 
-| Variables        | Default | Description                                                                                                                       |
-| ---------------- | :-----: | --------------------------------------------------------------------------------------------------------------------------------- |
-| WEB_GUNICORN     |  false  | Enables Gunicorn to manage Uvicorn web for multiple works                                                                         |
-| WORKERS_PER_CORE |    1    | Set the number of workers to the number of CPU cores multiplied by this value (Value \* CPUs). More info [here][workers_per_core] |
-| MAX_WORKERS      |  None   | Set the maximum number of workers to use. Default is not set meaning unlimited. More info [here][max_workers]                     |
-| WEB_CONCURRENCY  |    2    | Override the automatic definition of number of workers. More info [here][web_concurrency]                                         |
+| Variables       | Default | Description                                                                   |
+| --------------- | :-----: | ----------------------------------------------------------------------------- |
+| UVICORN_WORKERS |    1    | Sets the number of works for the web server [more info here][unicorn_workers] |
 
 ### LDAP
 
@@ -87,21 +84,21 @@ Changing the webworker settings may cause unforeseen memory leak issues with Mea
 
 For usage, see [Usage - OpenID Connect](../authentication/oidc.md)
 
-| Variables              | Default | Description                                                                                                                                                                                               |
-| ---------------------- | :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| OIDC_AUTH_ENABLED      |  False  | Enables authentication via OpenID Connect                                                                                                                                                                 |
-| OIDC_SIGNUP_ENABLED    |  True   | Enables new users to be created when signing in for the first time with OIDC                                                                                                                              |
-| OIDC_CONFIGURATION_URL |  None   | The URL to the OIDC configuration of your provider. This is usually something like https://auth.example.com/.well-known/openid-configuration                                                              |
-| OIDC_CLIENT_ID         |  None   | The client id of your configured client in your provider                                                                                                                                                  |
-| OIDC_USER_GROUP        |  None   | If specified, only users belonging to this group will be able to successfully authenticate, regardless of the `OIDC_ADMIN_GROUP`. For more information see [this page](../authentication/oidc.md#groups)  |
-| OIDC_ADMIN_GROUP       |  None   | If specified, users belonging to this group will be made an admin. For more information see [this page](../authentication/oidc.md#groups)                                                                 |
-| OIDC_AUTO_REDIRECT     |  False  | If `True`, then the login page will be bypassed an you will be sent directly to your Identity Provider. You can still get to the login page by adding `?direct=1` to the login URL                        |
-| OIDC_PROVIDER_NAME     |  OAuth  | The provider name is shown in SSO login button. "Login with <OIDC_PROVIDER_NAME\>"                                                                                                                        |
-| OIDC_REMEMBER_ME       |  False  | Because redirects bypass the login screen, you cant extend your session by clicking the "Remember Me" checkbox. By setting this value to true, a session will be extended as if "Remember Me" was checked |
-| OIDC_SIGNING_ALGORITHM |  RS256  | The algorithm used to sign the id token (examples: RS256, HS256)                                                                                                                                          |
-| OIDC_USER_CLAIM        |  email  | This is the claim which Mealie will use to look up an existing user by (e.g. "email", "preferred_username") |
-| OIDC_GROUPS_CLAIM      | groups  | Optional if not using `OIDC_USER_GROUP` or `OIDC_ADMIN_GROUP`. This is the claim Mealie will request from your IdP and will use to compare to `OIDC_USER_GROUP` or `OIDC_ADMIN_GROUP` to allow the user to log in to Mealie or is set as an admin. **Your IdP must be configured to grant this claim**|
-| OIDC_TLS_CACERTFILE    | None    | File path to Certificate Authority used to verify server certificate (e.g. `/path/to/ca.crt`) |
+| Variables              | Default | Description                                                                                                                                                                                                                                                                                            |
+| ---------------------- | :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| OIDC_AUTH_ENABLED      |  False  | Enables authentication via OpenID Connect                                                                                                                                                                                                                                                              |
+| OIDC_SIGNUP_ENABLED    |  True   | Enables new users to be created when signing in for the first time with OIDC                                                                                                                                                                                                                           |
+| OIDC_CONFIGURATION_URL |  None   | The URL to the OIDC configuration of your provider. This is usually something like https://auth.example.com/.well-known/openid-configuration                                                                                                                                                           |
+| OIDC_CLIENT_ID         |  None   | The client id of your configured client in your provider                                                                                                                                                                                                                                               |
+| OIDC_USER_GROUP        |  None   | If specified, only users belonging to this group will be able to successfully authenticate, regardless of the `OIDC_ADMIN_GROUP`. For more information see [this page](../authentication/oidc.md#groups)                                                                                               |
+| OIDC_ADMIN_GROUP       |  None   | If specified, users belonging to this group will be made an admin. For more information see [this page](../authentication/oidc.md#groups)                                                                                                                                                              |
+| OIDC_AUTO_REDIRECT     |  False  | If `True`, then the login page will be bypassed an you will be sent directly to your Identity Provider. You can still get to the login page by adding `?direct=1` to the login URL                                                                                                                     |
+| OIDC_PROVIDER_NAME     |  OAuth  | The provider name is shown in SSO login button. "Login with <OIDC_PROVIDER_NAME\>"                                                                                                                                                                                                                     |
+| OIDC_REMEMBER_ME       |  False  | Because redirects bypass the login screen, you cant extend your session by clicking the "Remember Me" checkbox. By setting this value to true, a session will be extended as if "Remember Me" was checked                                                                                              |
+| OIDC_SIGNING_ALGORITHM |  RS256  | The algorithm used to sign the id token (examples: RS256, HS256)                                                                                                                                                                                                                                       |
+| OIDC_USER_CLAIM        |  email  | This is the claim which Mealie will use to look up an existing user by (e.g. "email", "preferred_username")                                                                                                                                                                                            |
+| OIDC_GROUPS_CLAIM      | groups  | Optional if not using `OIDC_USER_GROUP` or `OIDC_ADMIN_GROUP`. This is the claim Mealie will request from your IdP and will use to compare to `OIDC_USER_GROUP` or `OIDC_ADMIN_GROUP` to allow the user to log in to Mealie or is set as an admin. **Your IdP must be configured to grant this claim** |
+| OIDC_TLS_CACERTFILE    |  None   | File path to Certificate Authority used to verify server certificate (e.g. `/path/to/ca.crt`)                                                                                                                                                                                                          |
 
 ### OpenAI
 
@@ -109,13 +106,14 @@ For usage, see [Usage - OpenID Connect](../authentication/oidc.md)
 
 Mealie supports various integrations using OpenAI. To enable OpenAI, [you must provide your OpenAI API key](https://platform.openai.com/api-keys). You can tweak how OpenAI is used using these backend settings. Please note that while OpenAI usage is optimized to reduce API costs, you're unlikely to be able to use OpenAI features with the free tier limits.
 
-| Variables                 |     Default   | Description                                                                                                                    |
-| ------------------------- |    :------:   | ------------------------------------------------------------------------------------------------------------------------------ |
-| OPENAI_BASE_URL           |      None     | The base URL for the OpenAI API. If you're not sure, leave this empty to use the standard OpenAI platform                      |
-| OPENAI_API_KEY            |      None     | Your OpenAI API Key. Enables OpenAI-related features                                                                           |
-| OPENAI_MODEL              |     gpt-4o    | Which OpenAI model to use. If you're not sure, leave this empty                                                                |
-| OPENAI_WORKERS            |       2       | Number of OpenAI workers per request. Higher values may increase processing speed, but will incur additional API costs         |
-| OPENAI_SEND_DATABASE_DATA |      True     | Whether to send Mealie data to OpenAI to improve request accuracy. This will incur additional API costs                        |
+| Variables                 | Default | Description                                                                                                                                                                  |
+| ------------------------- | :-----: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| OPENAI_BASE_URL           |  None   | The base URL for the OpenAI API. If you're not sure, leave this empty to use the standard OpenAI platform                                                                    |
+| OPENAI_API_KEY            |  None   | Your OpenAI API Key. Enables OpenAI-related features                                                                                                                         |
+| OPENAI_MODEL              | gpt-4o  | Which OpenAI model to use. If you're not sure, leave this empty                                                                                                              |
+| OPENAI_WORKERS            |    2    | Number of OpenAI workers per request. Higher values may increase processing speed, but will incur additional API costs                                                       |
+| OPENAI_SEND_DATABASE_DATA |  True   | Whether to send Mealie data to OpenAI to improve request accuracy. This will incur additional API costs                                                                      |
+| OPENAI_REQUEST_TIMEOUT    |  10     | The number of seconds to wait for an OpenAI request to complete before cancelling the request. Leave this empty unless you're running into timeout issues on slower hardware |
 
 ### Themeing
 
@@ -160,6 +158,4 @@ secrets:
     file: postgrespassword.txt
 ```
 
-[workers_per_core]: https://github.com/tiangolo/uvicorn-gunicorn-docker/blob/2daa3e3873c837d5781feb4ff6a40a89f791f81b/README.md#workers_per_core
-[max_workers]: https://github.com/tiangolo/uvicorn-gunicorn-docker/blob/2daa3e3873c837d5781feb4ff6a40a89f791f81b/README.md#max_workers
-[web_concurrency]: https://github.com/tiangolo/uvicorn-gunicorn-docker/blob/2daa3e3873c837d5781feb4ff6a40a89f791f81b/README.md#web_concurrency
+[unicorn_workers]: https://www.uvicorn.org/deployment/#built-in

docs/docs/documentation/getting-started/installation/installation-checklist.md

@@ -58,7 +58,7 @@ The following steps were tested on a Ubuntu 20.04 server, but should work for mo
 4. Create a docker-compose.yaml file in the mealie directory: `touch docker-compose.yaml`
 5. Use the text editor of your choice to edit the file and copy the contents of the docker-compose template for the deployment type you want to use: `nano docker-compose.yaml` or `vi docker-compose.yaml`
 
-## Step 2: Customizing The `docker-compose.yaml` files.
+## Step 3: Customizing The `docker-compose.yaml` files.
 
 After you've decided setup the files it's important to set a few ENV variables to ensure that you can use all the features of Mealie. I recommend that you verify and check that:
 
@@ -67,7 +67,7 @@ After you've decided setup the files it's important to set a few ENV variables t
 - [x] You've set the [`BASE_URL`](./backend-config.md#general) variable.
 - [x] You've set the `DEFAULT_EMAIL` and `DEFAULT_GROUP` variable.
 
-## Step 3: Startup
+## Step 4: Startup
 
 After you've configured your database and updated the `docker-compose.yaml` files, you can start Mealie by running the following command in the directory where you've added your `docker-compose.yaml`.
 
@@ -87,11 +87,11 @@ You should see the containers start up without error. You should now be able to
 
     **Password:** MyPassword
 
-## Step 4: Validate Installation
+## Step 5: Validate Installation
 
 After the startup is complete, you should see a login screen. Use the default credentials above to log in and navigate to `/admin/site-settings`. Here, you'll find a summary of your configuration details and their respective status. Before proceeding, you should validate that the configuration is correct. For any warnings or errors the page will display an error and notify you of what you need to verify.
 
-## Step 5: Backup
+## Step 6: Backup
 
 While v1.0.0 is a great step to data-stability and security, it's not a backup. Mealie provides a full site data backup mechanism through the UI.
 

docs/docs/documentation/getting-started/installation/logs.md

@@ -2,7 +2,7 @@
 
 :octicons-tag-24: v1.5.0
 
-## Highlighs
+## Highlights
 
 - Logs are written to `/app/data/mealie.log` by default in the container.
 - Logs are also written to stdout and stderr.
@@ -13,4 +13,4 @@
 Starting in v1.5.0 logging is now highly configurable. Using the `LOG_CONFIG_OVERRIDE` you can provide the application with a custom configuration to log however you'd like. This configuration file is based off the [Python Logging Config](https://docs.python.org/3/library/logging.config.html#logging.config.fileConfig). It can be difficult to understand the configuration at first, so here are some resources to help get started.
 
 - This [YouTube Video](https://www.youtube.com/watch?v=9L77QExPmI0) for a great walkthrough on the logging file format.
-- Our [Logging Config](https://github.com/mealie-recipes/mealie/blob/mealie-next/mealie/core/logger/logconf.prod.json)
+- Our [Logging Config](https://github.com/mealie-recipes/mealie/blob/mealie-next/mealie/core/logger/logconf.prod.json).

docs/docs/documentation/getting-started/installation/postgres.md

@@ -7,7 +7,7 @@ PostgreSQL might be considered if you need to support many concurrent users. In
 ```yaml
 services:
   mealie:
-    image: ghcr.io/mealie-recipes/mealie:v1.7.0 # (3)
+    image: ghcr.io/mealie-recipes/mealie:v1.10.2 # (3)
     container_name: mealie
     restart: always
     ports:
@@ -20,7 +20,7 @@ services:
       - mealie-data:/app/data/
     environment:
       # Set Backend ENV Variables Here
-      ALLOW_SIGNUP: true
+      ALLOW_SIGNUP: false
       PUID: 1000
       PGID: 1000
       TZ: America/Anchorage

docs/docs/documentation/getting-started/installation/sqlite.md

@@ -11,7 +11,7 @@ SQLite is a popular, open source, self-contained, zero-configuration database th
 ```yaml
 services:
   mealie:
-    image: ghcr.io/mealie-recipes/mealie:v1.7.0 # (3)
+    image: ghcr.io/mealie-recipes/mealie:v1.10.2 # (3)
     container_name: mealie
     restart: always
     ports:
@@ -24,7 +24,7 @@ services:
       - mealie-data:/app/data/
     environment:
       # Set Backend ENV Variables Here
-      ALLOW_SIGNUP: true
+      ALLOW_SIGNUP: false
       PUID: 1000
       PGID: 1000
       TZ: America/Anchorage

docs/mkdocs.yml

@@ -79,8 +79,8 @@ nav:
           - Permissions and Public Access: "documentation/getting-started/usage/permissions-and-public-access.md"
 
       - Authentication:
-        - LDAP: "documentation/getting-started/authentication/ldap.md"
-        - OpenID Connect: "documentation/getting-started/authentication/oidc.md"
+          - LDAP: "documentation/getting-started/authentication/ldap.md"
+          - OpenID Connect: "documentation/getting-started/authentication/oidc.md"
 
       - Community Guides:
           - iOS Shortcuts: "documentation/community-guide/ios.md"
@@ -88,6 +88,7 @@ nav:
           - Home Assistant: "documentation/community-guide/home-assistant.md"
           - Bulk Url Import: "documentation/community-guide/bulk-url-import.md"
           - Import Bookmarklet: "documentation/community-guide/import-recipe-bookmarklet.md"
+          - Automate Backups with n8n: "documentation/community-guide/n8n-backup-automation.md"
 
   - API Reference: "api/redoc.md"
 
@@ -97,23 +98,7 @@ nav:
       - Developers Guide:
           - Code Contributions: "contributors/developers-guide/code-contributions.md"
           - Dev Getting Started: "contributors/developers-guide/starting-dev-server.md"
+          - Database Changes: "contributors/developers-guide/database-changes.md"
           - Maintainers Guide: "contributors/developers-guide/maintainers.md"
       - Guides:
           - Improving Ingredient Parser: "contributors/guides/ingredient-parser.md"
-
-  - Change Log:
-      - v1.0.0beta-5: "changelog/v1.0.0beta-5.md"
-      - v1.0.0beta-4: "changelog/v1.0.0beta-4.md"
-      - v1.0.0beta-3: "changelog/v1.0.0beta-3.md"
-      - v1.0.0beta-2: "changelog/v1.0.0beta-2.md"
-      - v1.0.0 Beta: "changelog/v1.0.0.md"
-      - v0.5.2 Misc Updates: "changelog/v0.5.2.md"
-      - v0.5.1 Bug Fixes: "changelog/v0.5.1.md"
-      - v0.5.0 General Upgrades: "changelog/v0.5.0.md"
-      - v0.4.3 Hot Fix: "changelog/v0.4.3.md"
-      - v0.4.2 Backend/Migrations: "changelog/v0.4.2.md"
-      - v0.4.1 Frontend/UI: "changelog/v0.4.1.md"
-      - v0.4.0 Authentication: "changelog/v0.4.0.md"
-      - v0.3.0 Improvements: "changelog/v0.3.0.md"
-      - v0.2.0 Now With Tests!: "changelog/v0.2.0.md"
-      - v0.1.0 Beta: "changelog/v0.1.0.md"

frontend/.prettierrc

@@ -6,4 +6,4 @@
   "printWidth": 120,
   "arrowParens": "always",
   "eslintIntegration": true
-}
+}

frontend/components/Domain/Group/GroupWebhookEditor.vue

@@ -18,8 +18,6 @@
             icon: $globals.icons.testTube,
             text: $tc('general.test'),
             event: 'test',
-            // TODO: There is no functionality hooked up to this. Enable it when there is
-            disabled: true,
           },
           {
             icon: $globals.icons.save,

frontend/components/Domain/Recipe/RecipeCardMobile.vue

@@ -36,6 +36,9 @@
           <v-list-item-subtitle>
             <SafeMarkdown :source="description" />
           </v-list-item-subtitle>
+          <div class="d-flex flex-wrap justify-start">
+            <RecipeChips :truncate="true" :items="tags" :title="false" :limit="2" :small="true" url-prefix="tags" />
+          </div>
           <div class="d-flex flex-wrap justify-end align-center">
             <slot name="actions">
               <RecipeFavoriteBadge v-if="isOwnGroup && showRecipeContent" :recipe-id="recipeId" show-always />
@@ -83,6 +86,7 @@ import RecipeFavoriteBadge from "./RecipeFavoriteBadge.vue";
 import RecipeContextMenu from "./RecipeContextMenu.vue";
 import RecipeCardImage from "./RecipeCardImage.vue";
 import RecipeRating from "./RecipeRating.vue";
+import RecipeChips from "./RecipeChips.vue";
 import { useLoggedInState } from "~/composables/use-logged-in-state";
 
 export default defineComponent({
@@ -91,6 +95,7 @@ export default defineComponent({
     RecipeContextMenu,
     RecipeRating,
     RecipeCardImage,
+    RecipeChips,
   },
   props: {
     name: {
@@ -114,6 +119,10 @@ export default defineComponent({
       required: false,
       default: "abc123",
     },
+    tags: {
+      type: Array,
+      default: () => [],
+    },
     recipeId: {
       type: String,
       required: true,

frontend/components/Domain/Recipe/RecipeDialogAddToShoppingList.vue

@@ -231,36 +231,46 @@ export default defineComponent({
 
         const shoppingListIngredients: ShoppingListIngredient[] = recipe.recipeIngredient.map((ing) => {
           return {
-            checked: true,
+            checked: !ing.food?.onHand,
             ingredient: ing,
             disableAmount: recipe.settings?.disableAmount || false,
           }
         });
 
+        let currentTitle = "";
+        const onHandIngs: ShoppingListIngredient[] = [];
         const shoppingListIngredientSections = shoppingListIngredients.reduce((sections, ing) => {
-          // if title append new section to the end of the array
           if (ing.ingredient.title) {
+            currentTitle = ing.ingredient.title;
+          }
+
+          // If this is the first item in the section, create a new section
+          if (sections.length === 0 || currentTitle !== sections[sections.length - 1].sectionName) {
+            if (sections.length) {
+              // Add the on-hand ingredients to the previous section
+              sections[sections.length - 1].ingredients.push(...onHandIngs);
+              onHandIngs.length = 0;
+            }
             sections.push({
-              sectionName: ing.ingredient.title,
-              ingredients: [ing],
+              sectionName: currentTitle,
+              ingredients: [],
             });
+          }
+
+          // Store the on-hand ingredients for later
+          if (ing.ingredient.food?.onHand) {
+            onHandIngs.push(ing);
             return sections;
           }
 
-          // append new section if first
-          if (sections.length === 0) {
-            sections.push({
-              sectionName: "",
-              ingredients: [ing],
-            });
-            return sections;
-          }
-
-          // otherwise add ingredient to last section in the array
+          // Add the ingredient to previous section
           sections[sections.length - 1].ingredients.push(ing);
           return sections;
         }, [] as ShoppingListIngredientSection[]);
 
+        // Add remaining on-hand ingredients to the previous section
+        shoppingListIngredientSections[shoppingListIngredientSections.length - 1].ingredients.push(...onHandIngs);
+
         recipeSectionMap.set(recipe.slug, {
           recipeId: recipe.id,
           recipeName: recipe.name,

frontend/components/Domain/Recipe/RecipeDialogPrintPreferences.vue

@@ -31,6 +31,13 @@
               <v-switch v-model="preferences.showNotes" hide-details :label="$tc('recipe.notes')" />
             </v-row>
           </v-col>
+          <v-col cols="auto" align-self="start">
+            <v-row no-gutters>
+              <v-switch v-model="preferences.showNutrition" hide-details :label="$tc('recipe.nutrition')" />
+            </v-row>
+            <v-row no-gutters>
+            </v-row>
+          </v-col>
         </v-row>
       </v-container>
       <v-card

frontend/components/Domain/Recipe/RecipeExplorerPage.vue

@@ -126,8 +126,8 @@
       <RecipeCardSection
         v-if="state.ready"
         class="mt-n5"
-        :icon="$globals.icons.search"
-        :title="$tc('search.results')"
+        :icon="$globals.icons.silverwareForkKnife"
+        :title="$tc('general.recipes')"
         :recipes="recipes"
         :query="passedQueryWithSeed"
         @replaceRecipes="replaceRecipes"

frontend/components/Domain/Recipe/RecipeIngredientEditor.vue

@@ -104,6 +104,8 @@
             :buttons="btns"
             @toggle-section="toggleTitle"
             @toggle-original="toggleOriginalText"
+            @insert-above="$emit('insert-above')"
+            @insert-below="$emit('insert-below')"
             @insert-ingredient="$emit('insert-ingredient')"
             @delete="$emit('delete')"
           />
@@ -148,6 +150,14 @@ export default defineComponent({
           text: i18n.tc("recipe.toggle-section"),
           event: "toggle-section",
         },
+        {
+          text: i18n.tc("recipe.insert-above"),
+          event: "insert-above",
+        },
+        {
+          text: i18n.tc("recipe.insert-below"),
+          event: "insert-below",
+        },
       ];
 
       if (props.allowInsertIngredient) {

frontend/components/Domain/Recipe/RecipeIngredientListItem.vue

@@ -45,6 +45,22 @@ export default defineComponent({
   .d-inline {
     & > p {
       display: inline;
+      &:has(>sub)>sup {
+        letter-spacing: -0.05rem;
+      }
+    }
+    &:has(sub) {
+      &:after {
+        letter-spacing: -0.2rem;
+      }
+    }
+    sup {
+      &+span{
+        letter-spacing: -0.05rem;
+      }
+      &:before {
+        letter-spacing: 0rem;
+      }
     }
   }
 

frontend/components/Domain/Recipe/RecipeLastMade.vue

@@ -102,7 +102,7 @@
           <v-icon left>
             {{ $globals.icons.calendar }}
           </v-icon>
-            {{ $t('recipe.last-made-date', { date: value ? new Date(value+"Z").toLocaleDateString($i18n.locale) : $t("general.never") } ) }}
+            {{ $t('recipe.last-made-date', { date: value ? new Date(value).toLocaleDateString($i18n.locale) : $t("general.never") } ) }}
         </v-chip>
       </div>
     </div>
@@ -199,11 +199,7 @@ export default defineComponent({
         await userApi.recipes.updateLastMade(props.recipe.slug,  newTimelineEvent.value.timestamp);
 
         // update recipe in parent so the user can see it
-        // we remove the trailing "Z" since this is how the API returns it
-        context.emit(
-          "input", newTimelineEvent.value.timestamp
-            .substring(0, newTimelineEvent.value.timestamp.length - 1)
-        );
+        context.emit("input", newTimelineEvent.value.timestamp);
       }
 
       // update the image, if provided

frontend/components/Domain/Recipe/RecipeList.vue

@@ -7,7 +7,7 @@
       :class="attrs.class.sheet"
       :style="tile ? 'max-width: 100%; width: fit-content;' : 'width: 100%;'"
     >
-      <v-list-item :to="'/g/' + groupSlug + '/r/' + recipe.slug" :class="attrs.class.listItem">
+      <v-list-item :to="disabled ? '' : '/g/' + groupSlug + '/r/' + recipe.slug" :class="attrs.class.listItem">
         <v-list-item-avatar :class="attrs.class.avatar">
           <v-icon :class="attrs.class.icon" dark :small="small"> {{ $globals.icons.primary }} </v-icon>
         </v-list-item-avatar>
@@ -56,6 +56,10 @@ export default defineComponent({
       type: Boolean,
       default: false,
     },
+    disabled: {
+      type: Boolean,
+      default: false,
+    }
   },
   setup(props) {
     const { $auth } = useContext();

frontend/components/Domain/Recipe/RecipeNutrition.vue

@@ -8,14 +8,8 @@
       <v-card-text v-if="edit">
         <div v-for="(item, key, index) in value" :key="index">
           <v-text-field
-            dense
-            :value="value[key]"
-            :label="labels[key].label"
-            :suffix="labels[key].suffix"
-            type="number"
-            autocomplete="off"
-            @input="updateValue(key, $event)"
-          ></v-text-field>
+dense :value="value[key]" :label="labels[key].label" :suffix="labels[key].suffix" type="number"
+            autocomplete="off" @input="updateValue(key, $event)"></v-text-field>
         </div>
       </v-card-text>
       <v-list v-if="showViewer" dense class="mt-0 pt-0">
@@ -34,17 +28,10 @@
 </template>
 
 <script lang="ts">
-import { computed, defineComponent, useContext } from "@nuxtjs/composition-api";
+import { computed, defineComponent } from "@nuxtjs/composition-api";
+import { useNutritionLabels } from "~/composables/recipes";
 import { Nutrition } from "~/lib/api/types/recipe";
-
-type NutritionLabelType = {
-  [key: string]: {
-    label: string;
-    suffix: string;
-    value?: string;
-  };
-};
-
+import { NutritionLabelType } from "~/composables/recipes/use-recipe-nutrition";
 export default defineComponent({
   props: {
     value: {
@@ -57,37 +44,7 @@ export default defineComponent({
     },
   },
   setup(props, context) {
-    const { i18n } = useContext();
-    const labels = <NutritionLabelType>{
-      calories: {
-        label: i18n.tc("recipe.calories"),
-        suffix: i18n.tc("recipe.calories-suffix"),
-      },
-      fatContent: {
-        label: i18n.tc("recipe.fat-content"),
-        suffix: i18n.tc("recipe.grams"),
-      },
-      fiberContent: {
-        label: i18n.tc("recipe.fiber-content"),
-        suffix: i18n.tc("recipe.grams"),
-      },
-      proteinContent: {
-        label: i18n.tc("recipe.protein-content"),
-        suffix: i18n.tc("recipe.grams"),
-      },
-      sodiumContent: {
-        label: i18n.tc("recipe.sodium-content"),
-        suffix: i18n.tc("recipe.milligrams"),
-      },
-      sugarContent: {
-        label: i18n.tc("recipe.sugar-content"),
-        suffix: i18n.tc("recipe.grams"),
-      },
-      carbohydrateContent: {
-        label: i18n.tc("recipe.carbohydrate-content"),
-        suffix: i18n.tc("recipe.grams"),
-      },
-    };
+    const { labels } = useNutritionLabels();
     const valueNotNull = computed(() => {
       let key: keyof Nutrition;
       for (key in props.value) {

frontend/components/Domain/Recipe/RecipeOrganizerPage.vue

@@ -114,9 +114,9 @@ export default defineComponent({
       options: {
         ignoreLocation: true,
         shouldSort: true,
-        threshold: 0.6,
+        threshold: 0.2,
         location: 0,
-        distance: 100,
+        distance: 20,
         findAllMatches: true,
         maxPatternLength: 32,
         minMatchCharLength: 1,

frontend/components/Domain/Recipe/RecipePage/RecipePage.vue

@@ -72,7 +72,7 @@
     </div>
 
     <RecipePageComments
-      v-if="isOwnGroup && !recipe.settings.disableComments && !isEditForm && !isCookMode"
+      v-if="!recipe.settings.disableComments && !isEditForm && !isCookMode"
       :recipe="recipe"
       class="px-1 my-4 d-print-none"
     />

frontend/components/Domain/Recipe/RecipePage/RecipePageParts/RecipePageComments.vue

@@ -30,7 +30,7 @@
         </BaseButton>
       </div>
     </div>
-    <div v-for="comment in comments" :key="comment.id" class="d-flex my-2" style="gap: 10px">
+    <div v-for="comment in recipe.comments" :key="comment.id" class="d-flex my-2" style="gap: 10px">
       <UserAvatar size="40" :user-id="comment.userId" />
       <v-card outlined class="flex-grow-1">
         <v-card-text class="pa-3 pb-0">
@@ -54,9 +54,9 @@
 </template>
 
 <script lang="ts">
-import { defineComponent, ref, toRefs, onMounted, reactive } from "@nuxtjs/composition-api";
+import { defineComponent, toRefs, reactive } from "@nuxtjs/composition-api";
 import { useUserApi } from "~/composables/api";
-import { Recipe, RecipeCommentOut } from "~/lib/api/types/recipe";
+import { Recipe } from "~/lib/api/types/recipe";
 import UserAvatar from "~/components/Domain/User/UserAvatar.vue";
 import { NoUndefinedField } from "~/lib/api/types/non-generated";
 import { usePageUser } from "~/composables/recipe-page/shared-state";
@@ -76,22 +76,12 @@ export default defineComponent({
   setup(props) {
     const api = useUserApi();
 
-    const comments = ref<RecipeCommentOut[]>([]);
-
     const { user } = usePageUser();
 
     const state = reactive({
       comment: "",
     });
 
-    onMounted(async () => {
-      const { data } = await api.recipes.comments.byRecipe(props.recipe.slug);
-
-      if (data) {
-        comments.value = data;
-      }
-    });
-
     async function submitComment() {
       const { data } = await api.recipes.comments.createOne({
         recipeId: props.recipe.id,
@@ -99,7 +89,8 @@ export default defineComponent({
       });
 
       if (data) {
-        comments.value.push(data);
+        // @ts-ignore username is always populated here
+        props.recipe.comments.push(data);
       }
 
       state.comment = "";
@@ -109,11 +100,11 @@ export default defineComponent({
       const { response } = await api.recipes.comments.deleteOne(id);
 
       if (response?.status === 200) {
-        comments.value = comments.value.filter((comment) => comment.id !== id);
+        props.recipe.comments = props.recipe.comments.filter((comment) => comment.id !== id);
       }
     }
 
-    return { api, comments, ...toRefs(state), submitComment, deleteComment, user };
+    return { api, ...toRefs(state), submitComment, deleteComment, user };
   },
 });
 </script>

frontend/components/Domain/Recipe/RecipePage/RecipePageParts/RecipePageIngredientEditor.vue

@@ -7,7 +7,7 @@
       handle=".handle"
       v-bind="{
         animation: 200,
-        group: 'description',
+        group: 'recipe-ingredients',
         disabled: false,
         ghostClass: 'ghost',
       }"
@@ -22,6 +22,8 @@
           class="list-group-item"
           :disable-amount="recipe.settings.disableAmount"
           @delete="recipe.recipeIngredient.splice(index, 1)"
+          @insert-above="insertNewIngredient(index)"
+          @insert-below="insertNewIngredient(index+1)"
         />
       </TransitionGroup>
     </draggable>
@@ -140,6 +142,20 @@ export default defineComponent({
       }
     }
 
+    function insertNewIngredient(dest: number) {
+      props.recipe.recipeIngredient.splice(dest, 0, {
+            referenceId: uuid4(),
+            title: "",
+            note: "",
+            // @ts-expect-error - prop can be null-type by NoUndefinedField type forces it to be set
+            unit: undefined,
+            // @ts-expect-error - prop can be null-type by NoUndefinedField type forces it to be set
+            food: undefined,
+            disableAmount: true,
+            quantity: 1,
+          });
+    }
+
     return {
       user,
       groupSlug,
@@ -148,6 +164,7 @@ export default defineComponent({
       hasFoodOrUnit,
       imageKey,
       drag,
+      insertNewIngredient,
     };
   },
 });

frontend/components/Domain/Recipe/RecipePage/RecipePageParts/RecipePageInstructions.vue

@@ -79,7 +79,7 @@
       handle=".handle"
       v-bind="{
         animation: 200,
-        group: 'description',
+        group: 'recipe-instructions',
         ghostClass: 'ghost',
       }"
       @input="updateIndex"
@@ -170,12 +170,22 @@
                               text: $tc('recipe.move-to-bottom'),
                               event: 'move-to-bottom',
                             },
+                            {
+                              text: $tc('recipe.insert-above'),
+                              event: 'insert-above'
+                            },
+                            {
+                              text: $tc('recipe.insert-below'),
+                              event: 'insert-below'
+                            },
                           ],
                         },
                       ]"
                       @merge-above="mergeAbove(index - 1, index)"
                       @move-to-top="moveTo('top', index)"
                       @move-to-bottom="moveTo('bottom', index)"
+                      @insert-above="insert(index)"
+                      @insert-below="insert(index+1)"
                       @toggle-section="toggleShowTitle(step.id)"
                       @link-ingredients="openDialog(index, step.text, step.ingredientReferences)"
                       @preview-step="togglePreviewState(index)"
@@ -550,6 +560,10 @@ export default defineComponent({
       }
     }
 
+    function insert(dest: number) {
+      props.value.splice(dest, 0, { id: uuid4(), text: "", title: "", ingredientReferences: [] });
+    }
+
     const previewStates = ref<boolean[]>([]);
 
     function togglePreviewState(index: number) {
@@ -681,6 +695,7 @@ export default defineComponent({
       showCookMode,
       isCookMode,
       isEditForm,
+      insert,
     };
   },
 });

frontend/components/Domain/Recipe/RecipePrintView.vue

@@ -30,6 +30,9 @@
     <!-- Ingredients -->
     <section>
       <v-card-title class="headline pl-0"> {{ $t("recipe.ingredients") }} </v-card-title>
+      <div class="font-italic px-0 py-0">
+        <SafeMarkdown :source="recipe.recipeYield" />
+      </div>
       <div
         v-for="(ingredientSection, sectionIndex) in ingredientSections"
         :key="`ingredient-section-${sectionIndex}`"
@@ -83,19 +86,41 @@
         </div>
       </section>
     </div>
+
+    <!-- Nutrition -->
+    <div v-if="preferences.showNutrition">
+      <v-card-title class="headline pl-0"> {{ $t("recipe.nutrition") }} </v-card-title>
+
+      <section>
+        <div class="print-section">
+          <table class="nutrition-table">
+            <tbody>
+              <tr v-for="(value, key) in recipe.nutrition" :key="key">
+                <template v-if="value">
+                  <td>{{ labels[key].label }}</td>
+                  <td>{{ value || '-' }}</td>
+                </template>
+              </tr>
+            </tbody>
+          </table>
+      </div>
+    </section>
+    </div>
+
   </div>
 </template>
 
 <script lang="ts">
-import { defineComponent, computed } from "@nuxtjs/composition-api";
+import { computed, defineComponent } from "@nuxtjs/composition-api";
 import RecipeTimeCard from "~/components/Domain/Recipe/RecipeTimeCard.vue";
 import { useStaticRoutes } from "~/composables/api";
-import { Recipe, RecipeIngredient, RecipeStep } from "~/lib/api/types/recipe";
+import { Recipe, RecipeIngredient, RecipeStep} from "~/lib/api/types/recipe";
 import { NoUndefinedField } from "~/lib/api/types/non-generated";
 import { ImagePosition, useUserPrintPreferences } from "~/composables/use-users/preferences";
-import { parseIngredientText } from "~/composables/recipes";
+import { parseIngredientText, useNutritionLabels } from "~/composables/recipes";
 import { usePageState } from "~/composables/recipe-page/shared-state";
 
+
 type IngredientSection = {
   sectionName: string;
   ingredients: RecipeIngredient[];
@@ -129,6 +154,10 @@ export default defineComponent({
     const preferences = useUserPrintPreferences();
     const { recipeImage } = useStaticRoutes();
     const { imageKey } = usePageState(props.recipe.slug);
+    const {labels} = useNutritionLabels();
+
+
+
 
     const recipeImageUrl = computed(() => {
       return recipeImage(props.recipe.id, props.recipe.image, imageKey.value);
@@ -221,6 +250,7 @@ export default defineComponent({
     }
 
     return {
+      labels,
       hasNotes,
       imageKey,
       ImagePosition,
@@ -290,4 +320,16 @@ li {
   list-style-type: none;
   margin-bottom: 0.25rem;
 }
+
+.nutrition-table {
+  width: 25%;
+  border-collapse: collapse;
+}
+
+.nutrition-table td {
+  padding: 2px;
+  text-align: left;
+  font-size: 14px;
+}
+
 </style>

frontend/components/Domain/Recipe/RecipeTimelineItem.vue

@@ -8,7 +8,7 @@
     <template v-if="!useMobileFormat" #opposite>
       <v-chip v-if="event.timestamp" label large>
         <v-icon class="mr-1"> {{ $globals.icons.calendar }} </v-icon>
-        {{ new Date(event.timestamp+"Z").toLocaleDateString($i18n.locale) }}
+        {{ new Date(event.timestamp).toLocaleDateString($i18n.locale) }}
       </v-chip>
     </template>
     <v-card
@@ -25,7 +25,7 @@
           <v-col v-if="useMobileFormat" align-self="center" class="pr-0">
               <v-chip label>
               <v-icon> {{ $globals.icons.calendar }} </v-icon>
-              {{ new Date(event.timestamp+"Z").toLocaleDateString($i18n.locale) }}
+              {{ new Date(event.timestamp || "").toLocaleDateString($i18n.locale) }}
               </v-chip>
           </v-col>
           <v-col v-else cols="9" style="margin: auto; text-align: center;">

frontend/components/Domain/ShoppingList/ShoppingListItem.vue

@@ -69,13 +69,13 @@
     </v-row>
     <v-row v-if="!listItem.checked && recipeList && recipeList.length && displayRecipeRefs" no-gutters class="mb-2">
       <v-col cols="auto" style="width: 100%;">
-        <RecipeList :recipes="recipeList" :list-item="listItem" small tile />
+        <RecipeList :recipes="recipeList" :list-item="listItem" :disabled="$nuxt.isOffline" small tile />
       </v-col>
     </v-row>
     <v-row v-if="listItem.checked" no-gutters class="mb-2">
       <v-col cols="auto">
         <div class="text-caption font-weight-light font-italic">
-          {{ $t("shopping-list.completed-on", {date: new Date(listItem.updateAt+"Z").toLocaleDateString($i18n.locale)}) }}
+          {{ $t("shopping-list.completed-on", {date: new Date(listItem.updateAt || "").toLocaleDateString($i18n.locale)}) }}
         </div>
       </v-col>
     </v-row>
@@ -135,7 +135,7 @@ export default defineComponent({
     recipes: {
       type: Map<string, RecipeSummary>,
       default: undefined,
-    }
+    },
   },
   setup(props, context) {
     const { i18n } = useContext();

frontend/components/Domain/User/UserProfileLinkCard.vue

@@ -53,4 +53,3 @@ export default defineComponent({
   },
 });
 </script>
-    

frontend/components/Layout/DefaultLayout.vue

@@ -157,9 +157,9 @@
 
       const topLinks = computed<SidebarLinks>(() => [
         {
-          icon: $globals.icons.search,
+          icon: $globals.icons.silverwareForkKnife,
           to: `/g/${groupSlug.value}`,
-          title: i18n.tc("sidebar.search"),
+          title: i18n.tc("general.recipes"),
           restricted: true,
         },
         {

frontend/components/README.md

@@ -1,7 +1,7 @@
 # Components Folder Guide
 
 ## Domain Components
-Domain Components are specific to the domain or section of a website. For example if you have an admin page and a user page that have specific, unshared elements. These can be placed in the Domain/Admin folder. 
+Domain Components are specific to the domain or section of a website. For example if you have an admin page and a user page that have specific, unshared elements. These can be placed in the Domain/Admin folder.
 
 **Rules**
 - Components should be prefixed with their domain name
@@ -19,8 +19,8 @@ This folder is for widely reused components that provide little functionality an
 The layout folder is for reusable components that are specifically **only** used in the layouts for the Nuxt Application. They may take props or may not. They should be larger layout style components that don't have wide the ability to be widely reused in the application.
 
 **Rules:**
-- Layout folder should not have a subfolder 
-- If they take props they should start with a 'App' Prefix. 
+- Layout folder should not have a subfolder
+- If they take props they should start with a 'App' Prefix.
   - Examples: AppSidebar, AppHeader, AppFooter.
 - If they do not they should begin with the 'The' prefix
   - Examples: TheSidebar, TheHeader, TheFooter.
@@ -29,7 +29,6 @@ The layout folder is for reusable components that are specifically **only** used
 The Page folder is dedicated to 'single-use' component to break up large amounts on content in the pages themselves. A good examples of this is breaking your landing page into separate sections to make it more readable and less monolithic. Page components typically consume other components.
 
 **Rules:**
-- These are *last resort* components. Only to be used when the page becomes unmanageable. 
+- These are *last resort* components. Only to be used when the page becomes unmanageable.
 - Page components should be prefixed with their page name
   - Examples: HomeAbout, HomeContact, ClientProfile
-

frontend/components/global/BannerExperimental.vue

@@ -1,11 +1,12 @@
 <template>
-  <v-alert border="left" colored-border type="warning" elevation="2" :icon="$globals.icons.alert">
-    <b>{{ $t("banner-experimental.title") }}</b>
-    <div>{{ $t("banner-experimental.description") }}</div>
-    <div v-if="issue != ''" class="py-2">
+  <BannerWarning
+    :title="$tc('banner-experimental.title')"
+    :description="$tc('banner-experimental.description')"
+  >
+    <template v-if="issue" #default>
       <a :href="issue" target="_blank">{{ $t("banner-experimental.issue-link-text") }}</a>
-    </div>
-  </v-alert>
+    </template>
+  </BannerWarning>
 </template>
 
 <script lang="ts">

frontend/components/global/BannerWarning.vue

@@ -0,0 +1,26 @@
+<template>
+  <v-alert border="left" colored-border type="warning" elevation="2" :icon="$globals.icons.alert">
+    <b v-if="title">{{ title }}</b>
+    <div v-if="description">{{ description }}</div>
+    <div v-if="$slots.default" class="py-2">
+      <slot></slot>
+    </div>
+  </v-alert>
+</template>
+
+<script lang="ts">
+export default {
+  props: {
+    title: {
+      type: String,
+      required: false,
+      default: "",
+    },
+    description: {
+      type: String,
+      required: false,
+      default: "",
+    },
+  },
+};
+</script>

frontend/components/global/DevDumpJson.vue

@@ -22,4 +22,4 @@ export default defineComponent({
     };
   },
 });
-</script>
+</script>

frontend/composables/recipe-page/use-extract-ingredient-references.ts

@@ -57,4 +57,4 @@ export function useExtractIngredientReferences(recipeIngredients: RecipeIngredie
 
     return new Set<string>(allMatchedIngredientIds)
 
-}
+}

frontend/composables/recipes/index.ts

@@ -2,4 +2,5 @@ export { useFraction } from "./use-fraction";
 export { useRecipe } from "./use-recipe";
 export { useRecipes, recentRecipes, allRecipes, useLazyRecipes } from "./use-recipes";
 export { parseIngredientText, useParsedIngredientText } from "./use-recipe-ingredients";
+export { useNutritionLabels } from "./use-recipe-nutrition";
 export { useTools } from "./use-recipe-tools";

frontend/composables/recipes/use-recipe-ingredients.test.ts

@@ -31,13 +31,13 @@ describe(parseIngredientText.name, () => {
   test("ingredient text with fraction", () => {
     const ingredient = createRecipeIngredient({ quantity: 1.5, unit: { fraction: true, id: "1", name: "cup" } });
 
-    expect(parseIngredientText(ingredient, false, 1, true)).contain("1 <sup>1</sup>").and.to.contain("<sub>2</sub>");
+    expect(parseIngredientText(ingredient, false, 1, true)).contain("1<sup>1</sup>").and.to.contain("<sub>2</sub>");
   });
 
   test("ingredient text with fraction when unit is null", () => {
     const ingredient = createRecipeIngredient({ quantity: 1.5, unit: undefined });
 
-    expect(parseIngredientText(ingredient, false, 1, true)).contain("1 <sup>1</sup>").and.to.contain("<sub>2</sub>");
+    expect(parseIngredientText(ingredient, false, 1, true)).contain("1<sup>1</sup>").and.to.contain("<sub>2</sub>");
   });
 
   test("ingredient text with fraction no formatting", () => {

frontend/composables/recipes/use-recipe-ingredients.ts

@@ -63,7 +63,7 @@ export function useParsedIngredientText(ingredient: RecipeIngredient, disableAmo
 
       if (fraction[1] > 0) {
         returnQty += includeFormating ?
-          ` <sup>${fraction[1]}</sup>&frasl;<sub>${fraction[2]}</sub>` :
+          `<sup>${fraction[1]}</sup><span>&frasl;</span><sub>${fraction[2]}</sub>` :
           ` ${fraction[1]}/${fraction[2]}`;
       }
     }

frontend/composables/recipes/use-recipe-nutrition.ts

@@ -0,0 +1,47 @@
+import { useContext } from "@nuxtjs/composition-api";
+
+
+export interface NutritionLabelType {
+  [key: string]: {
+    label: string;
+    suffix: string;
+    value?: string;
+  };
+};
+
+
+export function useNutritionLabels() {
+  const { i18n } = useContext();
+  const labels = <NutritionLabelType>{
+    calories: {
+      label: i18n.tc("recipe.calories"),
+      suffix: i18n.tc("recipe.calories-suffix"),
+    },
+    fatContent: {
+      label: i18n.tc("recipe.fat-content"),
+      suffix: i18n.tc("recipe.grams"),
+    },
+    fiberContent: {
+      label: i18n.tc("recipe.fiber-content"),
+      suffix: i18n.tc("recipe.grams"),
+    },
+    proteinContent: {
+      label: i18n.tc("recipe.protein-content"),
+      suffix: i18n.tc("recipe.grams"),
+    },
+    sodiumContent: {
+      label: i18n.tc("recipe.sodium-content"),
+      suffix: i18n.tc("recipe.milligrams"),
+    },
+    sugarContent: {
+      label: i18n.tc("recipe.sugar-content"),
+      suffix: i18n.tc("recipe.grams"),
+    },
+    carbohydrateContent: {
+      label: i18n.tc("recipe.carbohydrate-content"),
+      suffix: i18n.tc("recipe.grams"),
+    },
+  };
+
+  return { labels }
+}

frontend/composables/store/use-food-store.ts

@@ -19,6 +19,7 @@ export const useFoodData = function () {
     name: "",
     description: "",
     labelId: undefined,
+    onHand: false,
   });
 
   function reset() {
@@ -26,6 +27,7 @@ export const useFoodData = function () {
     data.name = "";
     data.description = "";
     data.labelId = undefined;
+    data.onHand = false;
   }
 
   return {

frontend/composables/use-group-webhooks.ts

@@ -64,7 +64,6 @@ export const useGroupWebhooks = function () {
       newDt.setMinutes(Number(minutes));
 
       updateData.scheduledTime = `${pad(newDt.getUTCHours(), 2)}:${pad(newDt.getUTCMinutes(), 2)}`;
-      console.log(updateData.scheduledTime);
 
       const payload = {
         ...updateData,
@@ -85,7 +84,14 @@ export const useGroupWebhooks = function () {
       if (data) {
         this.refreshAll();
       }
+      loading.value = false;
     },
+
+    async testOne(id: string | number) {
+      loading.value = true;
+      await api.groupWebhooks.testOne(id);
+      loading.value = false;
+    }
   };
 
   const webhooks = actions.getAll();

frontend/composables/use-shopping-list-item-actions.ts

@@ -0,0 +1,223 @@
+import { computed, reactive, watch } from "@nuxtjs/composition-api";
+import { useLocalStorage } from "@vueuse/core";
+import { useUserApi } from "~/composables/api";
+import { ShoppingListItemOut, ShoppingListOut } from "~/lib/api/types/group";
+import { RequestResponse } from "~/lib/api/types/non-generated";
+
+const localStorageKey = "shopping-list-queue";
+const queueTimeout = 5 * 60 * 1000;  // 5 minutes
+
+type ItemQueueType = "create" | "update" | "delete";
+
+interface ShoppingListQueue {
+  create: ShoppingListItemOut[];
+  update: ShoppingListItemOut[];
+  delete: ShoppingListItemOut[];
+
+  lastUpdate: number;
+}
+
+interface Storage {
+  [key: string]: ShoppingListQueue;
+}
+
+export function useShoppingListItemActions(shoppingListId: string) {
+  const api = useUserApi();
+  const storage = useLocalStorage(localStorageKey, {} as Storage, { deep: true });
+  const queue = reactive(getQueue());
+  const queueEmpty = computed(() => !queue.create.length && !queue.update.length && !queue.delete.length);
+  if (queueEmpty.value) {
+    queue.lastUpdate = Date.now();
+  }
+
+  storage.value[shoppingListId] = { ...queue }
+  watch(
+    () => queue,
+    (value) => {
+      storage.value[shoppingListId] = { ...value }
+    },
+    {
+      deep: true,
+      immediate: true,
+    },
+  )
+
+  function isValidQueueObject(obj: any): obj is ShoppingListQueue {
+    if (typeof obj !== "object" || obj === null) {
+      return false;
+    }
+
+    const hasRequiredProps = "create" in obj && "update" in obj && "delete" in obj && "lastUpdate" in obj;
+    if (!hasRequiredProps) {
+      return false;
+    }
+
+    const arraysValid = Array.isArray(obj.create) && Array.isArray(obj.update) && Array.isArray(obj.delete);
+    // eslint-disable-next-line @typescript-eslint/no-unsafe-argument
+    const lastUpdateValid = typeof obj.lastUpdate === "number" && !isNaN(new Date(obj.lastUpdate).getTime());
+
+    return arraysValid && lastUpdateValid;
+  }
+
+  function createEmptyQueue(): ShoppingListQueue {
+    const newQueue = { create: [], update: [], delete: [], lastUpdate: Date.now() };
+    return newQueue;
+  }
+
+  function getQueue(): ShoppingListQueue {
+    try {
+      const fetchedQueue = storage.value[shoppingListId];
+      if (!isValidQueueObject(fetchedQueue)) {
+        console.log("Invalid queue object in local storage; resetting queue.");
+        return createEmptyQueue();
+      } else {
+        return fetchedQueue;
+      }
+    } catch (error) {
+      console.log("Error validating queue object in local storage; resetting queue.", error);
+      return createEmptyQueue();
+    }
+  }
+
+  function removeFromQueue(itemQueue: ShoppingListItemOut[], item: ShoppingListItemOut): boolean {
+    const index = itemQueue.findIndex(i => i.id === item.id);
+    if (index === -1) {
+      return false;
+    }
+
+    itemQueue.splice(index, 1);
+    return true;
+  }
+
+  async function getList() {
+    const response = await api.shopping.lists.getOne(shoppingListId);
+    return response.data;
+  }
+
+  function createItem(item: ShoppingListItemOut) {
+    removeFromQueue(queue.create, item);
+    queue.create.push(item);
+  }
+
+  function updateItem(item: ShoppingListItemOut) {
+    const removedFromCreate = removeFromQueue(queue.create, item);
+    if (removedFromCreate) {
+      // this item hasn't been created yet, so we don't need to update it
+      queue.create.push(item);
+      return;
+    }
+
+    removeFromQueue(queue.update, item);
+    queue.update.push(item);
+  }
+
+  function deleteItem(item: ShoppingListItemOut) {
+    const removedFromCreate = removeFromQueue(queue.create, item);
+    if (removedFromCreate) {
+      // this item hasn't been created yet, so we don't need to delete it
+      return;
+    }
+
+    removeFromQueue(queue.update, item);
+    removeFromQueue(queue.delete, item);
+    queue.delete.push(item);
+  }
+
+  function getQueueItems(itemQueueType: ItemQueueType) {
+    return queue[itemQueueType];
+  }
+
+  function clearQueueItems(itemQueueType: ItemQueueType | "all", itemIds: string[] | null = null) {
+    if (itemQueueType === "create" || itemQueueType === "all") {
+      queue.create = itemIds ? queue.create.filter(item => !itemIds.includes(item.id)) : [];
+    }
+    if (itemQueueType === "update" || itemQueueType === "all") {
+      queue.update = itemIds ? queue.update.filter(item => !itemIds.includes(item.id)) : [];
+    }
+    if (itemQueueType === "delete" || itemQueueType === "all") {
+      queue.delete = itemIds ? queue.delete.filter(item => !itemIds.includes(item.id)) : [];
+    }
+    if (queueEmpty.value) {
+      queue.lastUpdate = Date.now();
+    }
+  }
+
+  function checkUpdateState(list: ShoppingListOut) {
+    const cutoffDate = new Date(queue.lastUpdate + queueTimeout).toISOString();
+    if (list.updateAt && list.updateAt > cutoffDate) {
+      // If the queue is too far behind the shopping list to reliably do updates, we clear the queue
+      console.log("Out of sync with server; clearing queue");
+      clearQueueItems("all");
+    }
+  }
+
+  /**
+   * Processes the queue items and returns whether the processing was successful.
+   */
+  async function processQueueItems(
+    action: (items: ShoppingListItemOut[]) => Promise<RequestResponse<any>>,
+    itemQueueType: ItemQueueType,
+  ): Promise<boolean> {
+    let queueItems: ShoppingListItemOut[];
+    try {
+      queueItems = getQueueItems(itemQueueType);
+      if (!queueItems.length) {
+        return true;
+      }
+    } catch (error) {
+      console.log(`Error fetching queue items of type ${itemQueueType}:`, error);
+      clearQueueItems(itemQueueType);
+      return false;
+    }
+
+    try {
+      const itemsToProcess = [...queueItems];
+      await action(itemsToProcess)
+        .then(() => {
+          if (window.$nuxt.isOnline) {
+            clearQueueItems(itemQueueType, itemsToProcess.map(item => item.id));
+          }
+        });
+    } catch (error) {
+      console.log(`Error processing queue items of type ${itemQueueType}:`, error);
+      clearQueueItems(itemQueueType);
+      return false;
+    }
+
+    return true;
+  }
+
+  async function process() {
+    if(queueEmpty.value) {
+      queue.lastUpdate = Date.now();
+      return;
+    }
+
+    const data = await getList();
+    if (!data) {
+      return;
+    }
+    checkUpdateState(data);
+
+    // We send each bulk request one at a time, since the backend may merge items
+    // "failures" here refers to an actual error, rather than failing to reach the backend
+    let failures = 0;
+    if (!(await processQueueItems((items) => api.shopping.items.deleteMany(items), "delete"))) failures++;
+    if (!(await processQueueItems((items) => api.shopping.items.updateMany(items), "update"))) failures++;
+    if (!(await processQueueItems((items) => api.shopping.items.createMany(items), "create"))) failures++;
+
+    // If we're online, or the queue is empty, the queue is fully processed, so we're up to date
+    // Otherwise, if all three queue processes failed, we've already reset the queue, so we need to reset the date
+    if (window.$nuxt.isOnline || queueEmpty.value || failures === 3) {
+      queue.lastUpdate = Date.now();
+    }
+  }
+
+  return {
+    getList,
+    createItem,
+    updateItem,
+    deleteItem,
+    process,
+  };
+}

frontend/composables/use-users/preferences.ts

@@ -6,6 +6,7 @@ export interface UserPrintPreferences {
   imagePosition: string;
   showDescription: boolean;
   showNotes: boolean;
+  showNutrition: boolean;
 }
 
 export interface UserSearchQuery {

frontend/lang/dateTimeFormats/af-ZA.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ar-SA.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/bg-BG.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/ca-ES.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/cs-CZ.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/el-GR.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/en-GB.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/es-ES.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}

frontend/lang/dateTimeFormats/fi-FI.json

@@ -18,4 +18,4 @@
     "hour": "numeric",
     "minute": "numeric"
   }
-}
+}