Install Appaserver ©Tim Riley

Apache Group ©Tim Riley Add yourself to the apache group. Both the apache user and group are called “www-data”. This step is optional. However, having group-centric security is completely secure and most flexible. Equally effective, you could add yourself to the “admin” group, or you could create an “appaserver” group. If you do either, remember to add the apache username (www-data) to this group. Log back in for this to take effect.

Appaserver generates many temporary files. Therefore, it should be installed in /var. Ideally, /var should be on its own filesystem. /etc/profile ©Tim Riley Set these global environment variables in /etc/profile. Appending dot to your path is safe and convenient.

/etc/profile ©Tim Riley This step is optional. However, having group-centric security is completely secure and most flexible. If /var is on its own filesystem, then links to cgi-bin need to be symbolic. Remember to source this file before proceeding.

/usr/lib/cgi-bin ©Tim Riley The s-bit on a directory's group says: for all new files and subdirectories, set the group name to the directory's group, not the default group of the user creating the file or subdirectory. Set permissions for the $CGI_HOME directory. Remember, this might be either “admin” or “appaserver” group. Leave world access to read and execute. Virtual hosts run as other user IDs, so they need to execute here.

/var/www ©Tim Riley Set permissions for the $DOCUMENT_ROOT directory. Remember, this might be either “admin” or “appaserver” group.

/var/appaserver ©Tim Riley Create the appaserver directory. Remember, this might be either “admin” or “appaserver” group. Remember,this must match “APPASERVER_HOME=” in /etc/profile.

/var/appaserver ©Tim Riley Point your browser to the download directory. Make a note of the latest version of appaserver.

/var/appaserver ©Tim Riley Download the latest version of appaserver. Change directory to APPASERVER_HOME

/var/appaserver ©Tim Riley Untar it. First, make sure you're in either an empty directory or an appaserver directory. The tar file doesn't have a root directory.

Compile Appaserver ©Tim Riley Compile appaserver.

Compile Appaserver ©Tim Riley Successful compilation.

Directory /var/log/appaserver ©Tim Riley Make the appaserver log file directory. Have it participate in the group-centric paradigm. Remember, this might be either “admin” or “appaserver” group.

File appaserver.err ©Tim Riley Create the old appaserver error file. Some computer programs still send messages here.

©Tim Riley Create the first appaserver application error file. Each application gets its own error file. Appaserver Error File

Appaserver Configuration File ©Tim Riley Copy the appaserver configuration template to /etc/appaserver.config, then secure it. Remember, this might be either “admin” or “appaserver” group.

Appaserver Configuration File ©Tim Riley Edit the appaserver configuration file. You should only need to set the MySQL password.

Appaserver Configuration File ©Tim Riley Make sure MySQL works. Make sure sql works.

Create Database ©Tim Riley Create the template database.

Appaserver Configuration File ©Tim Riley Set the default database to template. Edit /etc/appaserver.config

Create Template Application ©Tim Riley Get the create and insert template SQL statements.

Create Application Table ©Tim Riley Run the create and insert template SQL statements.

Upgrade Appaserver Database ©Tim Riley Execute the upgrade scripts just in case any database changes were made.

Link to /var/www ©Tim Riley Apache only sees what is inside of $DOCUMENT_ROOT. Make these five directories available to apache. You may have to add “Options FollowSymLinks” to your apache configuration file. Appaserver's horizontal menu is accomplished with Dynarch's hmenu. However, hmenu is no longer supported. The hmenu version deployed is an unlicensed, trial version. Two attempts to contact the author about purchasing a distribution license went unanswered. To use the vertical menu instead, set frameset_menu_horizontal_yn to 'n' in the template_application table.

Create /var/appaserver/data ©Tim Riley Create the data directory and secure it.

Link icons to /var/www ©Tim Riley Two operations have icons: delete and detail. Make these icons available to apache. At the botton-left corner of each frame, a “Top” button appears. Make this icon available to apache.

Login Screen ©Tim Riley Point your browser to template. Login with nobody/changeit.

Welcome To Appaserver ©Tim Riley Become role=System. If something is wrong, then check: 1) /var/log/appaserver/appaserver_template.err 2) /var/log/apache2/error.log

Add Yourself ©Tim Riley Choose the menu sequence:

Add Yourself ©Tim Riley Enter your user name information. A convenient mechanism to generate passwords is to allow the user to log in with the password of “changeit”. Then instruct the user to run Change Password. This flag overrides APPLICATION.frameset_menu_horizontal_yn. Press

Add Yourself ©Tim Riley The bottom frame automatically displays the Role Appaserver User table, ready for inserting. Assign yourself to the System role. Press

Add Yourself ©Tim Riley You're in!

Log In As Yourself ©Tim Riley Remember? Your password is “changeit”.

Deactivate User=nobody ©Tim Riley Choose

Deactivate User=nobody ©Tim Riley Query where login_name = 'nobody'

Deactivate User=nobody ©Tim Riley Delete the password. An empty password prevents logging in.

Deactivate User=nobody ©Tim Riley Press

Change Your Password ©Tim Riley Choose the process “Change Password.”

Change Your Password ©Tim Riley Type in and confirm your new password. Press

Create Empty Application ©Tim Riley Select

Create Empty Application ©Tim Riley The Destination Application becomes the database name. So, only letters and numbers.

Create Empty Application ©Tim Riley Set the default database in /etc/appaserver.config. The executable “sql” will now connect to your new database.

Create Empty Application ©Tim Riley You can override the default database by setting $DATABASE.