I would like to test this new web application when its in a working state. Send me a PM when the editor is in a working state and Ill provide feedback on this web application.
Will do!
Is there any documentation of how Sponge will do permissions? I don’t think there would be since it’s a bit early in development but, might as well ask.
Yeah I figured so I’m just gonna try and develop it to where it will be easy to add new permission file formats.
Which is one of the main reasons I’m recoding it.
For various plugins, you may need to make quite drastically different editor setups. For instance, I’ve heard talk about ‘transient’ permissions, which may not be bound to an individual group, world, etc, so for those plugins, you may need areas that can list group-transient or world-transient permissions as well as the common setups so far with permission groups, permissions for groups (not permission groups, but rather permissions applied to a group), per-world per-group permissions, and per-world per-user permissions. I wouldn’t be looking forward to doing something with that many alternatives XD But regardless, good luck! Hopefully it doesn’t do what MCMA does and just kinda botches the permissions files if you have it set up before using MCMA. Seeing proper support for various plugin features would be really nice.
Also, instead of having to add a single permission node at a time in various sections, a bulk input would be nice.
@OffLuffy Aren’t the Lapis permissions just for simplifiying the configuration process, not being a drastically different idea of permissions? As far as I know, if you only want to have the features of e.g. PermissionsEx, you don’t need to use them and have a simple, clean and working permission setup… If I’m wrong, please correct me - I may did not fully understand the potential of those Buckets…
By the way: I’m now working with @jdf2 on this together and some things of the idea have changed drastically:
There will be a community feature: You can just import the most-used configuration from a huge database created by everyone hosting a server.
It will (probably only) work together with a Sponge plugin which acts as a secure REST API for the biggest permission plugins.
It will be centralized on one website with one database and user accounts for every server admin, so everyone can and will share his setup with the community database.
The interface will probably look completely different from what it does in the first version of jdf2’s PEXOE.
I know this may does not sound perfect for an open source-minded community to have a centralized platform to manage permissions, however this offers huge possibilities for features of all kinds instead of being just another PEx GUI.
I can’t say with any certainty as I’ve only really used Group manager in the past, but it does seem like Lapis has some pretty extensive permissions API, although I’m thinking they’re not implemented by Lapis themselves, only allows plugins to do so, so I guess it’s up in the air what happens with that setup.
As one of the largest supported permission handlers, I suspect the developers or some other developer would be interested in porting it. If not out of interest, then maybe out of necessity.
Although maybe the wrong place to be asking about that as this is thread is for a web-based permission editor, not necessarily Sponge support for permission handlers.
With this you will get no parse issues, a correct syntax and it does not break the server as you don’t need a reload. You can also argue there’s no need for things like McMyAdmin or SpaceCP and you should just use your vServer’s CLI, but it’s just more convenient to have something that looks good.
With this, you can setup the server permissions for a server with many plugins in under 10 minutes and you will never forget to set the permissions for new plugins - your server will always be safe from griefers