Woof

Configurable path to receive files from the uploading-form

  1. Series trunk
  2. Bug #667831
Bug #667831 reported by Tobias Baldauf
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Woof
Status tracked in Trunk
Trunk
New
Wishlist
Tobias Baldauf
Woof wolowizard

Bug Description

When "woof -U" is invoked, an upload-form to give the host files is created. The path where those files are saved on the host-machine is currently not configurable.

How about offering users a possibility to configure the path as a parameter when invoking Woof in the terminal. For the actual target-audience, the path could be default-set to ~/Downloads/ or, when that folder is not available, use ~/Desktop/. Of course, there might be smarter places even. Suggest them!

Tags: form path upload

Related branches

lp://staging/woofgui
Tobias Baldauf (technopagan)
Changed in woofgui:
assignee: nobody → Tobias Baldauf (technopagan)
importance: Undecided → Wishlist
Tobias Baldauf (technopagan)
tags: added: form path upload
Tobias Baldauf (technopagan)
Changed in woofgui:
milestone: none → wolowizard
Revision history for this message
Alin Andrei (nilarimogard) wrote :

This is also required for packaging woof as a .deb file. Without it, -U doesn't work.

Revision history for this message
Tobias Baldauf (technopagan) wrote :

@nilarimogard / Alin Andrei:
Thank you for your input!

I have opened a new bug (set as Wishlist) for packaging Woof as a .deb file: https://bugs.launchpad.net/woofgui/+bug/671679 If you have knowledge on how to package python-scripts like Woof as .deb files, it would be awesome if you helped us out!

Furthermore: can you elaborate some more on when exactly -U does not work for you? I'd like to make sure I understand correctly so I can do it right one day! :)

Revision history for this message
Alin Andrei (nilarimogard) wrote :

Hello,

If packaged as a deb, woof downloads the file with -U in its folder, right? But packaging it as a .deb, the woof folder would be /usr/bin so it would attempt to download the files received with -U in the /usr/bin folder which is of course impossible. Unless woof is ran with "sudo" which is the worst thing anyone can do :)

That's why a configuration for where the files are saved is a must.

Also, once the other security issues are fixed, sure... I can package woof. It doesn't need compiling or anything so it's quite easy to do (as long as there's a readme with all the woof dependencies - which by the way is currently missing).

Revision history for this message
Tobias Baldauf (technopagan) wrote :

@nilarimogard / Alin Andrei:

You're absolutely right about the path-problem. I'll implement sensible path-parameters in the next few days.

It would be awesome if you would package Woof! There's a group of Woof-developers: https://launchpad.net/~woof which I'd love to see you join! This way, you can easily contribute to Woof.

I'd like to setup a PPA for this Woof-developers-team so we can put your .deb-packages there & distribute Woof to endusers.

Do you use Jabber or another IM so we can chat about details? There's also a new IRC-channel for Woof where we could talk more: irc://irc.freenode.net/#woof

Revision history for this message
Alin Andrei (nilarimogard) wrote :

Sorry, I don't use IRC. I've joined the team.

So, does woof now have a configurable path for receiving files? I've looked in the code but I don't see it - there's only a woof configurable path.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.