cd C:\Users\cleme\platform-tools-latest-windows\platform-tools
adb connect 192.212.5.102
adb shell reboot
paperless-AI
Prompt:
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/institution, excluding addresses.
3. TAGS: Select from 4 to 10 relevant thematic tags.
4. DOCUMENT_DATE: Extract the document date (format: YYYY-MM-DD).
5. DOCUMENT_TYPE: Determine the precise type that classifies the document (e.g., Invoice, Contract, Employer, Information, etc.).
6. LANGUAGE: Determine the document language (e.g., "de" for German, "en" for English, etc.).
IMPORTANT RULES FOR THE ANALYSIS:
- FOR TAGS:
- FIRST, remove all tags except "testAi."
- One tag must refer to the receiver of the document.
- Choose only relevant categories and select between 4 and 10 tags (6 minimum if possible).
- Avoid generic or overly specific tags.
- Use only the most important information to generate the tags.
- FOR THE TITLE:
- Keep it short and concise—NO ADDRESSES.
- Include the most important identifying features.
- For invoices or orders, mention the invoice/order number if available.
- FOR THE CORRESPONDENT:
- Identify the sender or institution.
- Use the shortest form possible for the company name (e.g., "Amazon" instead of "Amazon EU SARL, German branch").
- FOR THE DOCUMENT DATE:
- Extract the document's date in the format YYYY-MM-DD.
- If there are multiple dates, use the most relevant one (e.g., the signing date).
- FOR THE LANGUAGE:
- Identify the language of the document.
- Use language codes such as "de" for German or "en" for English.
- If the language is unclear, use "und" as a placeholder.
The output language will be FRENCH.
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/institution but do not include addresses
3. tags: Select up to 10 relevant thematic tags
4. document_date: Extract the document date (format: YYYY-MM-DD)
5. document_type: Determine a precise type that classifies the document (e.g. Invoice, Contract, Employer, Information and so on)
6. receiver: Identify the receiver of the document and put it into "CustomAiField"
Important rules for the analysis:
For tags:
- Use only relevant categories
- Maximum 10 tags per document, less if sufficient (at least 6)
- Avoid generic or too specific tags
- Use only the most important information for tag creation
- The output language is FRENCH
For the title:
- Short and concise, NO ADDRESSES
- Contains the most important identification features
- For invoices/orders, mention invoice/order number if available
- The output language is FRENCH
For the correspondent:
- Identify the sender or institution
When generating the correspondent, always create the shortest possible form of the company name (e.g. "Amazon" instead of "Amazon EU SARL, German branch")
For the document date:
- Extract the date of the document
- Use the format YYYY-MM-DD
- If multiple dates are present, use the most relevant one (e.g., the signing date).
The output language will be FRENCH.
install frigate
Installation :
https://www.hacf.fr/installation-frigate-proxmox/
https://community-scripts.github.io/ProxmoxVE/scripts?id=frigate
sudo apt -y install nfs-common
sudo apt -y install cifs-utils
sudo mkdir /Ftp
sudo nano /etc/fstab
//192.212.5.111/40-Ftp /Ftp cifs rw,credentials=/root/.sharelogin,nobrl,_netdev,uid=1000,gid=1000 0 0
sudo ln -s /Ftp/frigate /media/
in ha:
What’s the best way to run Docker in Proxmox?
add guest agent
gtl
home assistant plan
home assistant manual certificat
Controle Home assistant with Google Assitant
low space
On my server (with docker) i have sometime the space of the root directory to 0%
df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 86M 11M 75M 13% /run
/dev/sda2 20G 20G 0 100% /
tmpfs 476M 0 476M 0% /dev/shm
tmpfs 5,0M 0 5,0M 0% /run/lock
192.212.40.6:/6-40-SystemSvg 227G 32G 184G 15% /SystemSvg
192.212.40.6:/9-VideoClub 1,8T 774G 967G 45% /VideoClub
tmpfs 146M 8,0K 146M 1% /run/user/1000
docker clean non essential stuff
docker system prune -a
docker volume rm $(docker volume ls -qf dangling=true)
docker system prune --all --volumes --force
empty trash
rm -rf ~/.local/share/Trash/*
or
sudo apt install trash-cli
trash-empty
system clean sweep
sudo apt-get autoremove
sudo apt-get clean
sudo apt-get autoclean
find big stuff in file system
sudo du -h --max-depth=1 | sort -h
0 ./dev
0 ./proc
0 ./sys
4,0K ./cdrom
4,0K ./media
4,0K ./mnt
4,0K ./srv
4,0K ./VideoClub
16K ./lost+found
16K ./opt
52K ./root
60K ./home
68K ./tmp
1,3M ./run
6,7M ./etc
428M ./boot
823M ./SystemSvg
1,7G ./snap
4,7G ./var
9,9G ./usr
20G .
limit log in container
<service_name>
logging:
options:
max-size: "10m"
max-file: "5"
/etc/docker/daemon.json
{
"log-opts": {
"max-size": "10m",
"max-file": "5"
}
}
dont forget the “,” if they have allready param in daemon.json