all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Yellow
|
|
|||
|
|||
|
|
|
Notes:
|
|
Duplicating Servers – Round One: - Start from the beginning o Create corp o Create user o Build assignments between corps based on permissions - Changes to logins - Timeline for new changes - Communication to other users - Going from current model – to – round one (please see sketches on scan in photo gallery) Round Two: 1. Universe 2. Galaxies 3. Clusters 4. Solar Systems 5. Worlds (are within solar systems) Duplicating Servers – Round One (Continued): - Application.cfm has a number of key pieces. (There are 3 application.cfm files – root, shop, top secret). Currently that file works as a config file of sorts. For right now, that file could be server specific until we could come up with a more dynamic way of controlling code. o Controlling variables: • Allow New Corps = “yes” or “no” • If yes, use key word next or a physical number, • If next, figure it out • If number, check for it first, then add it - How do we report back to the master? - When creating a new corporation, I’d like to look at a master list. - Between corporations and clusters it feels like the old debate between which comes first – the chicken or the egg? You kind of need both. Let’s say that we have created a chicken and now we want to get one or more eggs. - On some of the webservices… Depending on the cluster configurations. They, the webservices, may need to go out and then back in or update using local connections. |