The Website: Subdomains and Modularisation

[AF]

Abma raised this point in the main thread

imo the website stuff should be modularized:

create:
wiki.springrts.com
forum.springrts.com
bugs.springrts.com

extra db, extra git repo, extra layout. this would simplify stuff a lot. atm updating mediawiki / forum is difficult / a lot of work as many stuff possible could break. currently its hard to know what side-effect some change can have. mediawiki / phpbb has to many custom changes of the "core" code, which means, when updating the usual way these changes would be overwritten by the new version of the software.

I identify that we would likely need these new repositories:

• spring/spring-phpbb
• spring/spring-mediawiki

There is the question as to wether the homepage/media/news page should also be a separate repository or not. This would turn the primary spring-website repository into a server/deployment meta package of sorts containing htaccess and including the others.

There's also the question of how should these repositories be bundled? i see the following options:

• Git submodules
• Composer
• Git subtrees
• Bash scripts

If subdomains are used this wouldn't be an issue but it would mean that we need to implement redirects, and we'd need to identify what those are.

What are peoples thoughts?

[Forboding Angel]

Yes, they should definitely be modularized as abma has suggested. Honestly, this should be a no-brainer.

[abma]

only "problem" we will have is that wiki login requires phpbb db, but didn't investigate yet. should be easily to solve by giving the wiki db-user read-only access to the phpbb db.

[AF]

Do we anticipate any cookie authentication issues with moving to subdomains model? We'll also need appropriate test domains

I suggest these:

test.springrts.com
wiki.test.springrts.com
etc..

rather than:

test.wiki.springrts.com
etc..

It will aid in search replaces as only a single search replace will be necessary

[abma]

i would prefer

test-wiki.springrts.com
test-forum...