Question: Extending the core features (aka Plugin system) about cloudboost

[nawazdhandala]

What would you like to implement? Nawaz Dhandala E: [email protected]<mailto:[email protected]> P: [phone] From: Paolo Furini <[email protected]> Reply-To: CloudBoost/cloudboost <[email protected]> Date: Thursday, 8 March 2018 at 8:33 AM To: CloudBoost/cloudboost <[email protected]> Cc: Subscribed <[email protected]> Subject: [CloudBoost/cloudboost] Question: Extending the core features (aka Plugin system) (#302) Hi is there some standard way in place to be able to extend core features, without hacking the core code directly? Put in another way: is there a plugin system? Thanks P. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<#302>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ACkoehicNZYk3WWPBJutlkwAYDSmmvggks5tcSUzgaJpZM4SinN9>.

[pfurini]

@nawazdhandala well, a lot of things potentially.. I mean, I'm looking for a no-lock-in alternative of Firebase, but I'm not a newbie dev.
I need the freedom to add custom API endpoints (aka controllers) without the burden of a separate server, integrate and swap out different storage providers (like for example storing files both locally and on S3 or whatever), and the list can go on..

[nawazdhandala]

That's in our roadmap, but it will take months before it see's the light of the day.

[pfurini]

I see.. and it was clear navigating through the code, but I wanted to hear an official response ;)

Surely it will need a major refactoring, but just to have a sneak peak, have you already considered which extension points you're going to support in the first iteration?

Thx, P.