Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We want to get functionality similar to Yousendit or one of the other services that allows end users to upload large files. But we have a few Linux servers and want to use these instead of a third parties.

There seems to be software for practically everything else for Linux, I can't believe there isn't something that will meet our needs.

share|improve this question

closed as not constructive by Bryan, Michael Hampton, Zoredache, voretaq7 Dec 12 '12 at 1:57

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

I had a similar requirement in my company, solved it with this:

It's exactly like yousendit, you upload the file, it's got even the progress indicator, and you can send an email, even with a pwd to type in to download the file. It's brilliant!

Just one thing: remember to turn off output_buffering by adding this to your .htaccess:

php_value output_buffering off

If you don't do it, every download will require as much php memory as the file size (which can easily cripple your server or will result in a 500 error).

Hope this helps :)


share|improve this answer

Do you really need a Web interface?

Externally: a public Web server serving a directory accessible by a CIFS share, which users can e-Mail out. BasicAuth configuration for password protection, if necessary. Client side tools for encryption. Tons of options here in general.

Internally: wiki and general file sharing solutions such as NFS and SAMBA. Again, tons of options.

Have you looked through Freshmeat and Sourceforge?

share|improve this answer
Sorry, we do need a web front end. The client will want something that looks swish and also won't want to have to do anything complicated on each end users' machine. We don't want to be limited by email file constraints so that's not an option either. Ideally it'd be open source so we can customise it if need be. But we don't mind paying for it. – wkstar Mar 31 '10 at 12:46
@user39234, you should edit your question to add the extra details, as others may not read comments before answering. – John Gardeniers Apr 1 '10 at 0:11
John provides good advice. I have no intent to further contribute to this and I'd have already deleted my answer had your comment not clarified the initial question. – Warner Apr 1 '10 at 3:43

I've used a rebranded for a while and it worked great, but my use is sporadic and I couldn't justify paying for it when I run my own servers. I just installed and configured Droopy on Ubuntu 12.04. It uses Python. It seems pretty solid.

share|improve this answer

If you don't mind spending money, I've (easily) branded/integrated a YouSendIt "corporate" account within a Website I was doing contract work for: we embedded the YouSendit form into a page on the site; took all of 15 minutes maybe.

You can customize the email message, logo, etc. they charge based on how many uploads you do per month and how much data if I recall correctly, but it wasn't much. is really slick and free up to 100MB in file size; may also have an embedding/customizing option.

share|improve this answer has one, but it's $139 USD, and no idea how well it works either.

share|improve this answer
Thanks, I'll take a look. – wkstar Mar 31 '10 at 12:48

Isn't dropbox what you need?

share|improve this answer

Apache has a tendency to use as much memory per process as the uploaded file is in size. That will kill your server very soon if you continuously receive large files.

Have you tried to setup lighttpd for your upload receiving needs? It should behave in a more sane manner: saving chunks to a temporary directory you define and not consuming all the RAM you have.

share|improve this answer
Apache was not mentioned in the question (and the tendency depends totally on the script/method used to receive uploads, apache itself can stream perfectly fine). – eckes Dec 13 '12 at 2:43

Not the answer you're looking for? Browse other questions tagged or ask your own question.