tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki

add private storage #33

New Issue
Closed
opened 2007-05-04 05:46:53 +00:00 by zooko · 9 comments
zooko commented 2007-05-04 05:46:53 +00:00
Copy Link

Add the option of storing a file without submitting its URI to the vdrive server.

Add the option of storing a file without submitting its URI to the vdrive server.
zooko added the
code
major
enhancement
 labels 2007-05-04 05:46:53 +00:00
faried commented 2007-05-04 22:12:32 +00:00
Owner
Copy Link

Patch against webish.py sent to zooko.

Patch against webish.py sent to zooko.
zooko commented 2007-05-04 22:19:07 +00:00
Author
Copy Link

Attachment 6.1.txt (207 bytes) added

**Attachment** 6.1.txt (207 bytes) added
6.1.txt
207 B
zooko commented 2007-05-04 22:19:25 +00:00
Author
Copy Link

Attachment 6.2.txt (2738 bytes) added

the patch from Faried

**Attachment** 6.2.txt (2738 bytes) added the patch from Faried
6.2.txt
2.7 KiB
faried commented 2007-05-06 20:01:40 +00:00
Owner
Copy Link

Attachment ticket-33.diff.txt (2809 bytes) added

a working patch to add private uploads

**Attachment** ticket-33.diff.txt (2809 bytes) added a working patch to add private uploads
ticket-33.diff.txt
2.7 KiB
faried commented 2007-05-06 20:10:44 +00:00
Owner
Copy Link

It works. I'm not sure if it's the right way to do it, but it does upload files without reporting them to the vdrive. It also prints out the URI in the results div on the web page, as well as in twisted.log.

It works. I'm not sure if it's the right way to do it, but it does upload files without reporting them to the vdrive. It also prints out the URI in the results div on the web page, as well as in twisted.log.
tahoe-lafs added the
fixed
 label 2007-05-06 20:11:05 +00:00
faried closed this issue 2007-05-06 20:11:05 +00:00
zooko commented 2007-05-16 15:59:25 +00:00
Author
Copy Link

Oops, I forgot to apply this patch until just now. changeset:78e537de0c77ecd5

Okay, now this one we can definitely unit test. Here is the current code-coverage view of the files touched by this patch:

http://allmydata.org/tahoe-figleaf/figleaf-edgy-187/allmydata.webish.html

Notice that render_results() and uploadprivate() are not completely tested. Oh, and notice that upload() itself isn't, either!

Oops, I forgot to apply this patch until just now. changeset:78e537de0c77ecd5 Okay, now this one we can definitely unit test. Here is the current code-coverage view of the files touched by this patch: <http://allmydata.org/tahoe-figleaf/figleaf-edgy-187/allmydata.webish.html> Notice that render_results() and uploadprivate() are not completely tested. Oh, and notice that upload() itself isn't, either!
zooko removed the
fixed
 label 2007-05-16 15:59:25 +00:00
zooko reopened this issue 2007-05-16 15:59:25 +00:00
zooko commented 2007-06-29 23:16:07 +00:00
Author
Copy Link

Re-assigning to faried in the hopes that he'll write a unit test for it.

Re-assigning to faried in the hopes that he'll write a unit test for it.
warner added
minor
0.4.0
 and removed
major
 labels 2007-07-02 19:45:22 +00:00
warner commented 2007-07-11 22:30:41 +00:00
Copy Link

Given that we now have per-client private directories, is it still useful to expose a web interface to uploading files without attaching them to any directory?

The answer may be yes.. I'm just curious about the use case. If we do have this feature, it should go on a page that is reached from the top-level welcome page, rather than from any particular directory. The directory pages should be reserved for operations that affect their related directory, whereas an unlinked URI-only file upload doesn't involve a directory at all.

Given that we now have per-client private directories, is it still useful to expose a web interface to uploading files without attaching them to any directory? The answer may be yes.. I'm just curious about the use case. If we do have this feature, it should go on a page that is reached from the top-level welcome page, rather than from any particular directory. The directory pages should be reserved for operations that affect their related directory, whereas an unlinked URI-only file upload doesn't involve a directory at all.
warner added
code-frontend-web
 and removed
code
 labels 2007-08-14 18:56:12 +00:00
zooko added
0.6.0
 and removed
0.4.0
 labels 2007-09-25 04:27:09 +00:00
zooko added this to the undecided milestone 2007-09-25 04:27:09 +00:00
warner commented 2008-02-06 09:50:06 +00:00
Copy Link

I've added an upload link from the front welcome page which allows you to upload a file and get back a URI, with no vdrive directories involved at all. I believe that closes this issue.

I've added an upload link from the front welcome page which allows you to upload a file and get back a URI, with no vdrive directories involved at all. I believe that closes this issue.
warner added the
fixed
 label 2008-02-06 09:50:06 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No Milestone
eventually
Assignees
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#33
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?