Two reasons. First is that you will eventually run out of Bubble space. I’m starting to hit that. Also video uploading and retrieval can be pretty slow to Bubble.
Also Bubble storage is very expensive comparatively ( $10 for additional 10GB) & managing files/deletion can be difficult since you can’t do this in a bulk operation.
I’ve been experimenting with your plugin for about 5 hours today. I think you are really onto something!. If you are looking for a phase two to really knock another plugin out of the park, check out Bunny CDN. Many Bubblers don’t realize that Storage solutions like AWS and and Wasabi are not really meant to be streamed from at scale. The Bunny CDN is affordable and I didn’t see a single plugin on Bubble that tackles the issue.
This sounds like exactly what I’m looking for. But I do have Questions. I want to extend the bubble database.
Question: I have 2 applications and I want to connect them by data. So if I use one application to input data to the database, could I pull the data from the database on another application. Is this possible?
Question: I am creating a Stats website but input the data manually, with no sports API. So is this app possible to use as a backend?
Hey Josh thanks for trying our plugin and your nice feedback. We’re ready to start work on the new features today, thanks for the tip on Bunny, we’ll look into this.
Hey Sumit, you can store the whole list of uploaded files straight into a field on a datatype. The downside to this is the fields of these files won’t be visible inside the database, all you will see is a bunch of commas. In our demo we use Tookit’s forEach element to iterate over the list of uploaded files and save these into separate things in our database.
When you want to delete the user’s files for example, make a call to wasabi with delete file action, set the folder to wherever all the user’s files are stored.
Wasabi doesn’t charge you API fees, only retention/ storage.
Hi Jonesy, first question should be fine yes, you could use the same API keys or generate a second set.
Your second question, this plugin doesn’t work for backend. You could upload files via the Wasabi console and copy the urls into your Bubble editor. Just make sure they are public if needed.
So what I’m trying to do is connect my apps, I want to input data and have the data show up on another application instantly. There will be so much data over the long run, so would using Wasabi as the middle storage man work?
Hey, thanks for the plugin. I figured it came with the custom uploader built in, the one that’s shown on the app page, but now I’m actually trying to use that, it seems like I need to copy every element and workflow into my app to get them to work (been trying this for about 2 hrs and it’s mega complicated)? Is there a self contained way that I’m missing to just use the custom wasabi uploader as you have it (minus the checkboxes and filetype changer etc), so i can drop it into different pages and it’ll work simply? Thanks
Also I’m getting a ton of errors trying to use the elements… it says i dont have the plugin installed but I do… i’m very confused right now! Screen Shot 2021-01-02 at 21.19.13|604x420
Yes it will work, you can use the read files from bucket action for this, we added a new option for file name prefix so you could filter the results with. To show all uploaded files in App2 will be fine but if you want to show a specific file, let’s say an uploaded image to use on the page it will be difficult and you will need to find some creative ways of doing that. Not sure of your’e exact use case. Maybe this is not what you mean?
If you would like to use App1 to upload files like a admin type dashboard, then use the uploaded file url in App2 by pasting the url manually somewhere, let’s say it’s an image or video file then that won’t be a problem, unless you have some specific CORS restrictions. All files uploaded through the plugin will be public if you are on a paid plan of Wasabi, you can view these in any application.
Hi James thanks for trying the plugin.
There is a custom uploader built in but just without any UI, it’s up to you to style the previews or upload progress, however you want, using native Bubble. Agreed the demo is complex, it’s just to show off many features, events and processing states, you can design something simpler.
The checkboxes are for demo purposes to show different functions and validations. Unless you want your users to choose what file types, multiple files etc, then you won’t need to copy this.
Try not look at the demo, put the s3 element on your page, configure what settings you would like (this can all be static). Then add a repeating group with Type of content as ‘File (Wasabi)’ and Data source as ‘Wasabi S3 A’s Files’ here you can add some elements inside the repeating group cell of 'Current Cell’s File (Wasabi)‘s…xxx’ .
We are considering to add something like Dropzone in later releases though.
For the errors you’re copying over the testing version of the plugin, this won’t work. Only one app can test a plugin at a time. You can use the replace the feature to fix this, it should keep most of the logic you copied over. Some new features that we are currently working in test version are not public yet so may not work.
OK thanks. I’d already deleted it all by then anyway.
Any chance you can make a separate page in the demo app showing a simplified use case? So us less technical users can see it in action and understand what are the minimum steps required?
Right now I’ve got the files appearing in wasabi, BUT although the ‘accepts’ is set to .mp3, it will still let me upload any filetype.
Also not managing to get anything to show in the repeating group currently… just trying to show filenames as text… shouldnt these appear as soon as files are dropped on the uploader box?
Any ideas?
Thanks!
Sure, we can make another demo, give us few minutes.
Drag and drop validation doesn’t work with input accept values by nature, if you click/trigger the input it will accept correctly, we are already planning a fix for this issue. https://jsfiddle.net/ynj8dsu6/
Refer to the plugin’s state of Files and make this the datasource.
Do you have generate previews option checked?
ok yeah that was the problem, works now with previews turned on. I figured preview was only for generating an image. Thanks
Sorry about the confusion there, next update the field will be renamed to ‘Read Files’ and generate previews will be a new second option just for images.
No probs. Oh also any chance you could add “maximum number of files” as a feature? Also seems that max file size is for total upload, but could there be a yes/no that lets it apply to individual file limit instead? Thanks!
Limit total files count can be added, yes max file size is for total size, Bubble doesn’t let us write long field names there, should be described in the documentation under the call. We could add limit size per file but it’s a little more difficult to accomplish, this will be qued towards the end of the list for features.