Nephthys provides a web-interface to create file-sharing "buckets", through which data can be shared. Nephthys handles the buckets in the local filesystem of the server. Access and data transfer is done by helper protocols like FTP and WebDAV. For this ProFTPD (FTP) and Apache (WebDAV) seems to be perfect for which also configuration examples are available (see Installation). Some screen captures can be found on the Screenshot page.
Nephthys does handle any authentication mechanism of external applications. The path to the bucket - the directory name is a SHA1 hash - identifies the bucket.
The access mechanism (WebDAV, FTP, ...) needs to be configured so that no directory-listing is possible in the transfer directory. For this example configurations of Apache and ProFTPD can be found on the Installation wiki page. If you for example use a different FTP server which can be secured in a similar way like ProFTPD and want to share your configuration, please post it to the mailing list.
- Multi-Language Support
- user, manage his own buckets
- manager, manage all available buckets
- admin, like manager but handles user management too
- User auto-creation
- if authentication is done via web-server (ldap, kerberos, ...)
- Theme support
- create your own design
- Linux-based operating system
- Apache HTTP webserver (or other which supports PHP5 and WebDAV)
- ProFTPD (or any other suiteable FTP server).
- MySQL, >= 5.0
- SQLite, 2.0
Get a stable release out of the "Files" section. Or checkout the lasted development code out of the GIT repository via:
git clone http://git.netshadow.at/Nephthys.git/
A mailing list is available via firstname.lastname@example.org - make sure you subscribed here https://admin.netshadow.at/cgi-bin/mailman/listinfo/nephthys-users before send a message to the list.
It is not necessary to register on this project website (aka Redmine) for it. Anyway if you want to apply (to open a new issue for example), please send a request to the mailing list first.
Documentation and Howto's¶
How does it work?¶
Basically there are two modes:
"I want to share some files"¶
A user wants to share some files. He has to upload the files to the bucket and afterwards sends the bucket-url to the receiver.
- Via Nephthys the user creates a slot on the server by providing a slot name and a expiring date.
- User will receive an automatically generated email with links to the server, where he can store the files.
- User can then pass these links to the "other" users who should be able to access the uploaded files (FTP or WebDAV).
"Someone wants to share some files with me"¶
- Via Nephthys the user creates a slot on the server by providing a slot name, his own email address, the receivers email address, a expiring date and a short note of the purpose of this slot.
- The "other" users will receive an automatically generated email with links to the server, where they can upload files via FTP or WebDAV. The original sender will get this email in CC.
- Afterwards they notify the original sender that they files are up and can then download the firewalls from the server.
Where does the name "Nephthys" comes from?¶
An old egypt goddess - see this Wikipedia entry for more: http://en.wikipedia.org/wiki/Nephthys
What was the intension to write Nephthys?¶
Many companies (including the one I'm working for) have problems with their mail system, because users are starting to abuse it as a file sharing tool. They are sending a big amount of data through it and are getting quickly upset if their email with a 178MB attachment gets rejected by the mailserver... :-)
Also this becomes quiet expensive if you have some mail archiving tools and higher-level storage systems for your mailboxes.
Common FTP servers with usernames & passwords are often to difficult for "office" users. Not speaking about handling settings for firewalls, proxy servers, ... . For them WebDAV should be a real alternative.