Free process automation software software for linux

E/AS Automation Solutions is open source software system for help automate your solutions even for personal and/or corporate ones.
E/AS written on CLIP language (CA-Clipper dialect, compiler can be obtained from ITK.ru) and uses CODB (CLIP Object Database) as data storage.
Main features:
- client-server technology (both data and interface forms)
- component infrastructure with interaction between components by messages
- interface forms on XML
- MDI
E/AS contains in typical distribution:
- client software written on clip-ui library
- server software with wrapper for run as daemon
- maintenance tools: CODB console and component manager
- base (form, auth) and example (contact) components
Enhancements:
- completely rewrite code for implement E/AS architecture
- component infrastructure
- own server program instead COBRA
- maintenance tools: CODB console and component manager
- base and example components
- autoupdate views

The system can be used in the electronic world to keep track of your: Schematic, Printed Circuit Board, Front Plate, Programmable Logic Device numbers.
EDA index is programmed in PHP (and XHTML 1.0), using a MySQL database to store data, so its more or less OS independent, but a Linux server is recommended, since it already got most software installed as default, this configuration is also called LAMP (Linux Apache MySQL PHP)
Its also recommended that a local intranet server is used, since the system dont got a user login, so all data can be viewed without a password, but when you need to add or edit data a password is required. At first this approach might seem wierd, but its designed to allow quick lookups. Example:
You are sitting with a broken pcb with a number on it, and need to find the schematic (so you can repair it) on the computer or in the printed project (schematic) archive. EDA Index allow an quick lookup in the database, without you needing to login, so you get the job done faster.
As far as I know, there are no commercial (or free) program available that can do what EDA Index can, some companies may have created their own software, but how do that help you.
I have worked in an electronic department that had a self made application, but it lagged features like search.
This program is very usefull, if you are using numbers when:
Drawing electronic Schematics and PCBs using a CAD program like: Eagle, gEDA, Protel, Orcad, etc.
Creating Front Plate layouts in: GIMP, Coral Draw, Photoshop, AutoCAD, etc.
Programming Programmable Logic Devices like: PLD, EPLD, CPLD, PIC, APIC, PEEL, PAL, GAL, FPGA, Intel 80XX, Motorola 68XX, etc. Writing the code in: VHDL, Assambler, JEDEC, etc.
Enhancements:
- Included the bugfix to RC2.
- Updated online documentation.
- Updated INSTALL file.

Subversion Automation project is a wrapper around Subversion that automates and standardizes branching and merging.

The primary goal of the project is to simplify the more complex features of Subversion and therefore encouraging their use.

Konsole DCOP Scheme Automation Tool consists of a bash script which automatically changes the Konsole schema.
This is a Bash script to automatically set the desired Konsole Schema when apps such as VIM and less are executed.
It is a simple Bash script I wrote which allows you to automatically have the desired schema set when apps are run from within the shell.
For example, by default, when the user runs VIM with this script installed, the Konsole schema will switch to "VIM Colors" for the duration the user is in VIM. When the user exits VIM, the schema will change back to whatever it was before VIM was run. Other apps this script is setup for by default are:
$ less
$ man
$ info
$ watch
$ top
$ htop
I decided to create this because I became tired of switching my Konsole schema whenever I ran vim. I am now releasing it to everyone as Im sure someone else out there will find this usefull too.
This is a also nice way to impress your friends with how much more advanced the Linux shell is than those of the competitors! ;)
Users may also wish to enable this for other applications, such as mutt. To do so, simply edit the file ~/.konsole_dcop/schemas and follow the existing syntax.
Enhancements:
- This is the initial release.
- It is expected to be fairly stable and fully usable.
- If you have any bugs to report, please do so in the Issues category of the project homepage. Thank you.

The Stewie Radio Automation Project is a stand-in replacement for the "XMMS playlist on random" style of independent radio station.
Once properly configured, the user will enjoy the low maintenance of a "random playlist" station while still being able to use legal IDs, liners, multiple playlists, and music logs.
Main features:
- Low maintenance
- Multiple playlists
- Liners
- Legal IDs
- Logs every song and liner played
- Records errors and keeps truckin
Enhancements:
- Fixed a few bugs in install script
- Created error log/warning system
- Main script now updates the settings in stewie.conf in order to continue running. The only thing that *should* kill it, is not having any music available in the "master" playlist.
- Config file can be updated while script is running
- install-stewie gives "not found" audio players another chance
- Rewrote README file

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....

bibEC Process Card is a multiple gateway credit card payment processor.
This class is meant to process credit card payments via one of multiple payment gateways that are supported.
Currently the class supports the following payment gateways: Plug and Pay, Authorize.net, ViaKlix, and paynet . Changing between payment gateways is mostly a matter of changing the class constructor parameter.
The class provides a payment gateway independent API with functions for:
- Logging the payment activity
- Set the payment gateway authentication credentials
- Set the paying customer details
- Set the ship to details
- Set the credit card details
- Set the valuta
- Specify the order details
- Submit the payment processing request and retrieving the results
The payment submission is done securely when possible using PHP SSL socket connections or the Curl extension for PHP or the Curl command line.

Procbind project is a software that lets you bind a process to one or more processors. The process will then only run on those processors.
Install:
make install
Usage:
procbind -h
for help
For everything more or less related to procbind, please feel free to contact me.
Consider using PGP. My PGP key-id is: 0x1f28d8ae
Enhancements:
- Parameter sanity check added