Free web front end for ftp software for linux

OBEXFTP Front-End is very effective Java Swing application that uses the ObexFTP under the hood to make easier to manipulate the file system of OBEX-enabled devices.
The Open OBEX project, which is an open source project hosted in SourceForge.net, is the most successful implementation of the OBEX (OBject EXchange) protocol for Open Source Unix-based Operating Systems. Besides, it supports a wide range of devices of different models and vendors.
The only bad thing about this project is that the Open OBEX is a set of command-line programs, and they are not so friendly to the end users. We have been using the Open OBEX for some time, and we felt the need of a friendly user interface to make things easier for us - the users.
So, ObexFTP front-end is a simple - but nice - Java Swing application that uses ObexFTP under the hood to make easier to manipulate the file system of OBEX-enabled devices.
Main features:
- navigate through the devices files;
- create folders in the device;
- send file(s) to the device;
- download file(s) to your computer;
- delete files and folders;
The ObexFTP has been tested in the following Operating Systems:
- Slackware 12.0
- Ubuntu 7.0.4
If youre successfully running ObexFTP front-end in other Operating System than those listed here, please let us know!

The CSound Front-End provides CSound users with a GUI with a clean and efficient layout.

The main window has been redesigned. The engine input frame is a mutant widget that can accomodate different styles of input selection (in the picture we have orc/sco pair, all-in-one .csd file and orc/generator) as well as most kinds of orc/sco pre-processing.

At the moment you switch from between the input frames using the +/- buttons (ugly!). Settings are saved separately for each frame. From the programmers point of view, writing a pre-processing plug-in now means to write a new engine input frame class.

The option window is still the same. As general GUI design guide line, Im trying to use few complex windows instead of 10s of little windows.

As side effect of the routing re-design, the logger window as been simplified. From the only menu available you can still start an external generator, assigning the logged engine as default route.

Web Domain Manager is a PHP based product to add in a new domain to a server, by just filling out the domain name and putting in the ip, username, and password it will setup the new domain on the server by doing the following:
- Adding the config to Apache
- Adding a new user to the system for FTP Access
- Copying over a default site if you have one available
- Adding the domain into Qmail/vpopmail if you want that setup
- Makes the config file for awstats
- Also makes a file you can add into cron to update awstats automaticly
- Restarts apache with the new config
- Runs from cron every minute to make adding the domains near real time
The Script is made up of two parts, the backend script (AddDomainScript-0.05) which runs from cron every minute and adds any new domains that need added.
And then you need a front end script, I am going to have three of them, One for a administrator, One for a Reseller, and one where a customer could signup on your website.
If you have more than one webserver you just need a copy of the backend script running from each of those servers and it will check a central database for the updates so you can control an unlimited amount of server from just one frontend script, so administrating your servers is all done from one page!

Chestnut FTP Search is a web application to search for files on FTP servers. Files can by searched only by file/directory names, nor be file contents. Users can query files by part of the file name, the entire file name, a regular expression, or a shell pattern.
The program is written in Python using web.py framework. To store file indexes PostgreSQL or MySQL is use.
Main features:
- Four search modes: partial match, exact match, regular expression, shell pattern. Every mode can by case sensitive or case insensitive
- Character set can by specified for particular server to allow non ASCII file names.
- Multi-threaded indexer
- i18n support

file*HANDLER project is primarily a Perl script which coordinates some free media conversion packages (cited later) with a PostgreSQL back end accessing server to index and serve binary and text files direct from the database. A simple CGI file with embedded AJAX makes calls to this server which is also constantly looking for other alive f*H servers on the Internet.
Since the server caches media into the SQL database on demand, as the network grows, the network improves.
Its gridded directory sharing/browsing/searching with streaming audio/video as well as flat text/doc/pdf/image display for everyone. Its written with a few hooks for tags that would be included in your actual front page so that the UI is discard-able -- anyone can quickly rewrite a whole new [GT]UI without having to worry about the syntax of the newest version of dojo.licio.r or whatever.
If you wanted to ignore the JS/HTML/CSS hooks then you can easily use the system to make direct requests that just return lists formatted as HTML table-bodies. In other words, the markup IS the markup.
As such, Ive whipped up a Dojo 0.2 Widget that coordinates the serving backend with a UI so anyone can embed f*H functionality anywhere, or easily customize a provided default page.
A file*HANDLER server is really a few constituent parts Ive tied up for you (top down):
- A local web page providing the UI(served by an HTTP server of your choice) that is generated by a cgi script with embedded AJAX.
- A secondary portion of the same CGI script, acting as middle-ware, which communicates, via AJAX, with the local front page to reconcile asynchronous JavaScript requests with the file*HANDLER sub-network back-end.
- An always-on network server written in PERL that serves to the front and end communicates laterally with everyone elses file*HANDLER back-end PERL server additionally, it manages indexing of content directories you choose to serve.
- A PostgreSQL database that is accessed only via internal PERL routines called from your front page.
So for example, a remote user comes to your site. First, not only can they browse and search your files, but they can also browse and search the files of anyone else hosting a file*HANDLER server that your local server knows about. (file*HANDLER identifies other servers on the network automatically). The user can now read/view/listen/watch by stream any content they find from whomevers server. Theres no download, so theres so actual sharing, just direct streaming to the users browser.

TwoFTPd provides a simple, secure, efficient FTP server.
Twoftpd is an FTP server that strives to be secure, simple, and efficient.
None of the commands can cause execution of other programs, and the normal model of execution does a chroot to the logged in users directory immediately after authentication.
The name "twoftpd" comes from the fact that there are two parts to the server: an authenticating front end, which contains no file or data transfer code, and one of two back ends, which contain all the data transfer code.
Enhancements:
- Added a fake listing routine to twoftpd-drop, to avoid errors on GUI clients that require LIST or NLST.
- Fixed a compile failure on FreeBSD in the newer MDTM command. Thanks Sergei Kolobov.