Let's put an App on AppSource, Part #2
HTML-код
- Опубликовано: 20 сен 2024
- Episode 1: • Let's put an App on Ap...
Episode 2: • Let's put an App on Ap...
Episode 3: • Let's put an App on Ap...
Episode 4: • Let's put an App on Ap...
Find more information at my blog www.hougaard.com or follow me on / ehougaard
Source code can be found here: github.com/hou...
Thanks a lot Erik. As always you are the best BC expert that I have come across. Really helpful video.
I will personally recommend this video of yours to anyone who might need assistance on Appsource for BC.
Great videos about putting an app on AppSource, maybe you could walk us through your build script in a future video
I have kinda avoided that whole topic "cd/ci" / "devops" on the channel, because, as you can see, I prefer a different way of doing this and that way seems less sexy than all the fancy pipelines other mvps are promoting.
The script you saw exists in many forms, this was the simplest, others have tests, I have built a tool that builds both onprem and appsource .app files from the same source, deploys to download servers, etc.. But in the end, it's just a .bat file :)
@@Hougaard I understand, but it was the simplicity I liked about it :)
Me too :)
Hi Erik, great video! I was wondering if you could suggest how to protect a PTE. I mean... lets suppose I do not want to sell a PTE to a customer, just hire it as an extra little charge every month (just as standard license). Now lets suppose after sometiem this customer decides not to work with me and change to another partner. Is there a way I could have my PTE blocked if lets say after sometime I do not provide a token to it... Thanx
.. but it's the same thing with appsource apps, there's no protection builtin, everybody (include myself) have built their own license system.
But, if your "PTE" is a product, then you need to support your product at someone who has another partner - Otherwise, how do you scale your business?
@@Hougaard you are right Erik, but the scenario is a PTE not being sold but hired to a customer. I was thinking in "Show my code = NO" and after some executions my PTE will ask for a token to keep working... of course it would be fancy if I could publish a web service that my PTE consume to get that token without user interaction... I agree that If I sold the PTE to the customer and he decides to work with someone else, the customer can keep my PTE (in fact is "his PTE")
@@antoniocheca3787 Hmm... If the customer paid for the time to develop the PTE, then it's theirs. You can't have it both ways, that's not ethical. If the customer pays you for the time spend on developing the PTE, then it's their IP, or at least they have a lifetime right to use it. You can't have the cake and eat it too!
@@Hougaard Of course, if the customer pays for the PTE he may keep it (I am not that sure about IP, though) but of course the customer has the right to use it for ever... My scenario is a customer that is not buying the PTE, just pay a small fee every month to use it (just as a BC standard license). From your words I understand I need to develop my own licensing system, am my initial question/suggestion is wondering how would you do this "protection"...