Free software automates software for linux

Billing Software project allows your business to track invoicing and allows your customers to view their invoices online and easily export them to Excel for saving or printing.
Invoices can also be emailed to customers right from the online application for convenience and efficiency.
Enhancements:
- This release fixes some minor bugs in the XML portions of the library files.

Go Awstats project automates the production of Awstats Apache log reports at a site where multiple virtual hosts exist.
It always updates the reports for the current month and the current year and only produces other reports if they do not exist, which saves on CPU.
The regeneration of a report can be forced by simply erasing it.
Enhancements:
- A major year calculation error has been fixed that appeared when the logs began to span more than two years.
- The author is now confident that the whole thing now works as advertised, hence the bump to revision 1.0.

timeclock software is an application for employees to use as a timeclock. An employee time and attendance system keeps track of when your employees sign in and out of work.

This information can then be compiled to produce the total hours worked and the amount that the employees should be paid.

Timeclock-software.nets free software product will be a simple solution to allow your employees to record their time in one central location for easy access.

Njudge is an automated judge for Diplomacy games, based on Ken Lowe software.
Installation:
1. Create a system user account (i.e. judge) and its home directory
(i.e. /home/judge) It is recommended to lock the password for this
account as you should never need to login as this user.
2. `cd to the directory containing the packages source code and type
`./configure to configure the package for your system. If youre
using `csh on an old version of System V, you might need to type
`sh ./configure instead to prevent `csh from trying to execute
`configure itself.
By default it will set up the judge in /home/judge as user judge with
an email address of judge@localhost and sendmail in /usr/sbin.
If you chose a different user and directory in step 1, or if judge
email should come from a different domain, you can give the configure
script flags to override the defaults. The flags are:
--with-dir=DIR
--with-user=NAME
--with-domain=DOMAIN
--with-sendmail=SENDMAIL
for example to set up the judge in /home/jaldhar/dip as user
jaldhar and email judge@braincells.com and sendmail in /usr/ucb, you
would do:
./configure --with-dir=/home/jaldhar/dip --with-user=jaldhar --with-domain=braincells.com --with-sendmail=/usr/ucb
There are many other flags you can give (type ./configure --help
for a full list) but these are the main ones youre likely to use.
Running `configure takes awhile. While running, it prints some
messages telling which features it is checking for.
3. Type `make to compile the package.
4. If this is a new install:
Type `make install to install the programs, any data files and
documentation. You will have to edit a few configuration files
before the judge will become operation.
If this is an upgrade from an older version;
Type make upgrade to install the new programs only.
*Note* compiled programs will not be stripped of debug and other extra
information. If you want to make compiled programs a little smaller,
you can type make install-strip or make upgrade-strip instead. This
may give a few harmless errors (when it tries to strip scripts) but you
can ignore them.
If you just want to rebuild the map files (because e.g. you added a new
variant,) type make remap.
5. You can remove the program binaries and object files from the
source code directory by typing `make clean. To also remove the
files that `configure created (so you can compile the package for
a different kind of computer), type `make distclean.
Enhancements:
- Major bugfixes

ControlTier application aims to be a complete enterprise-ready automation solution. It is our goal to provide the tools needed to automate the build, release, deployment, configuration, and control of distributed, multi-tier applications. When it comes to ease of use and out of the box functionality, we havent met all of our goals yet but we are working hard to do so. Any comments, questions, or criticisms are always welcome.
ControlTier coordinates and automates the chain of events that take place when you build and deploy a collection of integrated applications (what we call a "site").
Youll use ControlTier to:
- Coordinate your build processes (interfaces with build tools like Ant)
- Manage your build artifacts and other deployable resources in a structured repository
- Coordinate the distribution, configuration, and control of the various applications that makeup a site
Unlike most automation solutions that are focused exclusively on hardware and OS provisioning in production environments, ControlTier was built to focus on the application build and deployment processes that run all the way from Development, through QA, and into Production.
Main features:
- Framework for sequencing and coordinating automation
- Configuration management database
- Logical remote management (manage lots of things as one logical unit, no matter where they physically reside)
- GUI based development and operations tools
- Improved reuse and componentization of your existing scripts and configurations
- Change detection and configuration validation
- Application status discovery and detection
- Fine-grain access control
- Release migration tools
- Logging (with environment context built-in)
- Reporting and correlation tools
- Cross-platform support (Linux, Solaris, Windows, Mac OS X, etc.)
Enhancements:
- This is a major upgrade of both the ControlTier automation framework as well as the pre-built automation modules and workflows that come with the framework.

SyntaxCMS simplifies publishing various types of content to a site, facilitates creating and managing arbitrary relationships among content items, automates and accelerates custom development, and encourages reuse of site components with other SyntaxCMS installations.
Syntax CMS is built using PHP and MySQL.
For Content Managers and Creators
- Create and edit site content online.
- Approve content before publishing to web.
- Set content items to publish/expire at a given time.
- Build complex site hierarchies using sections to organize content without creating HTML or template files.
- Restrict access and actions to content types by groups of users.
For Developers
- Define new content types on-the-fly. SyntaxCMS automatically provides forms for adding and editing content and base classes for working with content types in PHP code.
- Use the Collections and Filters API to query the database for matching objects without having to write SQL.
- Customize the look and layout of any part of the site using PHP.
Enhancements:
- Various performance enhancements and API improvements.
- New modules for working with RSS/Atom feeds, publishing a blog, and better default behavior.

The Faq-O-Matic is a CGI-based system that automates the process of maintaining a FAQ list. It allows visitors to your FAQ to take part in keeping it up-to-date. A permission system also makes it useful as a help-desk application, bug-tracking database, or documentation system. Jon wrote an article about the FAQ-O-Matic that appeared in the USENIX ;login: newsletter: http://www.usenix.org/publications/login/1998-6/faq.html.

This documentation itself is, naturally, maintained with Faq-O-Matic. Hence the weird title. If you see anything that can use updating, please do fix it! If you just want to play around, check out the (Xref) Playground.

A mailing list is very good because it gets together people who have questions with people who have answers.

A mailing list archive is even better, because it lets thoughtful people with Frequently Asked Questions search for an immediate answer, and avoid bothering the people who have answers. Unfortunately, the answers in a mailing list archive become stale over time, are disorganized, and are hard to sift from the conversational noise of the mailing list.

A Frequently Asked Questions list (FAQ) is even better, because the people with questions can be a little lazier and still find their answer right away. Unfortunately, maintaining a FAQ list requires effort; if the people with the answers become lazy, the FAQ list becomes stale.

I wrote the FAQ-O-Matic when I found myself frequently answering a certain question on a mailing list. The FAQ for the list had become stale (its creators interest had succumbed to laziness), and I knew I was far too lazy to take over maintaining my own FAQ.

So, in a triumph of laziness, I wrote the FAQ-O-Matic. The idea is this:

- People with answers can submit them to the FAQ, but
nobody is responsible for knowing all the answers.

- People with corrections can make them to answers, but
nobody is responsible for coordinating corrections.

This worked pretty well, but the first FAQ-O-Matic tended to become disorganized, since no-one was responsible for its structure. So I added commands to move answers and categories around, plus a Moderator feature that lets one person keep track of changes to the FAQ by e-mail:

- A person can keep a subset of the FAQ organized, but he
or she doesnt have to know all the answers or organize
the whole FAQ.

So a FAQ-O-Matic is something that lets the members of a community share the tasks of entering, correcting, and organizing frequently-asked questions and answers. Many folks have found other uses for FAQ-O-Matic, treating it as a general collaborative editing tool.

Aargh is a code generator, written in C++ and licensed under the terms of the GNU General Public License (GPL). It generates C++ code to parse a command line, using the getopt() facility available in UNIX and UNIX-like environments.
Automated Argument Helper project supports command-line options with integer arguments, string arguments, and no arguments. The generated code is commented and carefully indented for readability.
Its nice to have lots of command line options, but its a real pain to code for them.
Not that its difficult. Its just tedious, time-consuming, error prone, and no fun. I used to wince at the thought of adding command line options.
Not any more. All I have to do is define the options I want in a small XML file, and run it through aargh. Instantly I have C++ source code that I can compile and link into my program.
If I need to add another option, or otherwise change the rules, I can edit the XML and regenerate the code. No muss, no fuss. Now I can spend more time on the interesting parts of the project.
To use aargh, write an XML file to describe the options you want. When aargh reads the file, it generates two C++ files.
One file is a header that declares a class to represent the options. By default this class is named "Opts," but you can specify a different name. The other file is the implementation of Opts, or whatever you decide to call it. The Opts class provides member functions to parse the command line and return the results.
In your own code, declare an instance of Opts and call Opts::get() to parse the command line, passing it the argc and argv arguments from main(). Opts::get() returns zero if the command line follows the rules that you have outlined in the XML file, or non-zero otherwise. If the parsing is successful, the Opts object stores the results and makes them available to your program by a series of accessor functions.
Main features:
- You can enforce upper and/or lower limits on the number of non-option arguments.
- You can distinguish between options that take arguments and those that dont.
- You can specify that an option is required.
- You can require that the argument to an option be a non-negative integer.
- For an integer argument you can enforce upper and/or lower limits.
- For a string argument you can enforce upper and/or lower limits on the string length.
- For a string argument you can call a function of your own to validate the argument.
- You can allow multiple occurrences of the same option. In that case the generated code builds an STL vector to hold the arguments. By default the generated software allows only one occurrence of any given option.
Enhancements:
- You can now specify the location of the generated header file independently of its name.
- This feature may make it easier to incorporate aargh into complex build environments.