Free membership software for linux

Membership project allows you to keep accurate and up to date membership records online.
Features membership import, to bring your membership in from another software package. Also features membership export feature for creating mailings.
Search your membership and store information and pictues about each member.
Enhancements:
- This release fixes a few minor bugs found in the authentication module.

Number::Interval is a Perl module that can implement a representation of a numeric interval.

SYNOPSIS

use Number::Interval;

$i = new Number::Interval( Min => -4, Max => 20);
$i = new Number::Interval( Min => 0 );

$is = $i->contains( $value );
$status = $i->intersection( $i2 );

print "$i";

Simple class to implement a closed or open interval. Can be used to compare different intervals, determine set membership, calculate intersections and provide default stringification methods.

Intervals can be bound or unbound. If max is less than min the interval is inverted.

vSignup providea a member registration script which utilizes vAuthenticate for its security handling.

vSignup is a member registration script which utilizes vAuthenticate for its security handling. This handy script features email verification, sending confirmation email message, restricting email domains that are allowed for membership, and much more.

1. Please read the documentation.html thoroughly before attempting to install vSignup 2.5 much more send a support email

2. Please read the faq.txt first before sending a support email as most issues are resolved or explained well in the said file

3. Implementation, customization, and modifications to the code are available for a minimal fee. If you dont want to shell out some cash, go through the documents a couple of times then send me a support email and Ill help you out as much as I can. For cases wherein the only solution is a customization, you either do the customization yourself or let me do it for you (chargeable, of course)

GNU ccRTP is an implementation of RTP, the real-time transport protocol from the IETF (see RFC 3550, RFC 3551 and RFC 3555). ccRTP is a C++ library based on GNU Common C++ which provides a high performance, flexible and extensible standards-compliant RTP stack with full RTCP support. The design and implementation of ccRTP make it suitable for high capacity servers and gateways as well as personal client applications.
In designing ccRTP, we have taken into account that RTP has been defined as an application level protocol framework rather than a typical Internet transport protocol such as TCP and UDP. Thus, RTP is hardly ever implemented as a layer separated from the application.
Consequently, RTP applications often must customize the adaptable RTP packet layout and processing rules, timing constraints, session membership rules as well as other RTP and RTCP mechanisms. ccRTP aims to provide a framework for the RTP framework, rather than being just an RTP packet manipulation library.
Support for both audio and video data is also considered in the design of ccRTP, that can do partial frame splits/re-assembly. Unicast, multi-unicast and multicast transport models are supported, as well as multiple active synchronization sources, multiple RTP sessions (SSRC spaces), and multiple RTP applications (CNAME spaces). This allows its use for building all forms of Internet standards based audio and visual conferencing systems.
GNU ccRTP is threadsafe and high performance. It uses packet queue lists for the reception and transmission of data packets. Both inter-media and intra-media synchronization is automatically handled within the incoming and outgoing packet queues. GNU ccRTP offers support for RTCP and many other standard and extended features that are needed for both compatible and advanced streaming applications.
It can mix multiple payload types in stream, and hence can be used to impliment RFC 2833 compliant signaling applications as well as other specialized things. GNU ccRTP also offers direct RTP and RTCP packet filtering.
GNU ccRTP uses templates to isolate threading and sockets related dependencies, so that it can be used to impliment realtime streaming with different threading models and underlying transport protocols, not just with IPV4 UDP sockets. For a more detailed list of ccRTP features you can have a look at the programmers manual.
At its highest level, ccRTP provides classes for the real-time transport of data through RTP sessions, as well as the control functions of RTCP.
The main concept in the ccRTP implementation of RTP sessions is the use of packet queues to handle transmission and reception of RTP data packets/application data units. In ccRTP, a data block is transmitted by putting it into the transmission (outgoing packets) queue, and received by getting it from the reception (incoming packets) queue.
Main features:
- Highly extensible to specialized stacks.
- Supports unicast, multi-unicast and multicast. Handles multiple sources (including synchronization sources and contributing sources) and destinations. Also supports symmetric RTP.
- Automatic RTCP functions handling, such as association of synchronization sources from the same participant or NTP-RTP timestamp mapping.
- Genericity as for underlying network and transport protocols through templates.
- It is threadsafe and supports almost any threading model.
- Generic and extensible RTP and RTCP header validity checks.
- Handles source states and information as well as statistics recording.
- Automatically handles SSRC collisions and performs loop detection.
- Implements timer reconsideration and reverse reconsideration.
- Provides good random numbers, based on /dev/urandom or, alternatively, on MD5.
There are several levels of interface (public interface, public or protected inheritance, etc) in ccRTP. For instance, the rtphello demo program distributed with ccRTP just uses the public interface of the RTPSession class and does not redefine the virtual method onGotSR, thus what this program knows about SR reports is the information conveyed in the last sender report from any source, which can be retrieved via the getMRSenderInfo method of the SyncSource class.
On the contrary, the rtplisten demo program redefines onGotSR by means of inheritance and could do specialized processing of these RTCP packets. Generally, both data and control packets are not directly accessible through the most external interface.
All this functions are performed through a few essential classes and types. The most basic ones are the enumerated type StaticPayloadType, and the classes StaticPayloadFormat and DynamicPayloadFormat.
The most important ones are the classes RTPSession, SyncSource, Participant and AppDataUnit, that represent RTP sessions, synchronization sources, participants in an RTP application, and application data units conveyed in RTP data packets, respectively.
When using ccRTP, both sending and receiving of data transported over RTP sessions is done through reception and transmission queues handled by the RTP stack. In the most common case, a separate execution thread for each RTP session handles the queues. This case is the threading model that we will generally assume throughout this document. Note however that ccRTP supports other threading models, particularly ccRTP supports the use of a single execution thread to serve a set of RTP sessions. It is also possible to not associate any separate thread with any RTP session, manually calling the main data and control service methods from whatever other thread.
The basic idea for packet reception with ccRTP is that the application does not directly read packets from sockets but gets them from a reception queue. The stack is responsible for inserting received packets in the reception queue and handling this queue. In general, a packet reception and insertion in the reception queue does not occur at the same time the application gets it from the queue.
Conversely, the basic idea for packet transmission with ccRTP is that packets are not directly written to sockets but inserted in a transmission queue handled by the stack. In general, packet insertion and transmission occur at different times, though it is not necessary.
In order to use ccRTP, you must include the main header (#include < ccrtp/rtp.h >. Two additional headers are provided by ccRTP:
#include < ccrtp/rtppool.h
Classes for pools of RTP service threads.
#include < ccrtp/rtpext.h >
Classes for RTP extensions which are not mature yet.
You must also link in the library, currently ccrtp1.
Enhancements:
- Brand new support has been introduced for Secure RTP Profile (srtp) as per RFC 3711.
- This release also supports a new add-on package, libzrtpcpp, that directly offers native zfone (zrtp) compatible encryption capabilities to Common C++ RTP based applications.
- This is the first softphone client to use both Common C++ RTP srtp and zrtp support.

If you are having users authenticate with real Unix login ID over the net, using something like my mod_authnz_external / pwauth combination, and you want to do access control based on unix group membership, then mod_authz_unixgroup is exactly what you need.

Lets say you are doing unix passwd file authentication with mod_authnz_external and pwauth. Your .htaccess file for a protected directory would probably start with the following directives:

AuthType Basic
AuthName mysite
AuthBasicProvider external
AuthExternal pwauth

That would cause mod_auth_basic and mod_authnz_external to do authentication based on the Unix passwd database. Mod_Authz_Unixgroup would come into play if you wanted to further restrict access to specific Unix groups. You might append the following directives:

AuthzUnixgroup on
Require group staff admin

This would allow only access to accounts in the staff or admin unix groups. You can alternately specify groups by their gid numbers instead of their names.

Or you could use mod_authz_unixgroup together with the standard apache module mod_authz_owner to do something like:

Require file-group

This would allow access to the page, only the user was a member of the unix group that owns the file.

Though it makes the most sense to use mod_authz_unixgroup with unix passwd authentication, it can be used with other databases. In that case it would grant access if, (1) the name the user authenticated with exactly matched the name of a real unix account on the server, and (2) that real unix account was in one of the required groups. However, I think this would be a pretty senseless way to use this module. I expect that it will really only be used by user of mod_authnz_external and pwauth.

DB_cart Class is a MySQL shopping cart script that can be used with third party product catalogues and membership systems. The MySQL database structure is neutral to existing systems.
DB_cart Class can handle the shopping cart (add, update, and empty) and checkout process (set the shipment address and email the order).
For existing cart users, the shopping cart is still available upon the users next visit and is visible by checkout. The last option is configurable togther with a time period.
Enhancements:
- There are modifications and improvements inside the main class file, several examples, and the table structure has been extended.
- There two additional fields for the shipment values (name2 and address2).
- All messages are available in German, English, and Dutch.
- The standard text inside the email messages is in external files now; this content is parsed inside the improved email method.

Since MySQL is the most popular SQL server that is used in conjunction with web sites, there was a need for incremental backup utility. ZZEE Active SQL Backup is designed for clients of web hosting companies, and can be useful to system administrators as well.
Main features:
- Can perform *incremental* backup of MySQL database
- Can perform full backup of MySQL database
- Can replicate database
- Can process SQL queries
- Can dump database structure
- Can suggest database changes needed to process incremental backup
- Can send data backed up by email
- Can transfer backed up data by FTP to other computer (if Net::FTP is installed)
- Can compress backed up data
Usage synopsis
Active SQL Backup can do incremental or full backups of MySQL database as often as needed. It is suitable both for the clients of web hosting companies who can not get access to MySQL update logs and for the host administrators. Backup syntax is:
shell> ./zmdb.pl -b
It stores backup files in BACKUP_DIR, specified in user_settings.txt, named like YYYY_MM_DD_hh_mm_ss.sql[.gz]. The backup files consist of series of SQL INSERT statements and may contain DELETE statements. The database scheme is stored in file database_name.create.sql. If gzip is available, then Active SQL Backup automatically uses it to compress stored data. The program can automatically send backed up files by email or upload to the other computer by FTP.
If the system fails, Active SQL Backup can restore the database. Restore syntax for incremental backups is:
shell> ./zmdb.pl -r
If you make full backups, restore syntax is the following:
shell> ./zmdb.pl -e < BACKUP_DIR/database_name.create.sql
shell> ./zmdb.pl -e < BACKUP_DIR/YYYY_MM_DD_hh_mm_ss.sql &
The first line is needed to restore database structure, and the second is the *most recent* data file. You may need to "gunzip" it before supplying to restore.
You can use the program to dump database structure
shell> ./zmdb.pl -s > structure_dump_file
or to process queries. The latter feature is useful if you need to process queries regularly, for example, to update membership status of the users of your online service. The syntax to execute SQL queries is:
shell> ./zmdb.pl -e < some_sql_file
Where format of some_sql_file is the same as with Mysql utility: SQL statements are separated by semicolon. Note that if you pass SELECT queries to Active SQL Backup, then no result will be returned.
Syntax summary is:
zmdb.pl [SINGLE_OPTION]
-a --advice suggest database modifications and tables_config.txt
-b --backup backup database structure and data
-e --execute execute SQL queries [from STDIN]
-h --help print this screen
-r --restore restore database structure and data
-s --structure dump database structure [to STDOUT]

Tournament Pool and Bracket Tracker is a Java Servlet based generic game tournament pool bracket tracking application suitable especially for the NCAA basketball championship tournament.
Features include bracket entering, multiple scoring systems, multiple users, groups, pools, etc.
Tournament Pool and Bracket Tracker contains everything you need to run a tournament pool.
It supports small groups or organizations who wish to provide an NCAA basketball tournament pool without a lot of administrative work in registering users or in calculating up-to-date results and possibilities.
Though it was built with the NCAA "March Madness" tournaments in mind, it should be able to handle other sport tournament pools that use straight forward brackets.
As an administrator, you will first log into the system like any other user. Any user can create a group and aministrate their own pool. A group is a set of players that play together in any number of pools.
Pool adminstrators can choose from many different scoring systems. Scoring systems can be set up dynamically in the database. When you set up a group, you have a choice. Either you can tell the users about the pool, and have them register, then notify you. You would then add the users to the group manually. This keeps membership totally within your control.
However, you can also create an invitation code. Youll then have an link to the system with that invitation code embedded. You can send this link to your users. When they click the link and login (with a possible detour through registration), they will be automatically added to your group.
They can then create their bracket and add it to a pool without your direct involvement. You do risk that the email gets circulated to others and people you dont intend to enter your group do.
Players can create as many brackets as they like, name them, leave them unfinished, come back to them later, etc. Players can add a bracket to a pool once the bracket is finished either from the bracket interface page or from the pool interface page.
Once a tournament is underway, users can keep track of their progress as the administrator for a tournament updates the results of games. Tournaments results are updated by the administrator with the same interface players use to enter their brackets.
Players are prevented from editing their brackets once it has been added to a pool that has a tournament underway. Tournament administrators can delegate the duty of keeping game results up to date to others if they arent going to be around for some of the games via a simple interface.
This allows players to come into the system regularly during the tournament and check their results and the standings much quicker than your typical spreadsheet based systems. If something is updated wrong, the players will keep you honest. The results show current, remaining, and maximum available points.
Any user can inspect the other players brackets in the pool. The brackets are presented with good picks in the green and bad picks in the red.
Version restrictions:
- Right now, all of the bracket, tournament, and teams setup is done via SQL scripts. I typically am working on the scripts the night they are announced. The priority list for the user interface work so far has been first to make the player experience nice, second to make the in-tournament administration nice, and only third to make the tournament setup nice. Hopefully by the time March 2006 rolls around this third area will be improved.
- At this point the bracket system wont handle highest seed meets lowest seed type of brackets. Unfortunately, this rules out using this system for the NFL Playoffs for the time being. Ive been working on this, but it is hard nut to crack.
Installation:
- Install MySQL and Tomcat
- Put the tournament.war file in the tomcat webapps folder.
- To get the database ready, run the following commands from the mysql.exe tool in the following order:
. [path]configdb.sql
. [path]configncaa.sql
. [path]configncaa-teams.sql
. [path]configncaa-2004.sql (optional)
. [path]configacc.sql (optional)
. [path]configacc-2005.sql (optional)
. [path]configncaa-2005.sql
You need to grant privileges in mysql as well:
GRANT ALL PRIViLEGES ON *.* TO testuser@localhost
IDENTIFIED BY testpw WITH GRANT OPTION;
Make some tweaks to the [tomcat home]/conf/web.xml file. Uncomment the following:
< !-- The invoker servlet -->
< servlet>
< servlet-name>invoker
< servlet-class>
org.apache.catalina.servlets.InvokerServlet
< /servlet-class>
< init-param>
< param-name>debug
< param-value>0
< /init-param>
< load-on-startup>2
< /servlet>
and
< !-- The mapping for the invoker servlet -->
< servlet-mapping>
< servlet-name>invoker
< url-pattern>/servlet/*
< /servlet-mapping>
This enables the autoinvoker servlet, which maps from URLs to class names which happen to be J2EE servlet classes. Some people consider this a security risk, which is why it is disabled by default. Ive never had an issue so long as I know all of the servlet classes I have in the system. This can be changed. If you consider it an issue, let me know via a feature request.
- Start MySQL and Tomcat
- Go to http://localhost:8080/tournament/
Enhancements:
- This release adds many new options for the tournament pool administrator.
- You can do tie breakers, not show the players brackets to each other until the tournament starts, limit the number of brackets per player, and run a pool starting later in a tournament, such as starting at the Sweet 16.
- There is also a new interface for setting the start date and time of the tournament, sorting enhancements, the ability to edit pool settings, ranking the brackets of a running pool, and players may reset their passwords.