Part 3 - Configure Yellow Lite

Owned by Michael Gysel
Last updated: Feb 01, 2018
2 min read

As a result of Part I and Part II you have a Running Raspberry PI that captures images in a regular interval. In this part we are going to enhance the configuration to publish the images to a platform of your choice.

All configurations have to be added to the application.properties file on the Desktop.

sudo leafpad ~/Desktop/application.properties

Please remember to restart the `yellow` service to apply any configuration change.

sudo service yellow restart

Change the schedule

Image captures are triggered by a Quartz Cron expression. Cron allows flexible time and date based triggers. Please consult the Quartz documentation for a reference of the format.

The default configuration triggers every 15 minutes from 6:00 to 21:45.

capture.cron=0 */15 6-21 * * ?

Upload images to an FTP server

You can upload the images to your website using FTP. The images will be called LatestImage.jpg and Yellow Lite will always override the previous image with the newer version. If you want to archive images, we recommend uploading your images to Amazon S3.

# FTP
ftp.active=true
ftp.folder=publish_html/webcam
ftp.user=user
ftp.password=password
ftp.host=mywebsite.com

If your hosting provider also supports SFTP, we strongly recommend SFTP over FTP as the latter is neither robust nor secure.

# SFTP
sftp.active=true
sftp.folder=
sftp.user=
sftp.password=
sftp.host=

Publish to Teleport

Teleport is a webcam publishing platform offering public and private feeds including live Time Lapse videos starting from 5$ per feed and month.

# Teleport (FTP)
teleport.active=true
teleport.user=
teleport.password=

Publish to Amazon S3

Amazon S3 is a very powerful file storage platform and supports private as well as public image storage and automatic content expiration. If you want to keep your images for a certain number of days, Amazon S3 would be a very good platform to use then. The configuration of the authentication key and the S3 bucket will require some familiarity with the AWS platform though.

# S3
aws.s3.active=false
aws.s3.accessKey=
aws.s3.secretKey=
aws.s3.bucket=