Plazza — Admin Manual

This page documents operational and administrative tasks for the Plazza calendar service. It assumes shell access to the server.

Service Control

sudo systemctl restart plazza.service

sudo journalctl -u plazza.service -n 100 --no-pager

sudo systemctl daemon-reload

You do not need daemon-reload for code changes — only when the service file itself changes.

/home/david/plazza/plazza.db

sqlite3 plazza.db ".tables"

sqlite3 plazza.db "
select id, name, source_key, is_featured, is_active
from venues
order by name;
"

sqlite3 plazza.db "
select id, name, email
from users
order by id;
"

Featured venues determine what guests see by default. This is controlled by the is_featured column on venues.

./set_featured.py

This script:

Scrapers populate events and ensure venues exist.

./scrape_all.sh


python3 scrape_davis_library.py
python3 scrape_clark_ics.py
python3 scrape_eccles.py
python3 scrape_pioneer.py

Scrapers call ensure_venue(), which updates venue names, URLs, and featured status automatically.

sqlite3 plazza.db "
delete from users where id = 3;
"

sqlite3 plazza.db "
update venues set is_active = 0 where source_key = 'example_venue';
"

Avoid deleting venues outright — events and subscriptions reference them.