Added support for AWS S3 and CloudFront for those others who use Amazon for image serving.
Without the CloudFront Domain Name, images will be served directly from S3, otherwise your CloudFront domain will be used. All the particulars must be setup via the AWS console. If anyone is interested I can write a short howto on getting it done. Otherwise setup for AWS S3 support should be pretty straight forward.
Thus far we have support for Cloudinary, ImageKit, and AWS S3.
I was surprised that the gallery plugins seemed to be lacking... or maybe I'm missing something?!
Anyway I'd love to get feedback about nodebb-plugin-lightgallery.
Thanks.
@crazycells said in Imageshack Upload Plugin:
ImageShack - API
Are you still interested in a plugin for Imageshack? I just wrote a cloud storage plugin
and could either add support for Imageshack to that or develop an independent plugin. Shoot me a PM/email if you're still interested. Thanks.
@satishbh Fix pushed.
NPM - 1.0.15 • Public • Published 6 minutes ago
And since I don't want to spam the forum and I have no idea if there's a more appropriate place to announce these things... finished my second NodeBB plugin (nodebb-plugin-cloudstorage) today, well at least a mvp. Works with Cloudinary and ImageKit. Again, would love all feedback. Thanks.
I'll put up a gif in the readme shortly.
I just spent some time figuring out IF I had written a post earlier today or not... as I was unable to find any record of a post anywhere under my profile. However as I just posted a second time I saw the same "being queued..." message and so I'm pretty certain now that I did in fact post earlier today.
However it would be nice to have some sort of user record (email sent, notification in your profile somewhere) when posts are awaiting approval. This is probably only applicable to new users, but still it would be nice.
Thoughts...
https://github.com/june07/nodebb-plugin-lightgallery
Also available in the NodeBB plugin menu under find.
Wow! So turns out it was a silly error on my part. I had tried the Error object previously, but it was while looking at a different part of the code... I was actually looking/changing the 'imagekit' case in the code and being stumped as to why I was still seeing the behavior as I explained. Anyhow, it is working as it should when passing in an Error object. Thanks for the extra insight!
No. It is a dependency and will be installed automatically by nodebb-plugin-cloudstorage.
@maciejso Anyone with a solution to this?! Wth!?
I recently wrote a blog post which goes hand in hand with developing NodeBB plugins as of late
In the post, I talk about my workflow and wonder what other workflows people are using for there NodeBB development. NodeBB definitely presented it's own challenges, different from other Node.js projects I've worked on.
Would 
to hear about what others are doing.
@satishbh Also to add more context to this for others who come across it (using the older version):
https://github.com/june07/nodebb-plugin-cloudstorage/issues/2#issuecomment-526089881
The root cause of the error was having an S3 bucket that wasn't public. The plugin then handled the thrown error by the S3 API incorrectly, which was fixed in:
I found the reason that my bucket wasn't public.
@julian Thanks for the positive words. I'm glad it has been useful.
@satishbh Fix pushed.
NPM - 1.0.15 • Public • Published 6 minutes ago
@FreeWorLD Sure. Email me and let me know more about your requirements. Including what site do you plan to use the plugin for, typical traffic, etc.
Added support for AWS S3 and CloudFront for those others who use Amazon for image serving.
Without the CloudFront Domain Name, images will be served directly from S3, otherwise your CloudFront domain will be used. All the particulars must be setup via the AWS console. If anyone is interested I can write a short howto on getting it done. Otherwise setup for AWS S3 support should be pretty straight forward.
Thus far we have support for Cloudinary, ImageKit, and AWS S3.
Wow! So turns out it was a silly error on my part. I had tried the Error object previously, but it was while looking at a different part of the code... I was actually looking/changing the 'imagekit' case in the code and being stumped as to why I was still seeing the behavior as I explained. Anyhow, it is working as it should when passing in an Error object. Thanks for the extra insight!
