Free fastcgi software for linux

fastcgi-galleryy is a Web gallery based on Apache::Gallery, but is hacked for usage with Perl FastCGI scripts.
Therefore this version is about 10x quicker than Apache::Gallery. With best template system (Template-Toolkit) you can customize your gallery as you wish, for example you can create multilanguage gallery like this.
A database is not used; everything is stored in files. Output and generated thumbnails are cached for speed optimization.
Enhancements:
- A bug in the translation function when more than 2 languages were used has been fixed.
- A bug with files other than *.jpg has been fixed.
- Some W3C errors have been fixed.

RearSite is a simple collaborative Web site manager. RearSite is an automated Web publishing tool allowing to control who is allowed to access the published documents and also to manage per directories collaboratives tools well adapted to distance learning (forums, chats, shareable calendars, or multimedia quizzes).

An administrator can create users accounts (user name, user passwd, and user home directory), users get logged in and then receive access to their documents.


RearSite is written in PERL (CGI.pm based) and use a FastCGI compliant HTTP server (like APACHE).

Using RearSite is quite simple : after login, the user has access to his home dir and is able to delete, rename, create and edit documents. RearSite is well adapted to install WWW directories previously cooked (using any editors). Its very easy to transfer and install archives (ZIP, tar or tar.gz by now), they are automatically unpacked.

Published documents are public (by default), access restriction may be done using user/password couples, DNS domains or LDAP filters.

The user interface is WWW forms like, so RearSite only needs (on the client side) a Java, JavaScript and frames compliant WWW browser (accepting cookies).

RearSite is now quite secured, the login process (developped in Java) use an MD5 encryption of the user password (combined with a one time key). So, people spying the network cannot use the keys they may have seen. After login, users receive a cookie associated with their computers IP numbers.

RearSite also allows the user to specify who can retrieve his documents by configuring access rights :

documents are public (the default).
documents are restricted to users coming from trusted domains.
documents are restricted to users coming from trusted domains or to HTTP authenticated users.
* documents are restricted to class of users existing in an LDAP directory. This kind of HTTP client authentication needs auth_ldap for Apache (See restricted access by users classes).

Since 1.1, if the administrator wants it, the user is able to use templates to specify per directories access rights. By default (and as an example), the user can easily say that a directory is public, for frenchies only or for frenchies excepted those in the ripoux.fr domain (french joke!).

The user is also able to share his directories with other RearSite users (trusted users). When a directory is shared, a trusted user user is able to delete, rename, add ... files within the directory he received rights for.

The user is also able to recursively process all the file names of all his embeded directories. The functionality provided is to rename all files (lowercase, replace a string within all file names, ...) which simplyfies migration from systems with case-insensitive file names. These functionalities are available by selecting the Special tools button which also give a way to export the current directory within an archive (ZIP or tar.gz).

Since 1.4, a forum can directly be attached to each directories. When a user wants to create a forum, the result is a Forum.html file located within the current directory. This file will give access to the forum. People having access to this file are allowed to post in the forum.

Since 1.6, a chat can directly be attached to each directories. When a user wants to create a chat, the result is a Chat.html file located within the current directory. This file will give access to the chat. People having access to this file are allowed to talk in the chat.

Since 1.9, a shareable calendar can be directly attached to each directories. When a user wants to create a calendar, the result is a Calendar.html file located within the current directory. This file will give access to the calendar. People having access to this file are allowed to read the calendar. Only the owner of a calendar is allowed to update it, but he may allow other users. Accessing his calendar via RearSite allows the owner to update it immediatly. When accessing a calendar via a normal WWW access, the user (owner or not) must be authenticated (via Rearsite configured authentication scheeme) before being allowed to update it.

The chat,forum and calendar functionalities are accessible via the Communications button, they have been designed for distance learning purposes but can easily be used for any groupware needs.

Rails web framework is a full-stack framework for developing database-backed web applications according to the Model-View-Control pattern.

From the Ajax in the view, to the request and response in the controller, to the domain model wrapping the database, Rails gives you a pure-Ruby development environment. To go live, all you need to add is a database and a web server.

Everyone from startups to non-profits to enterprise organizations are using Rails. Rails is all about infrastructure so its a great fit for practically any type of web application Be it software for collaboration, community, e-commerce, content management, statistics, management, you name it.

Rails works with a wealth of web servers and databases. For web server, we recommend Apache or lighttpd running either FastCGI or SCGI. For database, you can use MySQL, PostgreSQL, SQLite, Oracle, SQL Server, DB2, or Firebird. Just about any operating system will do, but we recommend a nix-based one for deployment.

If you need hosting, TextDrive is the official Ruby on Rails host, offering fantastic plans with a knowledgeable staff. Whether you need shared or dedicated hosting, these guys are experts in Ruby on Rails.

Creating a weblog in 15 minutes

In 15 minutes, we go from scratch to complete weblog engine: with comments and an administrative interface. But since the actual application only took 58 lines to complete, we also have time left over to do unit testing, examine the logs, and play around with the domain model.

Putting Flickr on Rails

Ruby on Rails is not just for playing with your local database, its for taking on the web. So in 5 minutes, we create a web-based search engine for Flickr using their public API with all the fades and glamour of Ajax. Hows that for a low-tech alternative to something fancy like Flash.

Evolving your database schema without a sweat

Before you know it, youll have data that you care about in your application. Which makes adding, removing, or changing the schema an error-prone, time-consuming, and frustrating process. That is, unless youre using Ruby on Rails. In 20 minutes, youll learn all about how database migrations can make your schema as flexible as your code with no fear of data loss.

Htscanner will allow one to use htaccess-like file to configure PHP per directory, just like apaches htaccess. It is especially useful with fastcgi.

This package was originally developed by Bart Vanbrabant. Old versions are available from: http://files.zoeloelip.be/htscanner

Gitarella project aim to provide a more performant, complete and friently Web frontend for GIT other than gitweb. The language of choice is Ruby because it makes simpler to handle both CGI and FastCGI with the same code, and many libraries already exists for common tasks like page templates and diffs handling.
The current version supports the basic browsing of repositories and diffing of files, and uses memcached as a backend for short-term storage of extracted data.
The development is handled through GIT at the url git://farraugt.flameeyes.is-a-geek.org/gitarella.git . Web interface is available on gitarella itself.
Version 0.001 is a pre-alpha version, that shows the current status of the code, it does work for basic browsing.
Enhancements:
- This version features lots of bugfixes, especially in handling of tags, remote (pushed) branches, and commit descriptions.
- It also adds graceful and not-entirely-graceful handling of exceptions (depending whether they are thrown during the initialisation phase or during the request) so that the user is never (or should never, at least) presented with an unanswered request.
- It makes the ruby-filemagic extension optional, although recommended, and make use of log4r extension for logging ability.

HTML::CMTemplate.pm is a Perl module that can generate text-based content from templates.

SYNOPSIS
use HTML::CMTemplate;

$t = new HTML::CMTemplate( path => [ /path1, /longer/path2 ] );

$t->import_template(
filename => file.html.ctpl, # in the paths above
packagename => theTemplate,
importrefs => { myvar => hello },
importclean => { myclean => clean! },
);

theTemplate::cleanup_namespace();

print "Content-type: text/htmlnn";
print theTemplate::output();

# Template syntax is described below -- see that section to get the real
# details on how to use this sucker.

HTML::CMTemplate 0.4.0

A class for generating text-based content from a simple template language. It was inspired by the (as far as Im concerned, incomplete) HTML::Template module, and was designed to make template output extremely fast by converting a text/html template into a dynamic perl module and then running code from that module. Since the parsing happens only once and the template is converted into Perl code, the output of the template is very fast.

It was designed to work with mod_perl and FastCGI and has been the basis for all of the dynamic content on the Orangatango site (http://www.orangatango.com).

First release (version 0.1) was February 15, 2001 and was very quiet because it was a proprietary version.

As of version 0.2, it is released under the Artistic License. Its a much more feature-rich version as well as being Open Source! For a copy of the Artistic License, see the files that came with your Perl distribution.

The code was developed during my time at Orangatango. It has been released as open source with the blessing of the controlling entities there.