Website Management

James at Monument Valley

In the early years, you had static pages and a webserver and anybody could code HTML. Fast forward to today and its far more complex. With Starlight's help, you can avoid costly problems that can arise with owning and running a website system.

Website Elements 

Its good to create a matrix on a spreadsheet or similar to map key elements that are related.

A website has a database, a webserver config file (or two or three), a directory where website files are kept, a server name, and probably some key settings file. With a map, you can quickly relate a website you are looking at in a browser to the other key elements. The map is really helpful when you have several websites. Here's an example:

Website Map
Site Key Value
1 Database Name Drupal_754
1 Server Config File www.drupal754.conf
1 Root Dir /var/www/html/drupal754
1 Hostname
1 Settings File Location <rootdir>/sites/default
1 Machine Location someplace secure
1 Manager Joe Smith


The above isn't so necessary if you have one or two websites. In this world, if you have 2 websites, then you probably have 2-4 development sites. So already its 6 records of map data. You can imagine when its more...pretty soon its a database instead of a spreadsheet, with records for backup, restore, operating system, ssl certificate info, etc.

Weird Error Messages/Resolution

Situations like these arise all the time. Some have to be researched and fixed on the spot and others can be fixed later as long as a bandaid fix is available. The below is an example of a bandaid fix. FAQ pages were probably spawned from this:

Error: Site wont let user upload a picture into a content page after a data backup 

Cause: unknown

Resolution: reboot webserver gracefully

We'll add more to this page over time.... thanks!