DEV Community: Mitch Jackson

csh - simple helper for urxvt

Mitch Jackson — Mon, 04 May 2020 21:54:00 +0000

This shell script provides quick SSH shortcuts, and displays a configurable terminal background color while connected.

!/bin/csh

#!/bin/bash
#
# cssh: Color SSH helper
#
# Author: Mitch Jackson <mitch@mitchjacksontech.com
# Copyright: 
#
# Set the terminal background color and transparency before
# making an SSH connection, then resets them when the connection closes
#
# Allows for configuring different background colors per host,
# along with connetion aliases

# background color and opacity value to use during the session
CONN_BGCOLOR="#330000"
CONN_OPACITY=85

# background color and opacity to return to after the session ends
EXIT_BGCOLOR="#000000"
EXIT_OPACITY=70

# Connection Definitions:
#
# Define a shortname for each connection below
case $1 in
  box1)
    SSH_HOST="box1.lion.land"
    ;;
  box2)
    SSH_HOST="10.0.0.2"
    CONN_BGCOLOR="#002200"
    ;;

  *) # Catch-all
    SSH_HOST="$1"
    CONN_BGCOLOR="#000333"
    ;;
esac

printf '\33]11;%s\007' "[$CONN_OPACITY]$CONN_BGCOLOR"
command ssh $SSH_HOST $2 $3 $4
printf '\33]11;%s\007' "[$EXIT_OPACITY]$EXIT_BGCOLOR"

Also, a simple script to set the terminal background color and opacity at any time

!/bin/tglow

#!/bin/bash
#
# tglow: Set terminal background and opacity
#
# Author: Mitch Jackson <mitch@mitchjacksontech.com
# Copyright: Nope

function usage() {
  echo
  echo "tglow: set terminal background and opacity"
  echo
  echo "    usage: tglow 30 green"
  echo "           tglow 95 \"#333000\""
  echo
  exit 1
}

if [[ -z "$1" ]] || [[ -z "${2+x}" ]]; then
  usage
fi

printf '\33]11;%s\007' "[$1]$2"

Perl 5.30 deprecates use of my() in a false conditional

Mitch Jackson — Mon, 10 Jun 2019 18:08:23 +0000

Perl 5.30.0 is released (changelog). With it comes a breaking change for me. It has been a long time since I've faced a breaking change with perl.

Deprecated use of my() in false conditional.

I have been using this deprecated syntax liberally like so:

# This syntax generates a fatal error in perl 5.30
#
# Initialize $foo
#   If $bar tests true, $foo = 'foobar'
#   If $bar tests false, $foo = undef
my $foo = 'foobar' if $bar;

There has been a long-standing bug in Perl that causes a lexical variable not to be cleared at scope exit when its declaration includes a false conditional.

This could make for interesting bugs. The scoped variable declared this way may unexpectedly persist data!

# Use this instead
my $foo;
if ( $bar ) {
  $foo = 'foobar';
}

# Or this
my $foo;
$foo = 'foobar' if $bar;

According to RT# 133543, the deprecation will not always be triggered with this syntax! Therefore, I feel I can't trust a run of a test suite under 5.30 to identify all the offending code statements.

Is anybody else surprised to learn this declaration pattern is problematic?

How Do You Decide to Plunge Into a Startup?

Mitch Jackson — Tue, 17 Jul 2018 06:13:53 +0000

I'm confident in the product. What other factors should I consider before giving significant time and resources into a startup as a minority owner with a majority share of the software/hardware development?

That familiar place we all arrive at as developers: Let's make a business out of this! It is often an educational time sink. You learn just how reliably yourself and your friends will work without pay to chase a dream.

I'm facing this question again! My friend, the CEO of a long-standing non-profit, made a software wish while we played board games on Thanksgiving. Hold my beer... Several months later, as a volunteer, I've rewritten large parts of their infrastructure, built and integrated custom hardware deployments based on small board computers, and provided whiz-bang new features that were a first for their market. There was much rejoicing. I sacrificed into my day-job billable hours more than I want to admit to make this happen.

Now somebody else in the same space wants the same capability, and they're shopping vendors.

The product is not just a website. There is hardware/software integration. Significant business integration. As well as live event support. Somebody would have to travel several countries supporting installations and providing training. That person would NOT be me.

Everybody involved in the company would be working in "side-job" capacity. There's not enough money in the beginning to support full time employees.

What factors would YOU consider before deciding to join with such a company? What steps would you make early, as the business is structured, to realize both success and a good financial position?

SMS Notifications with Perl and Twilio

Mitch Jackson — Thu, 14 Jun 2018 06:11:39 +0000

Twilio is beyond useful, and easy to integrate. It's one of those tools that, once you get started, you just can't stop using it. You can add SMS Notifications and password resets to your existing application in an afternoon.

I see several examples of Twilio usage on dev.to. But of course, none for Perl, until now.

First, the entire simple program:

#!/usr/bin/env perl
use v5.10;
use strict;
use warnings;
use LWP::UserAgent;

my %text_message = (
    From => '12513001300', # Me
    To   => '16198675309', # Jenny
    Body => 'Thank you for being a friend! Travel down the road and back again!'
);

my %credentials = (
    account_id => '____YOUR_ACCOUNT_SID_GOES_HERE____',
    auth_token => '____YOUR_AUTH_TOKEN_GOES_HERE____',
);

my %twilio = (
    # HTTP Authentication
    api_domain => 'api.twilio.com:443',
    api_realm  => 'Twilio API',

    # Keep your line length within 80 characters please!
    api_url    => 'https://api.twilio.com/2010-04-01/Accounts/'
                  . $credentials{account_id}
                  . '/Messages'
);

my $ua = LWP::UserAgent->new;
$ua->credentials(
    $twilio{api_domain},
    $twilio{api_realm},
    $credentials{account_id},
    $credentials{auth_token}
);

my $response = $ua->post( $twilio{api_url}, \%text_message );

say $response->is_success
    ? "Message delivered"
    : "Error: ".$response->decoded_content;

As this is a #beginner post, let's break this down statement by statement.

#!/usr/bin/env perl
use v5.10;
use strict;
use warnings;

Begin with a Shebang Line. If you execute this program from a shell, this is how the shell knows which interpreter to use for the program. #!/usr/bin/env perl has replaced the long in the tooth standard #!/usr/bin/perl with good reason.

Invoking use v5.10; here allows us to use the say function.

use strict and use warnings asks Perl to warn you if you're doing something stupid. Like misspelling a variable name, or blogging at 2am.

use LWP::UserAgent;

LWP::UserAgent can perform most actions your web browser does. You can use it to browse pages, click links, and POST forms. It can keep persistent cookies. If you wanted to, say, write a robot to cheat an online poll, look no further.

my %text_message = (
    From => '12513001300', # Me
    To   => '16198675309', # Jenny
    Body => 'Thank you for being a friend! Travel down the road and back again!'
);

Store information about your text message into a hash. You'll want to replace the example data with your own. Jenny's had enough phone harassment.

my %credentials = (
    account_id => '____YOUR_ACCOUNT_SID_GOES_HERE____',
    auth_token => '____YOUR_AUTH_TOKEN_GOES_HERE____',
);

You can find your Twilio account credentials in the Dashboard under Settings/General. Twilio offers test API access. You can use the test API to text yourself.

my %twilio = (
    # HTTP Authentication
    api_domain => 'api.twilio.com:443',
    api_realm  => 'Twilio API',

    # Keep your line length within 80 characters please!
    api_url    => 'https://api.twilio.com/2010-04-01/Accounts/'
                  . $credentials{account_id}
                  . '/Messages'
);

Information you need to send a request to the Twilio API. Twilio uses Basic HTTP Authentication. Here is the DOMAIN and REALM for this authentication scheme. The Twilio API URL contains your account SID, so the full API URL is concatenated here.

my $ua = LWP::UserAgent->new;
$ua->credentials(
    $twilio{api_domain},
    $twilio{api_realm},
    $credentials{account_id},
    $credentials{auth_token}
);

Instantiate a new instance of the LWP::UserAgent object, and set the credentials it will use for the HTTP Request to the Twilio API.

my $response = $ua->post( $twilio{api_url}, \%text_message );

$ua makes a HTTP POST request to $twilio{api_url}. The data from %text_message are sent as form values. This operation returns a HTTP::Response Object.

say $response->is_success
    ? "Message delivered"
    : "Error: ".$response->decoded_content;

This statement includes the ternary operator, a short-hand for an if-else block. (Side note: If you didn't know what a ternary operator was, or what it was called, and you saw this statement block in some code, how would you phrase your internet search to learn what this statement was doing? Let me know in the comments...)

$response->is_success returns true or false based on the HTTP Status Code returned by the web server.

If Twilio reports the request was successful, you see Message Delivered displayed in your terminal. If Twilio reports a problem, you will see the full response from the Twilio API displayed in your terminal.

See how easy Twilio is? Go build something...

Frankly, Twilio has made themselves so easy to use that most languages can break their use down to one-liners. You can easily deliver an SMS via the shell using curl.

If you ever meet a Twilio engineer, be sure to buy them a beer.

Are you still reading? Go build something!

Would you pay a data ransom?

Mitch Jackson — Sun, 03 Jun 2018 20:58:26 +0000

Ticketfly.com data breach

I was notified by Have I Been Pwned that my Name, E-Mail address, Mailing addresses and phone numbers were dumped publicly online as part of the ticketfly.com data ransom involving 26 million account records. Motherboard reports the attacker requested a ransom of 1BTC (~$7500). It's unclear if the request was ignored intentionally, or overlooked. In theory, it would have cost ticketfly.com $0.000288 to protect my customer record. Now the dark web knows I always buy tickets to see They Might Be Giants.

Would I pay the 1BTC ransom?

It's common advice that a blackmailer will never stop asking for more money. It's also safe to assume that just because the hacker doesn't publicly dump the data immediately, she/he will still be selling it on the black market.

However this is a low-cost ransom request. Paying the ransom may buy time to fix the vulnerability, and perhaps could have kept ticketfly online. I'm told that venues cannot buy, sell, or verify tickets for concerts this weekend. This is going to cause probably more than $7500 in damage to every ticketfly venue.

I'd would have paid the ransom.

What would you do?

Auto-generate a Database Schema Diagram

Mitch Jackson — Sat, 02 Jun 2018 03:34:14 +0000

Generate a Live Database Schema Diagram for your Catalyst Application

When building a web application, I always create a URL endpoint that generates a database schema diagram on the fly. This is a quick reference item that never gets old.

This approach can be used with any Perl web framework. The provided example is for the Catalyst Framework using a DBIx::Class ORM. This example provides the url http://mywebsite.com/dbdiagram


=head2 dbdiagram

Render an image representing the current data model

=cut

use SQL::Translator;
sub dbdiagram :Local :Args(0) {
    my ($self, $c) = @_;

    my $translator = SQL::Translator->new(
        parser => 'SQL::Translator::Parser::DBIx::Class',
        data   => $c->model('Ezn')->schema,
        producer => 'Diagram',
        producer_args => {
            output_type => 'png',
            title       => "My clever database diagram",
            add_color   => 1,
            font_size   => 'large',
        },
    ) or die SQL::Translator->error;

    $c->res->content_type('image/png');
    $c->res->body($translator->translate);
}

Don't Forget to restrict to authorized users!

Trac Install Guide

Mitch Jackson — Fri, 25 May 2018 03:06:19 +0000

Install Trac with Git on a Debian 9

Since I was documenting the process anyway, why not make my first post with dev.to a software install guide.

Trac is my favored project management environment

Trac has been around for a long time. I was using it before git existed. It's been stable and reliable all this time. Unlike all the big bloated tools out there these days like GitLab and Jira, Trac runs quite well on the cheapest virtual servers you can rent.

Features include:

Ticketing system
Milestone tracking
Time tracking
Git integration with repository browsing
Wiki
Automated notifications
CI integration
Low system requirements

About this guide

Most guides or walkthroughs of this sort are very basic. They try to get you there with the least amount of information possible. My approach to guides opposes this philosophy. Advanced users may choose to skip over extra information like firewall configuration, and setting up E-Mail forwarding.

It's assumed the shell commands presented will be run using sudo, or as root.

Prepare your server

Create a Digital Ocean droplet using Debian 9

Creating a server with Digital Ocean is quite straightforward. Trac can run comfortably on the $5/mo small DO droplet. Use my referral link and get $10 of free credit.

This guide was written using Digital Ocean. You may encounter very minor differences during install in another environment. However this guide should still get you there. If not, please let me know.

Configure DNS for your Trac server

An obvious candidate is trac.yourdomain.com. This uses that example domain name. Update DNS so your new domain name points to your server.

You will also need an SPF record, or most mail your server sends will be rejected as spam. This will probably be adequate for your use case:

TXT @ v=spf1 a -all

Update the server

aptitude -y update
aptitude -y upgrade

Configure hostname and domain name on your server

Override Digital Ocean auto-config of domain name

sed -i 's/^manage_etc_hosts: true$/manage_etc_hosts: False/' /etc/cloud/cloud.cfg

Set the system hostname

cat << EOF > /etc/hostname
trac
EOF

Edit /etc/hosts to set the system domain name

Find these lines

127.0.1.1 example.com droplet
127.0.1.1 localhost

Update for your trac domain name

127.0.1.1 trac.yourdomain.com trac
127.0.0.1 localhost

Do not use simply use your root domain, yourdomain.com. You must have a subdomain prepended, such as trac.yourdomain.com. Otherwise you will have trouble later in the guide, allowing Trac to send e-mail notifications

At this point, reboot your server, and confirm your domain name and hostname remain correct after reboots. Use the shell commands hostname and domainname.

Configure the firewall

Install and enable firewalld

aptitude -y install firewalld
systemctl enable firewalld
systemctl start firewalld
firewall-cmd --zone=public --add-interface=eth0
firewall-cmd --zone=public --add-interface=eth0 --permanent

Protecting SSH

Many people will advise you to jump through hoops to protect SSH on your linux server. Unless you really need SSH available to the whole world (you don't) use my simpler approach. Disallow SSH in your firewall, except for trusted ip addresses. Since the whole internet can't talk to your SSH port, there's no need for elaborate settings and blocking firewalls like fail2ban.

Repeat the following commands for every trusted IP address

# Repeat these commands for every trusted IP address
firewall-cmd --zone=trusted --add-source=1.2.3.4
firewall-cmd --zone=trusted --add-source=1.2.3.4 --permanent

Should you find yourself unable to connect to SSH, because your current IP address has not been added to the trusted list, this is no problem. Just visit your server dashboard at digitalocean.com. Select the Access menu item. You will see a big blue button that says Launch Console. This gives you shell access to your server over the web. Issue the above command to grant yourself access from your new IP address.

Disable SSH to the public internet

firewall-cmd --zone=public --remove-service=ssh
firewall-cmd --zone=public --remove-service=ssh --permanent

Allow websites hosted on your server through your firewall

firewall-cmd --zone=public --add-service=http
firewall-cmd --zone=public --add-service=http --permanent
firewall-cmd --zone=public --add-service=https
firewall-cmd --zone=public --add-service=https --permanent

Get a free SSL certificate free from Lets Encrypt

You want all interactions with Trac and Git to be secure. To do this, enforce https for all your web traffic. You will need a security certificate for this.

Your DNS records must be in place for this step

Depending on your domain registry, and how you manage your DNS records, it can take minutes to hours before your new DNS names appear to everybody on the internet. If you cannot ping your domain name (ping trac.yourdomain.com) you will need to wait a while before completing this step.

Use certbot to request an SSL certificate

Install certbot

aptitude -y install certbot

Stop your web server, if it's running. Certbot will prove you own this domain name by hosting it's own temporary web server. There are other ways to use certbot. Look at letsencrypt.org if you're interested.

systemctl stop apache2

Request an SSL certificate.

certbot certonly --standalone -n --agree-tos \
    -m youremail@yourdomain.com \
    -d trac.yourdomain.com

We will configure the server to use this certificate later. The certificate can be found at:
/etc/letsencrypt/live/trac.mydomain.com/*.pem

Configure a local mail server so Trac can send E-Mails

Install Exim

aptitude -y install exim4

Update the Exim config file to contain these directives:
/etc/exim4/update-exim4.conf.conf

dc_eximconfig_configtype='internet'
dc_eximconfig_other_hostnames='trac.yourdomain.com'

Do not specify yourdomain.com as dc_eximconfig_other_hostnames, or mail to @yourdomain.com addresses will never be delivered. Also, if the output of the domainname command is yourdomain.com instead of trac.yourdomain.com, mail to @yourdomain.com will never be delivered. This happens because exim will try to deliver the mail locally, instead of over the internet.

It's a good idea to create a root email alias on your server, so you receive notices from your server

cat << EOF >> /etc/aliases
root: youremail@yourdomain.com
EOF

Restart Exim to apply the changed configuration

systemctl restart exim4

Check that Exim correctly decides to send mail via the internet.

exim -bt yourname@yourdomain.com
exim -bt yourname
exim -bt root

Send a test e-mail

echo "Test email" | mail -s "testing new server" yourname@yourdomain.com

Watch your logs if there is a problem

tail -f /var/log/exim4/* &
tail -f /var/log/maillog &
journalctl -f &

Install software and dependencies

Install software via Debian packages.

aptitude -y install \
  apache2 \
  exim4 \
  git \
  libapache2-mod-wsgi \
  libmariadb-dev-compat \
  mariadb-server \
  python \
  python-pip

At the moment, Trac does not install properly for me using only debian packages. You'll use a python virtual environment to install the latest version of Trac and associated libraries

Create the project home

mkdir -p /var/www/trac

Spawn a virtual environment

pip install virtualenv
virtualenv /var/www/trac/virtualenv

Activate the virtual environment

source /var/www/trac/virtualenv/bin/activate

Install Trac and dependencies

pip install trac
pip install docutils
pip install babel
pip install pygments
pip install MySQL-python
pip install TracAccountManager

Setup MariaDB

Enable MariaDB

systemctl enable mariadb
systemctl start mariadb

Run the following command and answer the questions. You will set your database admin password here.

mysql_secure_installation

Create a database for Trac, with the following SQL statements at the database prompt. Of course, replace TRAC_DB_PASSWORD with a real password.

mysql -u root -p

> CREATE DATABASE trac DEFAULT CHARACTER SET utf8 COLLATE utf8_bin;
> GRANT ALL ON trac.* TO trac_db@localhost IDENTIFIED BY 'TRAC_DB_PASSWORD';
> FLUSH PRIVILEGES;

# Press CTRL-D to exit database shell

Create a bare Git repository

mkdir -p /var/www/trac/git
git init --bare /var/www/trac/git/myproject.git

Trac Set-up

Initialize a Trac project

# Initalize a trac project
trac-admin \
  /var/www/trac/project \
  initenv project \
  mysql://trac_db:TRAC_DB_PASSWORD@localhost/trac \
  git /var/www/trac/git/myproject.git

Update Trac.ini

Make the following changes to the Trac project config file
/var/www/trac/project/conf/trac.ini

Add the following sections

[components]
tracopt.versioncontrol.git* = enabled
tracopt.versioncontrol.git.git_fs.csetpropertyrenderer = enabled
tracopt.versioncontrol.git.git_fs.gitconnector = enabled
tracopt.versioncontrol.git.git_fs.gitwebprojectsrepositoryprovider = enabled
acct_mgr.admin.* = enabled
acct_mgr.api.* = enabled
acct_mgr.db.sessionstore = disabled
acct_mgr.htfile.htdigeststore = disabled
acct_mgr.htfile.htpasswdstore = enabled
acct_mgr.http.* = disabled
acct_mgr.notification.* = enabled
acct_mgr.pwhash.* = disabled
acctmgr.register.* = enabled
acct_mgr.svnserve.svnservepasswordstore = disabled
acct_mgr.web_ui.* = enabled
acct_mgr.web_ui.LoginModule = enabled
acct_mgr.web_ui.resetpwstore = disabled
acct_mgr.guard.accountguard = enabled
trac.web.auth.LoginModule = disabled

[account-manager]
password_store = HtPasswdStore
htpasswd_hash_type = md5
htpasswd_file = /var/www/trac/users.htpasswd
allow_delete_account = false
login_attempt_max_count = 5
user_lock_time = 60
user_lock_max_time = 0
user_lock_time_progression = 2



[git]
shortrev_len = 40

Edit the logo section

[header_logo]
alt = Yet Another Trac Project
height = -1
link = /
src = /chrome/common/trac_banner.png
width = -1

Edit the attachment size limits

[attachment]
max_size = 8388608
max_zip_size = 8388608
render_unsafe_content = disabled

Edit log settings, to log through syslog

[logging]
# log_file = trac.log
# log_format = <inherited>
log_level = WARNING
log_type = syslog

Edit your project settings

[project]
admin = youremail@yourdomain.com
admin_trac_url = trac.yourdomain.com
descr = Name For Your Project

Edit the mail settings to use system sendmail for e-mail delivery. Note, you can also instruct Trac to relay via SMTP if you prefer.

[notification]
email_sender = SendmailEmailSender
smtp_from = trac@yourdomain.com
smtp_reply_to = trac@yourdomain.com

Create an empty password file

touch /var/www/trac/users.htpasswd

Generate static files, python cache

To reduce overhead in trac, extract and store static files that can be served directly by Apache.

mkdir -p /var/www/trac/static
trac-admin /var/www/trac/project deploy /var/www/trac/static

Allow for a python code cache

mkdir -p /var/www/trac/python_egg_cache

Configure Apache to serve Trac via WSGI

Enable apache modules

a2enmod ssl
a2enmod wsgi
a2enmod cgi

Set ownership of trac files to the apache system user

chown www-data:www-data -R /var/www/trac

Edit the apache config file. If your server is going to host multiple websites, you may wish to create a new conf file, rather than editing the default one.
/etc/apache2/sites-available/000-default.conf


<VirtualHost *:80>
  # Catch all non-ssl requests and redirect them to ssl
  ServerName trac.yourdomain.com
  Redirect permanent / https://trac.yourdomain.com/
</VirtualHost>

<VirtualHost *:443>
  ServerName trac.yourdomain.com

  <IfModule mod_headers.c>
    Header always set Strict-Transport-Security "max-age=15768000; includeSubDomains; preload"
  </IfModule>

  CustomLog /var/log/httpd/yourdomain.com_trac.access.log combined
  ErrorLog  /var/log/httpd/yourdomain.com_trac.error.log

  SetEnv PYTHON_EGG_CACHE /var/www/trac/python_egg_cache

  Alias /chrome /var/www/trac/static/htdocs
  <Directory "/var/www/trac/static/htdocs">
    <IfModule mod_authz_core.c>
      Require all granted
    </IfModule>
  </Directory>

  WSGIDaemonProcess tracweb python-home=/var/www/trac/virtualenv
  WSGIProcessGroup tracweb
  WSGIApplicationGroup %{GLOBAL}
  WSGIScriptAlias / /var/www/trac/static/cgi-bin/trac.wsgi
  <Directory /var/www/trac/static/cgi-bin>
      <IfModule mod_authz_core.c>
          Require all granted
      </IfModule>
  </Directory>

  SSLEngine on
  SSLCertificateFile    /etc/letsencrypt/live/www.yourdomain.com/cert.pem
  SSLCertificateKeyFile /etc/letsencrypt/live/www.yourdomain.com/privkey.pem
  SSLCertificateChainFile /etc/letsencrypt/live/www.yourdomain.com/fullchain.pem
</VirtualHost>

Check your Apache configuration for errors

source /etc/apache2/envvars
apache2 -t

Watch the output of your logs, to detect any problems

journalctl -f &
tail -f /var/log/apache2/*

Start Apache web server

systemctl restart apache2

Log in and configure Trac

Authentication plugin

Open trac.yourdomain.com in your browser. If you've done everything correctly, you should see the introductory WIKI page. Click the Login link, to be taken to the initial authentication setup

Step 1: Choose the following options:

Convert login names to lower case on registration and login - Checked
Restrict sending cookies to HTTPS connections - Checked
Authentication Front-End: Use a HTML login form
Integrate links to related actions in the login form - Checked
Allow the user to be remembered across sessions: checked

Steps 2 through 5: No changes to defaults

Step 6, choose your initial login name and password

Anonymous user permissions

By default, website visitors can see basically everything. In the admin menu, you can configure permissions for anonymous users.

Getting started with your Git repository

From your workstation, not the server, clone the repository

git clone https://trac.yourdomain.com/git/myproject.git

Create a README.md file, commit to git, and push back to the server

cd myproject

cat << EOF > README.md
# My Project
I am just getting started with my project!
EOF

git add README.md
git commit -a -m "Add Readme File"
git push

Visit Trac in your browser. You should see the code changes reflected in the Timeline, and Browse Source menu options.

Troubleshooting

Log files are your friends when something goes wrong on your server. You can watch all the relevant logs in real time, to see what errors are given with something doesn't work.


# Linux system logs
journalctl -f &

# E-Mail logs
tail -f /var/log/maillog &
tail -f /var/log/exim4/* &

# Web server logs
tail -f /var/log/apache2/* &

Getting Help

Contact

Please let me know if you discover errors in this guide that need to be corrected.