I need your advice

[LMD]

So I am developing a SQLite DB application for MT, client-side, called MTPC - Minetest Package Control, and need the opportunity that my program(and any user) can update and sync an online stored DB, BUT WHERE SHOULD I HOST IT ?
GitHub + Java Git Library - Pros : not that hard, Cons : 25 MB Limitation
any other ideas ?

[hajo]

SQLite DB application for MT .. Minetest Package Control ..WHERE SHOULD I HOST IT ?

What exactly do you want to store in that db,
and how much data would that be, per user/account ?

[LMD]

Nope I dont store any userdata, I store mod/subgame/TP data. You can estimate the mod amount.

[hajo]

I dont store any userdata, I store mod/subgame/TP data.

What kind of data ?
How & for whom is that useful ?

[LMD]

U know some Package Managers ? Where do u search ur software ? This is a PC for MT.

[sofar]

I wouldn't use Sqlite on the server side. Maybe as a backend to some web interface, but definitely do not expose this file directly to clients.

The server should expose a JSON file instead. There are methods to easily parse JSON in minetest so you can just load the JSON directly using the http api into lua in minetest and use it.

On the client side you can use Sqlite of course just fine, and store it somewhere in ~/.minetest or similar.

[LMD]

sofar :
There isn't a "server".
There's only many clients and ONE package list which is always synced with the clients package list :
If the user decides to edit/delete package information, the online stored db is updated too.
In my opinion, it has to made client-side, and not as web interface, to easily allow the user the following features :
- installed mods/subgames/texture packs ?
- update mods/subgames/texture packs ?
- install/remove mods/subgames/texture packs ?
Only a standalone application can be mighty enough.

[sofar]

sofar :
There isn't a "server".
There's only many clients and ONE package list which is always synced with the clients package list :
If the user decides to edit/delete package information, the online stored db is updated too.
In my opinion, it has to made client-side, and not as web interface, to easily allow the user the following features :
- installed mods/subgames/texture packs ?
- update mods/subgames/texture packs ?
- install/remove mods/subgames/texture packs ?
Only a standalone application can be mighty enough.

So sqlite on the client to maintain lists is fine, as I already said, and probably the best way to do this.

But what format is "ONE package list which is always synced with the clients package list"? That's the one that should be JSON. How is it created? Who creates the first version? How do clients get it? Why can clients update the online stored DB? THis seems like open to abuse?

I guess I don't understand your architecture, or you are not describing it in enough detail.

[rubenwardy]

See viewtopic.php?f=14&t=19766

[LMD]

Any further advice :
viewtopic.php?f=3&t=19842&p=314685#p314685