woof: The simple single file server

Here’s nifty toy, with a clever name too: woof, short for “web offer one file.”

2013-03-19-solo-2150-woof-01 2013-03-19-solo-2150-woof-02 2013-03-19-l3-e7548-woof

It’s a one-shot, single use server with a very primitive web interface for uploading as well.

Naturally, between in-house machines it might be easier to use something like scp, rsync or even a standard nfs arrangement.

But the cool part of woof, in my meager opinion, is that all of those things probably require a running daemon.

woof just awaits a connection, and sends its information. Of course, there’s no security, probably no encryption unless you do it manually, and so forth.

I only ran into one jam with woof, and that was trying to send files out beyond my router.

For whatever reason, I couldn’t arrange woof to listen beyond my home network. I blame my router settings, but if you have any ideas, I am willing to listen.

8 thoughts on “woof: The simple single file server

  1. yannanth

    Wait, I’m not really understanding how this works. So the purpose of this is to allow people to download files from a web server program you run on your computer? Can’t you just put it in the folder of your server? Or is it a P2P-like… thing where the first person that comes to the link waits to download it? Please clarify the program’s purpose.

    By the way, can I make a request? I know you don’t like music managers but I couldn’t live without them. I used Cmus for a while but eventually went back to my old graphical one. Could you try to make PyTone (http://www.luga.de/pytone/) build on modern systems? I’m not a programmer and really don’t have a clue what to do beyond following simple instructions. -.- Anyway, the interface seems like more of my thing but I obviously can’t try it. It would be really great if you could look into it.

    1. K.Mandla Post author

      You’re more or less on the money. As best I can tell it’s a one-shot, one-file server that does its work and then shuts down. So yes, first come first served, and nobody after that. Maybe that seems to defeat the purpose, but I actually have a couple of situations where that would be preferable to a full server suite, with the setup and maintenance involved.

      Like I said, I’m fairly sure the author’s intent was not as a LAN file server; of course there are much easier ways to handle that. In my case, I couldn’t wrangle with my router long enough to get it to work from beyond my own home network. But again, I suspect that was my fault.

  2. imgx64

    It’s probably not working because your router is doing NAT. You could forward port 80 to your computer and see if it works (log in to your router’s web interface and look for “port forwarding”).

    1. K.Mandla Post author

      Ah, thank you. I remember Droopy but I couldn’t remember the name. Thanks, I’ll add that to my list.

  3. Pingback: ncp: Possibly the easiest yet | Inconsolation

  4. Pingback: siphon (and ‘Siphon): For simple network transfers | Inconsolation

Comments are closed.