paperless-ai helm

No introduction found. Create it?

Install

Install with:

helm repo add app-template oci://ghcr.io/bjw-s/helm/
helm install paperless-ai app-template/app-template -f values.yaml

Examples

See examples from other people.

Top Repositories (2 out of 11)

NameRepoStarsVersionTimestamp
paperless-airafaribe/home-ops653.7.36 days ago
paperless-aidrag0n141/home-ops323.7.36 days ago

Values

See the most popular values for this chart:

KeyTypes
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
boolean
string
boolean
string
controllers.main.containers.main.image.tag (2)
2.7.6@sha256:c8ec15eccd08fe550d227297baf85130d375215196b40d2a9dd60fa62a41573e
string
string
string
string
string
string
string
string
controllers.main.containers.paperless-ai.env.CUSTOM_API_URL (1)
https://generativelanguage.googleapis.com/v1beta/openai
string
controllers.main.containers.paperless-ai.env.CUSTOM_FIELDS (1)
{"custom_fields":[{"value":"Betrag","data_type":"monetary","currency":"EUR"},{"value":"IBAN","data_type":"string"},{"value":"Verwendungszweck","data_type":"string"},{"value":"Empfänger","data_type":"string"}]}
string
string
string
string
controllers.main.containers.paperless-ai.env.PAPERLESS_API_URL (1)
http://paperless-paperless-ngx.productivity.svc.cluster.local/api
string
string
string
string
controllers.main.containers.paperless-ai.env.SYSTEM_PROMPT (1)
You are a personalized document analyzer. Your task is to analyze documents and extract relevant information. Analyze the document content and extract the following information into a structured JSON object: 1. title: Create a concise, meaningful title for the document. 2. correspondent: Identify the sender or institution but do not include addresses. 3. tags: Select up to 4 relevant thematic tags. Prefer existing tags, but create new ones if necessary. 4. document_date: Extract the document date in the format YYYY-MM-DD. 5. language: Determine the document language, using 'de' for German, 'en' for English, or 'und' if unclear. 6. document_type: Assign only an existing document type classification. Do not create new classifications. For tags: Select up to 4 tags per document, fewer if sufficient. Prefer existing tags. Only create a new tag if no suitable one exists. Avoid overly generic or too specific tags. Use the language of the document. - Apply the tag 'Honorar' ONLY if the document indicates that the user is RECEIVING money (e.g., payment confirmations, fee agreements, invoices issued by the user). - DO NOT apply 'Honorar' for normal invoices that require payment by the user. For the title: Keep it short and concise without addresses. Include the most important identification features. For invoices or orders, mention the invoice or order number if available. Use the language of the document. For the correspondent: Check the existing correspondent list first. If a match is found, use the existing correspondent. Only create a new correspondent if no suitable match exists. Use the shortest possible form of the company name, for example, Amazon instead of Amazon EU SARL German branch. For the document date: Extract the most relevant date from the document. Use the format YYYY-MM-DD. For the language: Determine the document language. Use language codes like de for German or en for English. If the language is not clear, use und as a placeholder. For document type classification: Use only predefined document type classifications. Do not create new ones. If no matching classification exists, leave it empty rather than inventing a new one. If applicable, extract and populate the predefined custom fields: Betrag, IBAN, Verwendungszweck und Empfänger. These fields should only be set for invoices and must not be included for other document types.
string
string
string
string
string
string
string
string
string
string
string
string
string
number
string
string
number
string
number
string
number
string
string
boolean
string
string
string
string
string
string
string
string
string
string
string
string
string
number
string
number
boolean
number
string
string
string
string
string
ingress.app.hosts[].host (5)
paperless-ai.${SECRET_DOMAIN}
string
string
string
string
ingress.app.tls[].hosts[] (4)
- paperless-ai.${SECRET_DOMAIN}
string
ingress.app.tls[].secretName (3)
wildcard-internal-${SECRET_DOMAIN/./-}-tls
string
boolean
string
string
string
string
string
string
string
string
string
string
ingress.main.hosts[].host (4)
paperless-ai.${SECRET_DOMAIN}
string
string
string
string, number
string
string
string
string
string
string
string
string
string
string
boolean
ingress.main.tls[].hosts[] (1)
- paperless-ai.casalani.de
string
route.app.hostnames[] (2)
- {{ .Release.Name }}.kokoro.wtf
string
string
string
string
string
number