rdpickard/uplily

A very simple web server for uploading files to.

uplily's Issues

Visually indicate upload to s3 is in process

Currently there is no visual feed back to the user that the upload to s3 is happening. As it is multi-part process this is an awkward silence.

Maybe an overlay on the upload window displaying the progress of the process?

Add "Stop" function for uploading to S3

Uploads to S3 can't be stopped from the UI

Validate this works on Windows

I haven't tried this on a Windows desktop. Need to try it and adjust as needed.

Added support for S3 pass-through uploading

Serverless cloud platforms like Heroku and Elastic Beanstalk are pretty limited to how long requests can take and how much data can persisted to "disk".

The S3 service provides a way to create a pre-signed URLs to allow uploading from a browser without having to go through the serverless app instance.

Need to look into that.

On Startup add self to S3 CORS configuration

When the application.py starts, use the boto API to check to see if the server is in the CORS configuration. If not add it.

https://boto3.amazonaws.com/v1/documentation/api/latest/guide/s3-example-configuring-buckets.html

This will save a step the operator needs to take and will reduce confusion.

Add AWS Elastic-Beanstalk configuration file

Basically add support for putting UpLily on AWS Elastic-Beanstalk instances.

Probably mostly a documentation issue.

Add drag-and-drop to web UI

Add UI element to drag files to for uploading.

Currently only "Browse" button can be used to select a file to upload.

This should come after the Issue to support local and S3 transfers simultaneously.

Support S3 and local transfers simultaneously

Add endpoints to upload/download to the local file system & S3 in the same instance.

Currently the transfer is for either a local or S3 destination. Both should be valid targets in the same instance, assuming S3 is configured.

Storage directory is hard coded as "/tmp/"

The "/tmp/" directory works fine in Heroku and on OS X but isn't very portable. Hard coding in the application.py file will likely lead to failures in other environments.

Need to change this.

Add UI element for reporting messages

The web UI should have a feedback message area.

Messages will convey information such as

• upload succeeded
• upload failed
• upload time out

Uploaded files dictionary isn’t request safe

The uploaded files dictionary as a global works ok when running locally but doesn’t work correctly in heroku cloud. I think this is because global variables aren’t safe between requests in a proper WSGI environment.

The manifestation of this is different results of “available files” and 404s when trying to download files that have been uploaded.

Need to add the dictionary to a persistent context or to something like a redis store.

Need to document limitiations of Heroku instances

Heroku constrains app instances in a way that caps the size of a file that could be transferred. Need to document that in the README file.

List files and download files from S3

If S3 is configured don't offer local fs storage

Currently if S3 is configuration the web UI offers an option for local or S3. This is kind of visually confusing.

If S3 is backend is configured local fs should not be a storage option.