Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow files bigger than 64MiB #71

Closed
tmplt opened this issue Sep 20, 2016 · 9 comments
Closed

Allow files bigger than 64MiB #71

tmplt opened this issue Sep 20, 2016 · 9 comments
Milestone

Comments

@tmplt
Copy link
Contributor

tmplt commented Sep 20, 2016

Presently, a 64MiB file size limit is hard coded. I presume https://ptpb.pw doesn't allow anything larger? I'd like to upload files bigger than that on my own pb deployment.

@HalosGhost
Copy link
Owner

That is correct; however, if memory serves, this limit is actually partially due to an inherent limit in pb's stack—i.e., I am not sure you actually can have a pb deployment which allows larger files.

I will go ahead and add a configure option for setting the max file size; that way, it is easy to change at compile-time in case pb ever can do larger files. Does that sounds good?

@HalosGhost HalosGhost added this to the 1.3.0 milestone Sep 20, 2016
@tmplt
Copy link
Contributor Author

tmplt commented Sep 21, 2016

The limit must have been fixed/removed; I just uploaded a 100M file on my own deployment. I had to change my nginx.conf first, though.

I will go ahead and add a configure option for setting the max file size [...]

That would be great, unless it is possible to check if the server would accept the file first? I tried uploading a file which was too large before, but curl didn't error out until the limit had been reached. Is it possible to check before uploading?

@HalosGhost
Copy link
Owner

HalosGhost commented Sep 21, 2016

In an ideal world, there would be a route that pb would offer which would tell you the max file size it would accept; then I would not hard-code it, but instead (when the db is first initialized, or a provider is set through the upcoming --set-provider option) call out to the provider to get the max file size.

However, no such route exists at the moment that I know of. I already have the change staged on my side (very small change really) to add the configure option; I will push it tonight.

@HalosGhost
Copy link
Owner

via d88ba02

@HalosGhost
Copy link
Owner

@tmplt, I have added a page to the wiki to informally track pb instances. Would you care to add your instance to the list (or are you hoping to keep it private)?

@tmplt
Copy link
Contributor Author

tmplt commented Oct 18, 2016

@HalosGhost at present I'm keeping it private. I might add it when I figure out how to remove files after some time, depending on their file size.

@HalosGhost
Copy link
Owner

No worries! If you know of any other pb instances which are public (or you ever decide to open your instance for public use), please feel free to add them to the wiki!

@tmplt
Copy link
Contributor Author

tmplt commented Oct 18, 2016

I'll do that. Perhaps a column could be added for maximum allowed file size?

On 10/18/2016 02:34 PM, Sam Stuewe wrote:

No worries! If you know of any other pb instances which are public (or
you ever decide to open your instance for public use), please feel free
to add them to the wiki!


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#71 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1cyhFTp0iek2V5m3tVJN7Mi2gH-A37ks5q1LzagaJpZM4KCP2p.

@HalosGhost
Copy link
Owner

It's a wiki, feel free to add whatever information you feel is pertinent 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants