search

GlowstoneMC / Shine

Glowstone's plugin database
MIT License
3 stars 1 forks source link

Merging the Shine project with the Glowstone site #7

Open aramperes opened 7 years ago

aramperes commented 7 years ago

Hello all,

we have been thinking about merging this project (Shine, the plugin database) with the new Glowstone site. The site's server software is made in Python, but already has an excellent base for development of new features. It has entered production mode earlier this week and now replaces our old Github pages site.

Instead of rewritting a website engine in a different language (currently Node.JS here), and having to re-do most of the designing of the front-end to match the current site, I think we should make Shine part of that server software.

The Glowstone site already has accounts (although no public profiles) and a template rendering engine, API engine and other features. Instead of re-inventing the wheel, maybe we should consider this an option.

Please reply if there are concerns about this option or other questions!

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/49303230-merging-the-shine-project-with-the-glowstone-site?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F45742928&utm_medium=issues&utm_source=github).
aramperes commented 7 years ago

After discussing this on Discord (#site channel), it's looking as though we should keep the Shine project as a separate software. However, we can merge the authentication prodecude by implementing SSO/OAuth2 for the Site, which would be used to login into Shine.

This does mean that more work will be needed to redesign the user system on the Site, but we can ditch the independant auth system currently made in Shine.