Local Plugin Repo

[xoft]

That would have problems if we wanted the integration plugin to have some form of a presentation for installing new plugins. It'd have to fetch each plugin's description from its repository, which could quickly become unfeasible with tens of plugins, let alone more.

Now, I'm not talking about the entire Info.lua file from the plugin, just a simple description, a sentence or two, so that the admin knows quickly if it's anywhere near the plugin they want or not.

[xoft]

Json parser and serializer added. Now it's easier to write API communicators.

I'm hoping I'll have time over christmas to write a higher level networking support up to something like Python's UrlLib.

[Nether Mc]

Sorry, but that sound unreasonably difficult and too dependent on a single person.

Really? I did it already!

---

And Something like urllib(2) would be really nice!

---

I think it would be better if the description file is inside the plugin's own repository and not in a shared repo, and the shared repo only contains a list of other repos, which would be even less centralised. You might not even need a central repo, just pasting GH URLs into your plugin manager could work.

Repo nID (Used to Add a repo) all_url:http://example.com/path/to/list.txt@name:Sample Repo Name@owner:myselfminer

Index File: name:Spleef@url:http://example.com/path/to/zipfile.zip@version:0.0.1@Author:myselfminer@Description:Test Plugin Nid made by myselfminer!
name:Bedwars@url:http://example.com/path/to/bedwars.zip@version:0.4.1@Author:Herobrine@Description:An Amazing Bedwars Plugin!
name:Lobby Plugin@url:http://example.com/path/to/Loppy.zip@version:7.3.4@Author:Steve@Description: -

Plugin nID: name:Bedwars@url:http://example.com/path/to/bedwars.zip@version:0.4.1@Author:Herobrine@Description:An Amazing Bedwars Plugin!


So one Repo could have some plugins stored at github and some others on private (or public like dropbox, etc) servers