Free dl download ticket service software for linux

dl Download Ticket Service project is a minimalist and rough download ticket service with automatic expiration, written in PHP. Ive been using this service as an email-attachment replacement for my company, but there are no plans on extending it. It will remain minimal: no fancy features, just bug fixes.
Installation:
Copy the "htdocs" directory to a directory of choice under your web server. Configure the needed parameters inside "include/config.php" to reflect the external url, main password, etc. The "include" directory must not be accessible: if you use apache, the included .htaccess file should be sufficient; consult your web server documentation otherwise.
A spool directory outside of the web server root must be accessible to the web server process. In the example "include/config.php" this is configured as "/var/spool/dl". If you web server runs as "nobody:nogroup", issue:
mkdir -p -m770 /var/spool/dl
chgrp nogroup /var/spool/dl
to create correctly this directory.
The maximal upload limit is determined by several PHP configuration parameters:
file_uploads: must be "On".
upload_tmp_dir: ensure enough space is available.
upload_max_filesize: change as needed.
post_max_size: must be at least 1M larger than upload_max_filesize.
The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter. You can also set these parameters with ini_set() inside "include/config.php" or through apaches directives to localize them to the installation path.
There are several bugs in the dba_open() function in PHP 4.x which cannot be fixed. If you can, upgrade PHP to at least 4.3.5. If you cannot upgrade, you need to configure the "$dbHandler" parameter to something available to your PHP installation (usually db3/db2/dbm) and use the Berkeleys DB "db4_load" utility to create an empty database:
echo | db4_load /var/spool/dl/data.db
echo | db4_load /var/spool/dl/user.db
chmod 770 /var/spool/dl/*.db
chgrp nogroup /var/spool/dl/*.db
Depending on your system, you may have to use "db3_load/db2_load/etc" instead of "db4_load". Sometimes these utilities are part of "db*-util" packages under several linux distributions. If you have PHP 4.3.5 or greater, this is done automatically.
Ticket expiration is performed automatically when any web page is requested. This means that expired downloads will still occupy space on the spool directory until a web page is first serviced. If you need to ensure that the spool is purged regularly (for very low traffic servers), setup a scheduled job that requests the "http://dl.example.com/d/" page. Under UNIX, setup a cron entry like this:
0 0 * * * wget -q -O /dev/null "http://dl.example.com/d/" > /dev/null
Version restrictions:
- Tested with all mayor and minor browsers.
- Tested with PHP 4.2/4.3.
- Byte ranges are currently not supported.
- The submit button is not disabled correctly with Internet Explorer 6 (works on other graphical browsers however).

LaTeX Service project is a small service which converts LaTeX into an image.
It returns a LaTeX rendering of selected text as a TIFF image.
Enhancements:
- Many things could be improved, its just a 0.1 release... but it works

Download Embedded extension downloads all or selected embedded objects on a webpage. Can be used for downloading movies, mp3s, flash, quicktime, or other embedded files.

When the Download Embedded plugin detects an embedded object, a small red arrow will appear on the status bar at the bottom of your firefox window. Just click that and either download them all or pick which ones you want to download. Enjoy!

If you were using the old download embedded (0.1), -=please=- remove it before installing this one.

Download Slave provides a remote-controlled download slave.
The Download Slave is a very flexible script which is controlled via eMail and stores files requested for downloading on the servers harddisk or sends them via eMail to the user who asked for them. Users are identified by their eMail address and a personal password, so only authorized users can use the service.
Main features:
- users identified by their eMail address and a personal password
- a real multi user mode, so each user has his own home and can have his own CD-R burnt.
- corporate mode: all downloaded files are stored in one base directory
- every download is logged
- user gets a status mail about his download request
- slave is controlled via commands in the eMail message body
- download things onto the servers HDD... (also more than one URL per eMail request possible...)
- show already downloaded files (that are on the servers HDD)
- change own password
- download files onto the servers HDD and send them via eMail to you (split into parts of 1MB). The last one of such a multi part eMail has an attached script to rejoin the large file...
- online help
- an index file which holds who downloaded what and when and a short description given by the downloading user in his mail subject

Son of Service (SOS) is a multiuser volunteer management database for non-profits, charities, schools, churches, and clubs. SOS will keep track of your volunteers, their contact information, availability, work history, comments, reminders, and relationships.

It will help you quickly find the right volunteer for the job and e-mail him, and it will make reports about how you are using volunteers.

SOS is a helpful tool for organizations with many volunteers or multiple volunteer coordinators.

Your organization helps people for free, and your volunteers work for free. So you know there is a "free lunch."

SOS is free. Its free from charge: notice there is no menu option for purchasing or ordering. But SOS also provides freedom from many restrictions. Download the program, install it, and use it without buying expensive licenses.

Use it on as many systems with as many users and volunteers as you have. Use your choice of server operating system and RDBMS. (You dont need to buy a RDBMS or other server software.) You can even modify SOS to meet your specific needs because the full source is available to you.

PHP Trouble Ticket project provides a centralized means of problem reporting and tracking in multi-user environments (medium to large companies, development groups, etc.).
It helps direct problem reports to the responsible administrator(s), keeps track of the status of a problem being worked on, and offers an up-to-date list of recent changes applied. It aims to be widely configurable, easy-to-use even for those not technically inclined, and multi-language capable.
Main features:
- problem reporting
- submitting update-info
- email-notification of administrators
- email-notification sent to problem reporter after ticket is modified or closed
- watch-function for tickets to be kept up to date on progress of chosen tickets
- file attachments (including on-the-fly virus checking with external virus-scanner)
- powerful list/search function with paged browsing
- tickets can be set into relations/dependencies
- ticket quick-search function directly from the main index
- quickly access all your own tickets from the main index page
- printer-friendly display of lists and ticket details
- css style sheet support for easy customisation
- easy multiple-select/close/delete functions
- username/password protected logins
- varying levels of permissions/access-rights
- the scope of unprivileged users can be limited to their own tickets
- new users can either sign up at the login page or be created by the superuser from the administration page
- detailed userlist available for administrators with info on last login and included search function
- online configuration of all major options
- configuration of the expert/administrator information
- deadlines for trouble tickets
- up to five customizable datafields
- changes and entire tickets can be hidden from unprivileged users by the operators
- "locking" areas against change by other administrators
- national language support (included: english, german. Other language files are made available separately on the download page)
- date/Time format configurable to suit national format
- ability of the program to work with PHPs "safe mode" and "open basedir" security mechanisms

MOV, MP4 conversion service is final and working version of my script, which I use to convert files supported by ffmpeg to MOV / MP4 format, supported by my iPod Video G5.

Everything was tested to be easy to use (finally, after installation). If You have any problems with it, just let me know - Ill try to help as far as I can.

INSTALLATION:

Just download "avi2mov" script, and save it in /usr/sbin/ directory (You can save it in any directory, but take care later, because i assume, youve saved it in /usr/sbin/ :) ).

After this, You need to set proper permissions, so use chmod:

chmod +x /usr/sbin/avi2mov

Finally, You need to add this converter to Service Menu. Create file

/usr/kde/3.5/share/apps/konqueror/servicemenus/convert-avi-to-mov.desktop

with Kate for example, and copy and paste this code:

[Desktop Action MediaConvertFile]
Exec=/usr/sbin/avi2mov %U
Icon=reload
Name=Convert selected file to mov / mp4 ...
[Desktop Entry]
Actions=MediaConvertFile
Encoding=UTF-8
Icon=reload
ServiceTypes=video/*
ExcludeServiceTypes=kdedevice

The Bluetail Ticket Tracker (BTT) is a system for creating, storing and keeping track of tickets. A ticket describes an issue of some sort.

It can, for example, be a Trouble Report or a ToDo note. It is available for use (and distribution) under the GNU Public License.

The users of BTT are divided in four different user categories: Staff, Friend, Customer and Anonymous. The access to the data stored in BTT can be tailored for the Friend, Customer and Anonymous groups, while the Staff group has full access rights. This (hopefully) allows BTT to be used both for Open Source Projects as well as in more commercial settings.

In an Open Source Project:

* one or several people (Staff) hosts a site which runs the Ticket handling for a certain application
* a number of people (Staff + Friends) collaborates in the development which also include Ticket handling
* anyone else interested (Customer or Anonymous) may want to check the status of the Tickets (e.g Trouble Reports)

In a commercial setting:

* a company (Staff) runs the Ticket tracker as an aid in their product development.
* the company may be spread geographically or may have development partners (Friends)
* the customers can report problems and track the progression (Customer)

A ticket consists of a number of fields, e.g denoting a release name, component name, responsible person, staus, priority, etc. The actual field values is defined by the Staff when the Bluetail Ticket Tracker is setup. The daily operation of BTT includes creation, editing, searching and viewing of tickets.

The users can also activate the mail alert function which will send a mail to the user when, for example, a new ticket as been assigned to the user.

BTT can also store information about customers which can be useful in a support desk scenario. This makes it possible to connect a ticket with a particular customer. It is also helpful in a support desk scenario where the support engineer quickly need to find information about a customer.

BTT can also store more general information. This Knowledge Base consists of a mail store and a information store.

The mail store makes it possible to retrieve mails (from a POP3 account) and store it locally in a BTT directory. Stored mails can then be searched, viewed and turned into tickets.

The information store is divided in two parts, one external (for users/customers) and one internal (for staff/friends). The external area can for example be used for creating a FAQ (Frequently Asked Question), a HOWTO area. The internal knowledge base is intended for the Staff and/or Friends, and may for example store information such as address lists, how to fill in the expenses form, or contain description of the work process, etc.

Currently BTT supports English, French, German, Spanish and Galician. Adding new languages is easy, one language definition file has to be created with a translation of all text that can be displayed. (If you do this, make sure to send the new language file to the maintainers so that it can be incorporated into the standard release).

Tickets can also be retrieved and stored via a Unix command line interface.