Paid jhipster marketplace

[Kosha-account]

Propose to create for jhipster blueprints a marketplace similar to other framework's marketpaces where some could publish for sell his own developed blueprint.

[Tcharl]

Hi @Kosha-account ,

The marketplace is already here: https://www.jhipster.tech/modules/marketplace/.
I think that with a little bit of tweak of the project readme the 'paid' stuff could be easily achieved. May you please try to include a blueprint/module in this marketplace and identify the hickups that you can face with this model and opencollective?

Would be definitely appreciated to be able enhance the experience, or even contributon.

Please tell us if it could be a go or a nogo on your side

[Kosha-account]

Hi @Tcharl ,
I'm pretty newbie here and although I'm pretty experienced with spring boot/hibernate but not yet very familiar with the JH codebase. Currently trying to learn blueprint development principals but it also not goes very fast as no much teaching docs I found, thus I'm affraid at the moment I can't be helpful until will understand how all staff is working, saddenly. Would be highly appreciate if you could point me to more stuff regarding the blueprint development except the pubished on the main website

[Kosha-account]

Hi @Tcharl , I'm become a bit more familiar with jhipster and found that jhipster website is made not by jhipster itself but static TS/HTML, so I don't see how the blueprints can be usefull here, moreover they are dedicated to extend the framework functionality but not create some final product, thus I'm affraid I'm not quite sure I understood your idea clearly at all

[Tcharl]

Hi @Kosha-account ,

At least adding a badge on every tile of this static website stating the opencollective, patreon or any other subvention mecanism could be a nice addition would it?
Modifying the overall to also support private npm registry could also be another step in this way.

Do you think it would be kinda possible? TBH I do not know how this website works :-S, just have an idea of the overall mecanism

[Tcharl]

We are speaking about th same thing sir :-).
Jhipster modules/blueprints are in the end npm package right? Thus, if you want to sell something you don't want it to be available on a public repo (npmjs). Adding support for private registry in the marketplace (i.e. github private registry) + a mean to expose the price and paiement method (i.e. opencollective/patreon) would answer to the problem no?

[Kosha-account]

Hi @Tcharl , what do you mean of "support of private registry", does it mean the flag "--blueprint" should support url+credentials parameters, smth similar to "-:blueprints my-blueprint:repourl:github.com...:creds:..." ?
I think it's yes, it can be part of the official jhipster repo and be in use, but originally I imagined to get the purchased archive with files and put it in place of my choice and use it from there. The payment API blueprint could also be developed as part of the idea, but it means that jhipster should support the activity workflows except just CRUD of ERD.
Or if you mean to develop a blueprint which will create the whole internet shop, then, I think, it is too much effort for one specific solution, I would use some existing open source solution for the web marketplace or indeed developed it using jhipster with following manual customization, but yet think it's too much effort for one person unless it would be made as separate internal project. Moreover such a marketplace will require constant human attention because it will be responsible to check the published blueprints similar to validations in Apple store and Android marketplaces, this implementation looks as much wider approach than just a blueprint.

[Tcharl]

IMHO, supporting private registry for this marketplace first will come with a huge added value: supporting company catalog.
One public repo may be needed for the description of the blueprint (through readme) but the npm package (blueprint) could be on a private url: that doesn't seems to be an assles to implement on static website page.

Then, the addition of payment to grant the access to these private registries will lead to what you expect.
As an addition, the jhipster community won't need to host any additional service and few pieces of bits will need to be modified compared to the existing landscape which is a big plus!

[Kosha-account]

Usually companies which become responsible for storing client's staff are not giving this important part to other parties, but it's really not my business since this marketplace will be totally under jhipster maintainers control and responsibility

[Kosha-account]

IMHO, supporting private registry for this marketplace first will come with a huge added value: supporting company catalog. One public repo may be needed for the description of the blueprint (through readme) but the npm package (blueprint) could be on a private url: that doesn't seems to be an assles to implement on static website page.

Then, the addition of payment to grant the access to these private registries will lead to what you expect. As an addition, the jhipster community won't need to host any additional service and few pieces of bits will need to be modified compared to the existing landscape which is a big plus!

But realy funny how you concentrated on most less important feature of the project)))