Free quickstart software for linux

App::quickstart is App::Context Developers Quick-Start Guide.

This is the Developers Quickstart Guide to the App::Context Framework. Its focus is to give a minimum amount of theoretical or explanatory background and get right into learning by example.

That having been said, it is also important to let you know what documentation exists and what state it is in.

I got started building the App::Context framework a while ago. The documentation is very limited. This is an effort to bring it all together. This list shows how all of the documentation fits together and in what state it is.

The following documentation is in good shape. To get started, read them more or less in the order shown.

App::quickstart - This quick start guide.

App::installguide::hosted - Installing the App::Context Framework on a non-root web hosting account

The following documentation also is in good shape. It is background reference material.

App::datetime - Guidance on date, time, and datetime types in perl.

App::exceptions - Guidance on exceptions in perl.

The following documentation is in a state that needs review, modification, or completion.

App::perlstyle - A perl style guide that builds minimally on perlstyle.

App::faq - Questions about P5EE.

App::installguide - Installing the App::Context Framework on Unix.

App::installguide::win32 - Installing the App::Context Framework on Windows.

App::devguide - Developers Guide.

App::devguide - Developers Guide.

App::adminguide - Administrators Guide.

App::adminguide::cvs - Admin Guide, setting up CVS source control.

CLASS/MODULE DOCUMENTATION (indented entries are subclasses)

Most of this documentation needs review, modification, and completion.

App - The module that bootstraps the use of the App::Context Framework.

App::Context - Abstract class representing the the runtime context of the program.

+-- App::Context::Cmd - A program running in a command-line context.

+-- App::Context::HTTP - A program running in a CGI/mod_perl context.

+-- App::Context::Server - A program running in a multi-process server context.

=====+-- App::Context::ClusterController - Running in a multi-node cluster context.

=====+-- App::Context::ClusterNode - Running on a single node of a cluster.

+-- App::Context::NetServer - Another flavor of server context (not yet implemented).

App::Exceptions - Defines the exceptions used in the framework.

App::UserAgent

App::Request

+-- App::Request::CGI

App::Response

App::Session

+-- App::Session::HTMLHidden

+-- App::Session::Cookie

App::Reference

+-- App::Conf

=====+-- App::Conf::File

App::Service

+-- App::Serializer

=====+-- App::Serializer::Properties

=====+-- App::Serializer::Ini

=====+-- App::Serializer::Perl

=====+-- App::Serializer::Xml

=====+-- App::Serializer::Yaml

=====+-- App::Serializer::OneLine

=====+-- App::Serializer::TextArray

=====+-- App::Serializer::Storable

+-- App::SessionObject

+-- App::Authentication

+-- App::Authorization

+-- App::ValueDomain

+-- App::SharedDatastore

+-- App::MessageDispatcher

+-- App::CallDispatcher

=====+-- App::CallDispatcher::HTTPSimple

+-- App::ResourceLocker

=====+-- App::ResourceLocker::IPCSemaphore

=====+-- App::ResourceLocker::IPCLocker

Apache::Framework::App

INSTALLATION

You can go through one of the installation guides. Installing the App::Context Framework generally involves several distributions and should just work when installed from CPAN.

perl -MCPAN -e shell
cpan> install App::Options
cpan> install App::Context
cpan> install App::Repository
cpan> install App::Widget
cpan> exit

If its not this easy, I need to work on making it easier.

HTML::Seamstress::Quickstart is a gentle introduction to HTML::Seamstress.

Introduction

This guide is designed to get you started with dynamically generating and modifying ("templating") HTML with HTML::Seamstress.

We will work through several examples, with each one increasing your ability to work with Seamstress effectively.

Sample files

All the files for the samples are in the directory lib/HTML/Seamstress/Quickstart

Pure TreeBuilder

Welcome to the first example. This is our bare-bones example. Lets say we want to dynamically modify the following HTML:

< html >

< head >
< title >Greetings< /title >
< /head >

< body >

< h1 >Greetings< /h1 >

Hello there < span id=name >person< /span >, your lucky number is
< span id=lucky_number >666< /span >

< /body >

< /html >

Lets not use Seamstress at all in this case. Remember Seamstress just makes using HTML::Tree more convenient when writing software - it is completely optional and totally non-magical. So heres the (admittedly verbose) pure TreeBuilder solution:

use strict;
use warnings;

use HTML::TreeBuilder;

my $name = Redd Foxx;
my $number = 887;

my $tree = HTML::TreeBuilder->new_from_file(html/greeting.html);

my $name_elem = $tree->look_down(id => name);
$name_elem->delete_content;
$name_elem->push_content($name);

my $number_elem = $tree->look_down(id => lucky_number);
$number_elem->delete_content;
$number_elem->push_content($number);


print $tree->as_HTML(undef, );

Theres a convenience function in HTML::Element::Library which makes it easy to replace all the content of an element. This will make our script shorter. If we simply use Seamstress, its new_from_file() method will bless the HTML tree into a class which inherits from HTML::Element::Library, making it easy for us to shorten our program. So lets rework the example using bare-bones Seamstress.

Squid Graph is a free, simple, yet powerful Squid v2 native logfile analysis tool that generates reports with graphical representation of the proxy servers traffic.
Squid Graph is distributed under the GNU General Public Licence (GPL), which means it is FREE FOR USE AND DISTRIBUTION.
Squid Graph was developed using the Linux operating system running kernel versions ranging from 2.2.x to 2.4.x with PERL 5.6.0. It should work on all other similar operating systems with PERL 5.6 and above installed.
Some platforms which have been reported to run Squid Graph successfully are FreeBSD, OpenBSD, Sun Solaris and most Linux kernel versions and distributions.
Enhancements:
- No algorithm changes, mostly changes to contact information etc. due to hand-over of project to SecurLogic.
Installation:
Extracting the Tarball
- Extract the Squid Graph tarball file after you have downloaded it. Those with Redhat Linux (or other similar distributions) can do this: -
$ tar -zxvf squid-graph-x.x.tar.gz
- Alternatively, those with UNIX-like operating systems can do this: -
$ zcat squid-graph-x.x.tar.gz | tar -xvf -
Gathering the Pre-requisites
- As of version 3.0, Squid Graph requires the GD perl module. You can download it from http://stein.cshl.org/WWW/software/GD/ or you can use the included GD-1.3.3.tar.gz file in the extras/ directory.
- Follow the intructions in the GD perl module to get it installed correctly before you proceed.
Compiling
- Squid Graph runs out of the box. You dont have to compile it.
Putting it in the Right Place
- You might not prefer to have Squid Graph lying around in your current directory, so you should just move it to a directory which makes sense, such as /usr/local/squid-graph. e.g.
$ mv squid-graph-x.x /usr/local/squid-graph
Runing Squid Graph:
Quickstart
First, get yourself into the bin/ directory, for example: -
$ cd /usr/local/squid-graph/bin
Next, you run Squid Graph with the default options. The bare minimum for Squid Graph to run is the --output-dir option. The output directory is where the generated HTML reports and image files would be written.
$ ./squid-graph --output-dir=/var/www/html/reports < /usr/local/squid/logs/access.log
NOTE: Please check your directory permissions of your output directory!
Usually you would want the output to be generated into a directory which your web server is configured with access to. In the above example, /usr/local/squid/logs/access.log is your Squid logfile.
Where you store your Squid logfile differs from system to system. For default Redhat Linux installations, it should be in /log/squid/access.log. For those who compiled and installed Squid with the default options, it should be in /usr/local/squid/logs/access.log.
Removing the TCP or UDP Graphs
Most of you wont use cache ICP or log cache ICP, so there wont be any UDP messages in your logfiles. Disabling UDP is a good idea. You can do this by specifying the --tcp-only command line option.
$ ./squid-graph --tcp-only --output-dir=/var/www/re...
Likewise, if you only want to see UDP statistics, you can specify the --udp-only option.
$ ./squid-graph --udp-only --output-dir=/var/www/re...
Generating Cumulative Graphs
As of version 3.0, Squid Graph comes with a new feature to generage cumulative curves instead of the normal graphs. This can be done by specifying the --cumulative option.
$ ./squid-graph --cumulative --tcp-only --output-dir=/var/www/re...
To have a better understanding of what cumulative curves are, take a look at the output examples. Do note that enabling cumulative graphs disables the Average Transfer Duration graph automatically.
Disabling Average Transfer Duration Graphs
You can disable the Average Transfer Duration Graph by specifying the --no-transfer-duration option.
$ ./squid-graph --no-transfer-duration --output-dir=/var/www/re...
Specifying the Start/End Time
By default, Squid Graph generates reports based on the current time. It starts analyzing from 24 hours before the current time until the current time. Sometimes we cycle logfiles so it is necessary to specify when you want Squid Graph to start looking at your log files. This is done by specifying the --start option.
$ ./squid-graph --start=991353612 --output-dir=/var/www/re...
Likewise, you can specify the end time and Squid will automatically calculate the start time for you. This is done by specifying the --end command line option.
$ ./squid-graph --end=991352122 --output-dir=/var/www/re...
To get the last line of the Squid logfile, simply use tail -n1 logfile.log
Note that the start value is a numerical value which represents the number of seconds since 1970, NOT the conventional hh:mm:ss dd/mm/yyyy format. The reason why we did this is because Squid logs its time in this format, and we can easily use head -n1 logfile.log to view the first line of the log file to determine the start time.
Enhancements:
- Updated links after moving project to Sourceforge
- Updated links to incorrect GPL license in documentation
- Updated links to outdated GD Perl module
- Simplified package directory structure and removed old files
- No algorithm / logic changes

Wagtail is yet-another-CD-ripping-and-encoding-wrapper. Wagtail is designed for bulk encoding, large collections and for people who take their encoding seriously. Wagtail wont suit everyone. The learning curve seems steep but its really not that bad, to get going read the quickstart guide and you can always delve into the details later.
If youre installing or setting up Wagtail I have a strong recommendation to start with the quickstart guide then moving onto the full manual.
Main features:
- Handles CD ripping, CDDB (including submission) encoding, tagging and moving of files.
- Supports re-encoding of existing files/playlists.
- User choice of software for each stage of processing and encoding.
- Client/server architecture. Clients send files to the Server to be encoded. Both tasks can be performed by a single machine.
- Files to be processed are queued on the server, i.e. no need for the client to wait for the server to catch up before sending more files.
- Server can support multiple formats and quality levels.
- Server supports multiple tasks which define the encoded file naming scheme, arbitrary re-processing instructions, format choice restrictions etc.
- Flexible naming rules for files and directories. Names can be based on file properties. Multiple

localscan is a frontend to nmap. The purpose of localscan is to make the lives of administrators easier. At its heart, localscan is simply a list of "ignore this host/port combo" rules designed to reduce the amount of useless information returned by nmap scans of a given subnet.

I administer a largish lab at a largish higher educational institution (which shall remain unnamed!), and about three months ago I found it necessary to start running a portscanner against my subnet every so often. Now, while it was relatively easy to cobble something together that would do this and mail the results of the scan to me, I found that my inbox was being filled with inanity. Lots of valid services were present, and the few invalid services were hard to pick out. So I put together a quick-and-dirty filter and released it internally as local_scan 1.0a. Not surprisingly, no one used it. This is because I was (am!) still learning Perl.

After the initial disappointment, I sat down and started rewriting, with the end result being what you just downloaded. :) Localscan 2.0 is much easier for the non-Perl person (yes, there are a few of them out there) to use. All the "interesting" user-configurable parameters are now contained in a plaintext external datafile called localscan.conf.

You should have received four files in this tarball.

This readme file
A "quickstart" guide
Localscan.pl, the actual script
Make_conf.pl, a script to generate the localscan.conf file

Gantry::Docs::TOC is a table of contents for Gantry::Docs::* documentation modules.

What should I read?

This document is a brief annotated list of each Gantry::Docs::* module.

About.pm

Describes the history, features, and motivation behind Gantry.

DBConn.pm

Explains how database connection information flows from app configuration to DBI. The process should be seamless for app developers, but if you need to work on the engines or add support for in ORMs, you may find useful information here.

FAQ.pm

A list of questions we think people are likely to ask along with answers. This is not a philosphical document, it is filled with code examples.

QuickStart.pm

If you are new Gantry and want to get your first app running with a minimum of fuss, this is for you.

TOC.pm

This document.

Tutorial.pm

More detailed than the Quick Start, this document walks through building a simple application with Gantry.

Why.pm

Explains you should use a framework at all, whether it is Gantry or one of the many others.

Uplug is a collection of tools for linguistic corpus processing, word alignment, and term extraction from parallel corpora. Several tools have been integrated in Uplug.
Pre-processing tools include a sentence splitter, tokenizer, and external part-of-speech tagger and shallow parsers. The following external tools are used: the Grok system for English (tagging and chunking) and the morphological analyzer ChaSen for Japanese.
Other tools such as the TreeTagger can easily be added. Translated documents can be sentence aligned using the length-based approach by Gale & Church. Words and phrases can be aligned using the clue alignment approach and the toolbox for training statistical alignment models GIZA++.
Enhancements:
- User management for the Web-based alignment interfaces (ICA & ISA) using simple password protection and user-specific data storage.
- 2 new sentence aligners integrated into Uplug: hunalign and GMA.
- Another sentence alignment approach: uplugalign (length-based sentence alignment with cognate/dictionary filters).
- Quickstart documentation for the new features.

VoxForge project was set up to collect transcribed speech for use with Open Source Speech Recognition Engines. We will categorize and make available all submitted audio files under the GPL license, and then compile them into Acoustic Models for use with Open Source Speech Recognition engines such as such as Sphinx, HTK, CAVS and Julius.
The current focus of VoxForge is on collecting transcribed audio for Command and Control applications on a PC and for Telephony Speech Recognition (i.e. IVR - Interactive Voice Response) applications. We will collect English language audio to begin with, and add other languages in the future.
Click the SubmitSpeech link on the menu above to learn how to record your speech and submit your speech audio files to VoxForge. Click the AcousticModels link to learn how compile your speech audio files into a Speaker Dependent Acoustic Model or how to modify the VoxForge Speaker Independent Acoustic Model to better recognize your voice.
Enhancements:
- The QuickStart Acoustic Model was updated.