Edit History Actions Discussion

Diff for "Info/Design"

Differences between revisions 5 and 6
Revision 5 as of 2008-02-17 20:01:05
Size: 1142
Editor: localhost
Comment: converted to 1.6 markup
Revision 6 as of 2009-07-07 20:39:34
Size: 1136
Editor: marco
Comment: spelling+rephrasing
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
This is how the Blinkenshell shell account envinorment works. Behind the domain Blinkenshell.org there is a physical server, the name of this server is Saturn. This is how the Blinkenshell shell account environment works. Behind the domain Blinkenshell.org there is a physical server: the name of this server is Saturn.
Line 4: Line 4:
Saturn has several virtual servers, of witch one is the one where all the shell accounts live, Titan is the name of that virtual server. Saturn has several virtual servers, one of which is where all the shell accounts live; Titan is the name of that virtual server.
Line 6: Line 6:
When you surf to Blinkenshell.org firstly Saturn checks what content you are requesting, and then either serves that content directly or sends a request to a virtual server. If you browse the main webpage, you are being served directly by Saturn. If you however request a users webpage, then it's the webserver on Titan thats serving your request. When you surf to Blinkenshell.org firstly Saturn checks what content you are requesting, and then either serves that content directly or sends a request to a virtual server. If you browse the main webpage, you are being served directly by Saturn. If you however request a user's webpage, then it's the webserver on Titan that's serving your request.

Design/Architecture

This is how the Blinkenshell shell account environment works. Behind the domain Blinkenshell.org there is a physical server: the name of this server is Saturn.

Saturn has several virtual servers, one of which is where all the shell accounts live; Titan is the name of that virtual server.

When you surf to Blinkenshell.org firstly Saturn checks what content you are requesting, and then either serves that content directly or sends a request to a virtual server. If you browse the main webpage, you are being served directly by Saturn. If you however request a user's webpage, then it's the webserver on Titan that's serving your request.

This explains some of the behaviours of the environment. And the reason I chose this design/architecture is mostly because of the added security. If someone gets root access on Titan, he will not be able to bring down the whole server.

  • [ATTACH]

Between 18-19 December 2006, there were some server problems and what I did then was to replace the previous virtual server Rhea with the new one called Titan.


CategoryInfo