Full ALPR Database System for Blue Iris!

I think the code is stable, and Charlie hasn't had time to add new features. Maybe he'll come back or someone else will take up the challenge?
I just want to know that Charlie (@algertc) is okay. I know he was having health scares and a lot of life changes, a move, a new job and other pressures. Hopefully he'll stop by and give us an update.
 
I just want to know that Charlie (@algertc) is okay. I know he was having health scares and a lot of life changes, a move, a new job and other pressures. Hopefully he'll stop by and give us an update.
Ditto this.

But I'll also say that this ALPR application and database is exactly the kind of coding that AI excels at. And it's open source. To wit, scroll back a few pages and see the security hole that my Claude was able to detect and fix.

If anyone wants to throw some tokens at algertc's project, I'm sure it could add some of the requested features, easily.
 
Ditto this.

But I'll also say that this ALPR application and database is exactly the kind of coding that AI excels at. And it's open source. To wit, scroll back a few pages and see the security hole that my Claude was able to detect and fix.

If anyone wants to throw some tokens at algertc's project, I'm sure it could add some of the requested features, easily.
Charlie was in the process of creating a "Gen 2" version with a new database, a notification/rules engine, etc. and said he was very close. Anyone know if that is available to view and start testing? Maybe he can just jump into this conversation for a moment and give us an update and perhaps the best steps to offload the workload from him?

I know he said he doesn't have an active ALPR setup, but the rest of us do and would gladly give the gen 2 a go.

And with a little guidance from him on how to set up a dev environment, maybe a few of us could start learning and improving that version?
 
Ditto this.

But I'll also say that this ALPR application and database is exactly the kind of coding that AI excels at. And it's open source. To wit, scroll back a few pages and see the security hole that my Claude was able to detect and fix.

If anyone wants to throw some tokens at algertc's project, I'm sure it could add some of the requested features, easily.
GitHub - prsmith777/ALPR-Database-Community: Fully-Featured Automated License Plate Recognition Database Platform for Blue Iris + CodeProject AI Server



Ive been on this for over a month with Codex. Ive added tons of stuff and its working well but its kind of specialized for my setup so I dont know if it would work for others. I also have no idea how it could be implemented by others...sorry Im new at all this
 
He has not signed in since June 8th.
 
Somehow part of your database schema didn't get updated to the latest version. Try manually reapplying the schema.sql and migrations.sql.
  • Grab the updated schema.sql and migrations.sql directly from the ALPR-Database GitHub Repository.
    Move the fresh files into your local host directory mapped to the container.
    Access your database container console and run:
    psql -U postgres -d postgres -f /migrations/migrations.sql
I got it working by manually modifying the schema. I know next to nothing about sql, but I kept feeding the results into Google's AI, and, the REALLY scary thing is, after doing everything it suggested, I flipping got it working.
 
GitHub - prsmith777/ALPR-Database-Community: Fully-Featured Automated License Plate Recognition Database Platform for Blue Iris + CodeProject AI Server



Ive been on this for over a month with Codex. Ive added tons of stuff and its working well but its kind of specialized for my setup so I dont know if it would work for others. I also have no idea how it could be implemented by others...sorry Im new at all this
I've been using this fork for about 2 weeks now, it added a lot of features and functionality on top of the algertc/ALPR-Database. Things like future plate correction, viewing 500 results all at once, the expansion of rules and many more!

Thank you prsmith777!
 
How would one switch to this new fork?
Save whatever you want from the old ALPR, it will not migrate to the new ALPR.

I log into my docker,

I ran below to see what the CONTAINER ID are for both ALPR and postgres 13.
Code:
sudo docker ps -a

Copy the CONTAINER ID for one at a time for both, then paste the CONTAINER ID into the code and run it to stop both ALPR and postgres 13
Code:
sudo docker stop CONTAINER ID

Then I ran these according to GitHub - prsmith777/ALPR-Database-Community: Fully-Featured Automated License Plate Recognition Database Platform for Blue Iris + CodeProject AI Server

Code:
sudo git clone https://github.com/prsmith777/ALPR-Database-Community.git

Code:
sudo cd ALPR-Database-Community

Code:
sudo git checkout

approved-commit above

Code:
sudo docker build --tag alpr-dashboard:local .

Then run

Code:
sudo mkdir -p auth config logs storage

and

Code:
sudo cp .env.example to .env

Code:
sudo nano .env

fill in both passwords, CTRL Z then save the file.

Code:
sudo docker compose up -d.

Verify the new ALPR is up and running using the same url as the old ALPR.

Then you can delete the old ALPR and postgres 13 if you choose with.

Code:
sudo docker rm CONTAINER ID
 
Last edited:
Save whatever you want from the old ALPR, it will not migrate to the new ALPR.

I log into my docker,

I ran below to see what the CONTAINER ID are for both ALPR and postgres 13.
Code:
sudo docker ps -a

Copy the CONTAINER ID for one at a time for both, then paste the CONTAINER ID into the code and run it to stop both ALPR and postgres 13
Code:
sudo docker stop CONTAINER ID

Then I ran these according to GitHub - prsmith777/ALPR-Database-Community: Fully-Featured Automated License Plate Recognition Database Platform for Blue Iris + CodeProject AI Server

Code:
sudo git clone https://github.com/prsmith777/ALPR-Database-Community.git

Code:
sudo cd ALPR-Database-Community

Code:
sudo git checkout

approved-commit above

Code:
sudo docker build --tag alpr-dashboard:local .

Then run

Code:
sudo mkdir -p auth config logs storage

and

Code:
sudo cp .env.example to .env

Code:
sudo nano .env

fill in both passwords, CTRL Z then save the file.

Code:
sudo docker compose up -d.

Verify the new ALPR is up and running using the same url as the old ALPR.

Then you can delete the old ALPR and postgres 13 if you choose with.

sudo docker rm CONTAINER ID
Thanks for this detailed information.

Would there be a way to install this as a separate instance so I could run old and new in parallel?

You say to save the existing data because it won't migrate, but are there any details on the database differences. I'm not ready to lose all my existing data and would be willing to figure out a manual migration if needed.
 
You say to save the existing data because it won't migrate, but are there any details on the database differences. I'm not ready to lose all my existing data and would be willing to figure out a manual migration if needed.

Oh, I mean write down the "Known Plates", "MQTT server", and all the other information you want to keep. Above my pay grade to merge data from the two APR together.


Would there be a way to install this as a separate instance so I could run old and new in parallel?
You'll need another IP address, I'd would just install another Debian linux VM in my Proxmox virtual host, I don't know your setup so this is as far as I can help you.
 
Oh, I mean write down the "Known Plates", "MQTT server", and all the other information you want to keep. Above my pay grade to merge data from the two APR together.



You'll need another IP address, I'd would just install another Debian linux VM in my Proxmox virtual host, I don't know your setup so this is as far as I can help you.
This is the sort of task that Claude Code (and other AIs) excel at. Just be very clear up front that you want the AI to "plan before execute" so you can "review the plan" and do a "dry run before migration" and "run both in parallel" before retiring the original application. If you're explicit about these things, there is very little risk of data loss (e.g. lower than you doing it manually).

I will be doing this in about a week's time after I have Claude assist me with virtualizing the 3rd of my 3 installations, after it did an outstanding job on the first two.