Do you ever had a chance to work on a quite complex project, where you have multiple Magnolia Instances?
Just to make an example, a “standard” multi-environment setup consists in at least 3 places:
But you can find even different environments setup. Just to make few example of REAL environments I faced:
Project 1: “don’t try at home”
Project 2: “no more envs?”
- LOCAL: Local laptops
- DEV: Development, a kind of “playground-for-developers”
- SIT: System Integration Test
- STAGE: Staging
- UAT: User Acceptance Test
- PROD: Production
- DR: Disaster Recover, a kind of “soft copy” of PROD
If your response is “Yes, I did..” you know this feeling: to see a Magnolia Login screen without knowing where you are logging to.
In this situation, you can even disable superuser acces, since you type “superuser / superuser” multiple time, saying: “but on DEV superuser has password “superuser”. But you are on a different env.
Ok, this can be quickly be solved. With a very simple module (jar) drop.
I’ve created a very simple module, able to isolate this functionality. Hope you (dear community..) like it! Download it, branch it, fork it.. and let me know if you find it useful or maybe.. if you find bugs
More info directly on GitHub:
Magnolia Module Logininfo