Hi,
I am having a hard time getting a handle on the most up to date information on deploying hosted plugins. My users are confused and I am really confused.
I’m looking at this page https://docs.coronalabs.com/native/hostedPlugin.html and am confounded by a number of things.
First, in the Packaging and Hosting section, it says that my .tgz needs to be a flat file (no directories), but pretty much every one of my plugins are built using a directory structure for organization. How exactly am I supposed to handle that without rewriting all references? Why is it different than how it used to work?
Example (S3Lite plugin):
- s3-lite.lua
- s3-lite (directory)
- awsauth.lua
- awsrequest.lua
- mimes.lua
…etc
Secondly, in the Running Plugins in the Simulator section, there only seems to show a path for MacOS based systems. Where do these go for Windows?
Additionally, if my plugins are plain Lua, can I just point to the same url for “iphone” and “android” platforms?
Regarding the “macos” and “win32” being set to false, I have also seen urls there instead (on Scotts plugin metadata entries). How does that aspect work?
And lastly, are downloaded plugins cached? And if so how are they checked for updates? I would prefer not to have a pull every time a build is made.
I’m trying hard to support my plugin users, and I handle the support directly. But I don’t have any good solid information to tell them. Obviously the first issue is that I need to get my plugins hosted, but as I read through the documentation, I’m getting the feeling that I would have to heavily refactor all my plugins, which I have neither the time nor resources for.
Please tell me that this process is simpler than it appears. I want to continue supporting Solar2d, but if I have to rewrite all my plugins, it will be a full stop, and I will have to explain to my users that Solar2d is unable to support my plugins, even though the initial impression was that it would be a very basic transition.
Thanks in advance,
dev