Version 1 (modified by 11 years ago) (diff) | ,
---|
FedCam
Federated Cameras
This is a rough outline of the moving pieces of fedcam.
camera hosts
Our set up has four camera hosts, two in each cabinet. (front and back).
- Telehouse: ken (front) and negri (back)
- XO: luisa and ottorene
The files on each host server lives in /srv/motion/cam0/
These machines are running the motion daemon, and the main config file is /etc/motion/motion.conf
.
Each of these machines will need a series of files put in place, and specified in the motion configs.
All of this needs to be put into...
Puppet
There needs to be a puppet module, or modules.
One set of configs for the camera hosts, and another set of configs for the remote host (in this case jojobe
).
The camera hosts need:
- event start script
- frame write script
- event end script
- etc conf.
The web host needs:
- the web app files
- sqlite3 installed, and blank db created
- cron job to delete data tagged for deletion.
Other Tasks that need completeing
jojobe
Mod Auth openid needs to be enabled on jojobe, and the fedcam software needs to be updated to use that in the .htaccess.
set up the sqlite3 db on the jojobe
build file structure:
files/telehouse/front files/telehouse/back files/XO/front files/XO/back
Remember the dir names get read as meaningful values by the web app, so name em right.
fedcam software
Update to work with OpenID auth
on the individual camera hosts
Add the config file to /etc/fedcamrc
create the ~/.ssh/masters file for the motion user.
Add the push-frame script Add the event end script
Add the motion cleanup script