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

Multiple files upload #46

Open
heinbez opened this issue Jan 29, 2016 · 13 comments
Open

Multiple files upload #46

heinbez opened this issue Jan 29, 2016 · 13 comments

Comments

@heinbez
Copy link

heinbez commented Jan 29, 2016

Hi,

Thanks for building this project. A feature that I would really appreciate is being able up upload multiple files at once.

Thanks,
H.

@andre-d
Copy link
Contributor

andre-d commented Jan 31, 2016

Related: #4

@k3d3
Copy link
Contributor

k3d3 commented Jan 31, 2016

I don't think this is the same as #4 - I think he just wants to upload multiple files at once, not necessarily put those files into an album.

Still, adding multiple file upload and then putting a checkbox somewhere stating "create an album" would solve both of them.

@andre-d
Copy link
Contributor

andre-d commented Jan 31, 2016

Not the same, if it were the same I would have closed it, this is just a
flaw in the way github relates issues (you need to make a comment). Just
related, the "here are the files you have uploaded" view is the same as the
album view minus actually uploading the index and both depend on uploading
multiple at once.

On Sun, Jan 31, 2016 at 10:54 AM, Keith M [email protected] wrote:

I don't think this is the same as #4
#4 - I think he just wants to
upload multiple files at once, not necessarily put those files into an
album.

Still, adding multiple file upload and then putting a checkbox somewhere
stating "create an album" would solve both of them.


Reply to this email directly or view it on GitHub
#46 (comment).

@k3d3
Copy link
Contributor

k3d3 commented Jan 31, 2016

Fair enough, I've modified your comment. Feel free to change it back if you prefer

@perpi
Copy link

perpi commented Feb 1, 2016

@k3d3, you mean sth like imgur.com? doesn't it need user profiles?!

@andre-d
Copy link
Contributor

andre-d commented Feb 1, 2016

No, albums will not require accounts. Basically the server will be
modified to allow you to overwrite if you have the deletion key which will
allow you to overwrite an album index as you add to it linking to other
files in one index.

There will also be albums via + in the URL.
On Feb 1, 2016 3:51 AM, "perpi" [email protected] wrote:

@k3d3 https://github.com/k3d3, you mean sth like imgur.com? doesn't it
need user profiles?!


Reply to this email directly or view it on GitHub
#46 (comment).

@k3d3
Copy link
Contributor

k3d3 commented Feb 1, 2016

@perpi Nope, you wouldn't need user profiles. For an album, basically you would just upload multiple files normally, and then create a new "upload" that just contains an table of contents for the just-uploaded files.

@heinbez
Copy link
Author

heinbez commented Feb 1, 2016

Is up1 a no database solution? Could you potentially just use folders to create a collection of items?

@andre-d
Copy link
Contributor

andre-d commented Feb 1, 2016

There is no database except the filesystem
On Feb 1, 2016 2:28 PM, "Heinrich Bezuidenhout" [email protected]
wrote:

Is up1 a no database solution? Could you potentially just use folders to
create a collection of items?


Reply to this email directly or view it on GitHub
#46 (comment).

@k3d3
Copy link
Contributor

k3d3 commented Feb 1, 2016

@heinbez yep, there's no database involved - just the file storage on the filesystem. That way it can easily be scaled out via FS-scaling solutions like glusterfs.

We'd prefer having a single flat directory, as it makes it easier to just use a plain static web server like nginx to serve the files. Having a directory would require weird things like directory listings in collections directories and not anywhere else. We want the server to be as dumb as possible.

For multiple file uploads, we plan on giving the option to either 1) giving multiple individual links, or 2) creating an album file that refers to the aforementioned multiple individual links. This also has a nice side-effect of being able to refer to existing images and files in new albums.

@heinbez
Copy link
Author

heinbez commented Feb 1, 2016

Cool! Looking forward to the update :)

On Tue, Feb 2, 2016 at 8:43 AM, Keith M [email protected] wrote:

@heinbez https://github.com/heinbez yep, there's no database involved -
just the file storage on the filesystem. That way it can easily be scaled
out via FS-scaling solutions like glusterfs.

We'd prefer having a single flat directory, as it makes it easier to just
use a plain static web server like nginx to serve the files. Having a
directory would require weird things like directory listings in collections
directories and not anywhere else. We want the server to be as dumb as
possible.

For multiple file uploads, we plan on giving the option to either 1)
giving multiple individual links, or 2) creating an album file that refers
to the aforementioned multiple individual links. This also has a nice
side-effect of being able to refer to existing images and files in new
albums.


Reply to this email directly or view it on GitHub
#46 (comment).

@elimisteve
Copy link

For multiple file uploads, we plan on giving the option to either 1) giving multiple individual links, or 2) creating an album file that refers to the aforementioned multiple individual links. This also has a nice side-effect of being able to refer to existing images and files in new albums.

@andre-d @k3d3 I came here hoping to find something like this! Are there plans to add this feature? And either way, is there a design laid out somewhere. I really want this feature and may be able to add it.

@wolfgangasdf
Copy link

I modified up1 (too much for a fork, mainly for personal use) including multi-file upload (browser ZIP, not focussed on pictures), probably this is useful for someone: https://github.com/wolfgangasdf/up1234me

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

No branches or pull requests

6 participants