Local Plugin Repo

[Nether Mc]

And is there an API for the online repo?

[NiLSPACE]

No, I don't think so. You might want to create an issue for that on the repo

[xoft]

Even easier, Cuberite plugins can use HTTPS to directly check with the GitHub API and download each file separately (no need to extract ZIPs) and even query the last commit date and such metadata from each repo.

[NiLSPACE]

I usually add a SourceLocation to my Info.lua files. With that your plugin could get a link to the plugin's repo.

[sphinxc0re]

I thought of that a while ago. It would be like having a package manager: cpm - cuberite package manager

Code:

cpm install worldedit

What about creating some kind of dependency management using LuaRocks?

[xoft]

I think it should be a plugin, not a standalone app.

[Schwertspize]

What I meant. If users are using zip files, we can't use it, but if the program does a git clone (or submodule) we could just use it. So we could use the program (or webadmin part) to manage ALL plugins.

[NiLSPACE]

You would have to force the user to install git for that. Personally I hate dependencies like that. It's much easier for the user if the plugins goes through all plugins and checks at the source location if there is a newer version.

[sphinxc0re]

no, you don't need to, because of libgit2. there might be a port for Lua out there

[NiLSPACE]

That's kinda OS dependent. People might need to compile it themselves before they can use it in the plugin.