tahoe-lafs/trac-2024-07-25

Allow N, K, and H to be specified per command. #2767

New issue

Open

opened 2016-04-02 20:00:27 +00:00 by PRabahy · 2 comments

PRabahy commented

2016-04-02 20:00:27 +00:00

Owner

It would be nice if there were more places to specify N, K, and H than just the tahoe.cfg file. For example, if I have a very important file that I'm uploading, I might increase K or H. On the other hand, if I'm uploading something big like a movie, I might turn up N for that file to make the disk usage smaller.

I could also see some benefit of having these recorded per alias in the .tahoe\private\aliases file. For any upload action to a specific alias, I would expect the alias definition to override tahoe.cfg.

It would be nice if there were more places to specify N, K, and H than just the tahoe.cfg file. For example, if I have a very important file that I'm uploading, I might increase K or H. On the other hand, if I'm uploading something big like a movie, I might turn up N for that file to make the disk usage smaller. I could also see some benefit of having these recorded per alias in the .tahoe\private\aliases file. For any upload action to a specific alias, I would expect the alias definition to override tahoe.cfg.

tahoe-lafs added the

code-frontend-cli

labels 2016-04-02 20:00:27 +00:00

tahoe-lafs added this to the undecided milestone 2016-04-02 20:00:27 +00:00

PRabahy commented

2016-04-02 20:00:56 +00:00

Author

Owner

Somewhat related to #84 and #1252.

Somewhat related to #84 and #1252.

dawuud commented

2016-04-03 09:42:39 +00:00

Author

Owner

+1!

I agree the aliases file would be a convenient place to store this information... although that does lead me to remark that then we'd have structured data inside a text file which the user is responsible for editing; therefore we should replace the aliases file with aliases.yaml

What would the commandline options look like?
I guess the new options should apply to the tahoe put, cp and backup commands
and if unspecified default to the N,K,H as specified in the tahoe.cfg

+1! I agree the aliases file would be a convenient place to store this information... although that does lead me to remark that then we'd have structured data inside a text file which the user is responsible for editing; therefore we should replace the **aliases** file with **aliases.yaml** What would the commandline options look like? I guess the new options should apply to the **tahoe put, cp and backup commands** and if unspecified default to the N,K,H as specified in the tahoe.cfg

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#2767

No description provided.