Codimd: Loosen Imgur dependency / plug-ins

[neopostmodern]

We're considering to use this project at our art school but we're reluctant to depend on external service providers / storying anything on anybody else's server.

I've seen that the upload code is server-side (app.js#L407) and wondered if it would be possible to make this either

• configurable
• or plug-in based (and still configured)

to enable other upload targets (such as local FS or - for other use cases - the usual S3 etc)

This would make it much easier for custom deploys to keep up with the upstream version. I haven't seen a generic plug-in system yet, is that on the roadmap or do you have a different approach?

Now that I think of it, plug-ins for oAuth would be sweet too.

[Yukaii]

@neopostmodern

We're working on filesystem/s3 Image uploading now. You can track this in PR #248 😸

related issue: #156

[neopostmodern]

That's great to hear! Couldn't find those issues before, sorry.

Any word about a general plugin-oriented architecture? Especially concerning oAuth?

[jackycute]

It's ok. @neopostmodern

We use passport.js to auth users, so it's already a module and plug-in.
Also we'll trying to make everything be module in the future, need a good arch though.

[jackycute]

Supported in bd3d4958e43a8437e45113354059cf41dacda995