This has a bunch of parameters. These parameters can be set on the command line, or in .rc files located at:

• /etc/appt.mysqlrc -- System defaults
• ~/.appt.mysqlrc -- User defaults
• ./.appt.mysqlrc -- User defaults for a specific directory

• --host=picard.peak.org -- Defines the host with the webcal SQL database.
• --database=webcal -- Defines the table with the webcal information.
• --user=regan -- Defines the user who has read access to the webcal information.
• --password=password -- Defines the password used to access the database.
• --calname=CalendarName -- Defines the webcal calendar name to use. This can be a comma separated list of calendar names.
• --help -- Print help information.
• --debug -- Turns on some debugging output.

You can pick up the entire archive for version v0.03. This contains all of the files mentioned on this page.

Once you have the tar file, you will need to extract and build it. Do something like the following:

	cd
	mkdir appt.mysql
	tar xvfz appt.mysql-0.03.tar.gz
	cd appt.mysql-0.03
	make

Limitations and deficiencies:

To present data, this program reaches straight into the SQL database. The table which stores the information, stores it for all users of the calendar. Thus, if a user has read access to the SQL database, they can get the calendar information for any user of webcal. If this doesn't fit your security requirements, then don't use this program. A possible way around this is to use HTTP to ask the webcal program for the necessary information. That would be rather ugly.

Webcal has a way to make recurring appointments, and appointments spanning multiple days. This information is not processed.

The mkappt.mysql program (not yet written) cannot be allowed to have complete write access to the SQL table. That's just asking for mischief. So the data is presented to the webcal program via HTTP. This isn't the fastest access, but is reasonable.