Free procedures software for linux

pyctures is a small web gallery written in Python that uses the web.py framework. It does not use any database and stores all the necessary data in the filesystem.
pyctures is published under the BOLA (Public Domain), so you can run the software anywhere, and do whatever you want with it.
Installation:
The installation procedure depends on the HTTP server youre using. What follows is a list of procedures for some common HTTP servers. If you use pyctures with something else, please let me know so I can add it here.
After youve completed the install, read the "Administration" file to learn how to manage your gallery.
Common procedure
1. Copy the "website" directory to a suitable place where you want to install
pyctures. It does not have to be inside your website, but has to be
readable by your webservers user.
2. Create a "config.py" file based on the "config.py.sample" file, and edit it
according to your configuration. A really important setting is the album
path, where all albums will be stored. It can be anywhere you want. Create
an admin user so you can create albums using the web interface.
3. Make sure the album path is writeable by the user who will run the pyctures
application. It usually is your web server user.
4. Install PIL from http://www.pythonware.com/products/pil/. The package name
for most distributions is "python-imaging" or just "imaging".
5. Install cheetah from http://www.cheetahtemplate.org/. The package name for
most distributions is "python-cheetah" or just "cheetah". You need at least
version 2.0-rc5.
No server (stand-alone)
pyctures can be run without any HTTP server by just executing
"./pyctures [PORT]" directly on the website directory. Its useful for
testing and small sites. I recommend that you test everything works this way
before integrating it into a webserver.
lighttpd
First of all, install "flup", from http://www.saddi.com/software/flup/.
Gentoo: Its not in portage, it sucks. Check
http://bugs.gentoo.org/show_bug.cgi?id=100784
Debian: apt-get install python-flup
Now, lets suppose youve installed pyctures in the "/var/www/pyctures"
directory, and want to publish it under the "/pics/" directory.
You need to add the following to /etc/lighttpd/mod_fastcgi.conf (or just
/etc/lighttpd/lighttpd.conf if you dont have the other file):
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
fastcgi.server = (
"/pics" => ((
"socket" => "/tmp/fastcgi-pics.socket",
"max-procs" => 1,
"bin-path" => "/var/www/pyctures/pyctures"
))
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
This is enough, but be aware that "http://mysite/pics" (note the missing
"/" at the end) will *not* be redirected to pyctures.
If you want to be able to refer to your pyctures root both as
"http://mysite/pics/" and "http://mysite/pics", you need to add the
following in the same file as before:
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
url.redirect = (
"^/pics$" => "/pics/"
)
---------- 8< ---------- 8< ---------- 8< ---------- 8< ----------
And then create an empty file in your document root called "gallery",
otherwise lighttpd will think the path does not exist and return 404 before
doing the redirection.
Enhancements:
- This version implemented pagination, IE support, and automatic thumbnail regeneration on config changes.
- It also improved performance considerably, reduced the memory footprint, added Apache installation instructions, and included several other minor improvements.

The Job Scheduler runs executable files, shell scripts and database procedures automatically (MySQL, PostgreSQL, Firebird and SQL Server, Oracle, DB2).

Job Scheduler processes sequential and parallel tasks and job chains, provides an API for job implementation with Java, Javascript, VBScript, Perl and exposes jobs as Web Services.

Apache Directory Server is an embeddable LDAP server implemented in pure Java.
Our primary vision (others also outlined below) is to build an enterprise directory server platform (and its components) where other Internet services snap in to store their data within the directory so they may be managed using LDAP.
From the image above youll see the architecture is designed so services besides LDAP like DNS, DHCP, SLP and Kerberos will snap in. Other services like UDDI can also be implemented and snapped in. These services will use a common networking layer and each can be toggled on and off according to the needs of the environment.
apseda, mina, or sedang are various frameworks used for the common network layer. These services share the common network layer and back their data within the Apache Directory Servers backing stores without any network latency or going through the LDAP line protocol. NTP btw is the only exception and its there to remedy the need for time sync for replication and other time sensitive protocols like kerberos. Its implementation here is intended to prevent any dependency on external infrastructure.
Main features:
- Designed as an LDAP and X.500 experimentation platform. Plugable components and subsystems make ApacheDS extremely modular and ideal for experiments with various aspects of the LDAP protocol.
- The servers frontend is completely separable from its backend and vice-versa making it very flexible for implementing virtual directories, proxy servers and gateways to X.500.
- Several backends can be implemented and plugged into the servers partition nexus. The server supports a BTree based partition out of the box but any backing store can be used to implement a partition so long as it conforms to interfaces.
- The server exposes aspects of administration via a special system backend. LDAP can be used to manage these concerns through the system naming context at ou=system.
- Java based triggers and stored procedures are being implemented.
- Both the backend subsystem and the frontend are separable and independently embeddable.
- The server contains a server side JNDI LDAP provider as the facade for the entire backend subsystem. JNDI operations are directly translated by this provider into operations against the nexus and the target partitions storing server entries.
- The server will use JNDI as the data access API for stored procedures. This will make stored procedures functional within and outside of the server without requiring recompilation.
- The servers networking code, MINA, Multipurpose Infrastructure for Network Applications was designed for pluggable protocol providers, of all sorts and not just LDAP. MINA gives ApacheDS the ability to handle large amounts of concurrency.
- The server uses the Snickers tools and APIs for ASN.1 BER encoding and decoding. These tools are designed for a very small encoding and decoding footprint as well as for use in non-blocking servers. The chunking nature of the BER codec makes the server very efficient while handling encoding and decoding making it more resistant to DoS attacks. This layer is also pluggable with a new experimental Twix provider which is much more efficient. Of course there is the unsupported Snacc4J provider which is no longer maintained.

my Knowledge Explorer, in short mKE, is an intelligent knowledge assistant. mKE helps the user to record, change and search knowledge, and provides extensive error checking to ensure the internal consistency of the knowledge. mKE possesses self-knowledge -- just ask it (using the mKR language) what commands it can execute for you.
mKE command-line options select the language definitions -- RDF or OWL or CycL or mKR -- which are automatically loaded on startup. The CycL definitions include the complete Upper Ontology of the OpenCyc knowledge base.
mKE is implemented using the Unicon and KornShell and Java languages, providing easy integration with Unicon procedures, shell scripts, Linux/Windows commands, web pages and standard databases.
Enhancements:
- This release includes the OpenCyc Upper Ontology, which is automatically loaded with "-cyc" option.
- RDF and OWL language definitions are loaded with "-rdf" and "-owl" options.
- The mKR binary relation syntax was enhanced for easier translation of OWL files to mKR files.

GEBORA is an administrative tool for the Oracle Relational Database Management System. GEBORA project is an OpenSource alternative to TOAD.
Since beta-2, GEBORA uses native look-and-feel. This approach looks faster in Windows when huge tables are filled (something about 2000 or more rows).
Main features:
- Send manually created SQL commands to server, showing the results in a table;
- Browse thru all database schemas (users) and its tables and packages;
- Display tables:
- Data (with filter, ordering and printing);
- Columns (can be printed, too);
- Relations (foreign keys) in both directions (referenced tables and tables that references a table);
- Statistics (with unique profile generation and print);
- Creation script (without constraints);
- Display stored procedures source code and parameters;
- Run stored procedures, defining and viewing IN/OUT parameters.

mod_plsql is Apache module that allows you to create Web Applications using Oracle stored procedures. mod_plsql Apache module works similarly to Oracle Web Application Server PL/SQL cartridge.
Main features:
- Database connection caching.
- Integration with SSI
- Doesnt need Oracle OWS Toolkit - no copyright problems
- Ability to freely play with HTTP Headers and such.
Enhancements:
- This release fixed cookie age handling and changed the cookie format to Version 1.

Firebird .NET Data Provider is an ADO.NET data provider for Firebird. Firebird .NET Data Provider is written in C# and provides a high-performance native implementation of the Firebird API. It also includes an implementation of the Firebird Services API and Firebird array datatype support.

Firebird is a relational database offering many ANSI SQL standard features that runs on Linux, Windows, and a variety of Unix platforms. Firebird offers excellent concurrency, high performance, and powerful language support for stored procedures and triggers. It has been used in production systems, under a variety of names since 1981.

Firebird is a commercially independent project of C and C++ programmers, technical advisors and supporters developing and enhancing a multi-platform relational database management system based on the source code released by Inprise Corp (now known as Borland Software Corp) on 25 July, 2000 under the InterBase Public License v.1.0