Oily Rag 1: Introduction: Difference between revisions
(New page: {{Uc nav oily rag 1}} '''UniServer 3.5-Oily Rag Introduction''' I am slightly saddened by the fact; Uniform Server 3.5 is the last in its series. The new model "four" series will eventual...) |
(Minor formatting, punctuation.) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 7: | Line 7: | ||
I use a car analogy because Uniform Server 3.3 is reminiscent of older cars where you can dive in, get your hands dirty, fine tune and bolt on a few goodies to make it uniquely yours. | I use a car analogy because Uniform Server 3.3 is reminiscent of older cars where you can dive in, get your hands dirty, fine tune and bolt on a few goodies to make it uniquely yours. | ||
Like a car you would not recast an engine block or camshaft | Like a car you would not recast an engine block or camshaft; these are fixed components. Similarly DLLs and exe files are pre-complied, hence are fixed components. In both scenarios you can tweak, move components around, add little extras, even move the air intake to act as a vacuum cleaner. This blows your engine apart as it sucks up a puddle of water. | ||
Leads me onto component reuse. Buried within 3.5’s architecture are some very elegant, standalone components just asking to be reused, perhaps in other projects. However I am thinking more in terms of tweaks saving extra work when coding. | |||
== That dream == | == That dream == | ||
Ever purchased a brand new car, sat there looking at the dashboard wishing you could remove or add a new switch | Ever purchased a brand new car, sat there looking at the dashboard wishing you could remove or add a new switch? | ||
Not a chance for fear of devaluing the car | Not a chance, for fear of devaluing the car. However take a look at 3.5's admin panel and wreak your revenge; it won’t be devalued when you break it. Just install a brand new one. | ||
== Opulence == | == Opulence == | ||
Well if you are feeling opulent you can have a model 3.5 for every day of the week. | Well if you are feeling opulent, you can have a model 3.5 for every day of the week. | ||
I purposefully neglected to state what the model refers to, thus giving me the opportunity to | I purposefully neglected to state what the model refers to, thus giving me the opportunity to emphasize that Uniform Server is much more than a web server. | ||
'''''[[#top | Top]]''''' | '''''[[#top | Top]]''''' | ||
== Just get on with it! == | == Just get on with it! == | ||
If I were reading this article, by now I would be screaming! Show me something new and shut up. OK at least it’s not full of those irritating adverts. | If I were reading this article (instead of writing it), by now I would be screaming! Show me something new and shut up. OK, at least it’s not full of those irritating adverts. | ||
{|cellpadding="0" cellspacing="0" | {|cellpadding="0" cellspacing="0" | ||
| Line 42: | Line 41: | ||
|[[Image:Uc_eye_candy.gif]] | |[[Image:Uc_eye_candy.gif]] | ||
|align="center"| | |align="center"| | ||
'''After a time | '''After a time it becomes so irritating''' | ||
|- | |- | ||
|[[Image:Uc_eye_candy.gif]] | |[[Image:Uc_eye_candy.gif]] | ||
| Line 48: | Line 47: | ||
'''Result Click through''' | '''Result Click through''' | ||
'''Bandwidth is valuable don't waste it''' | '''Bandwidth is valuable, don't waste it''' | ||
|[[Image:Uc_eye_candy.gif]] | |[[Image:Uc_eye_candy.gif]] | ||
|} | |} | ||
== Title == | == Title == | ||
For this series I could not think of a better title | For this series I could not think of a better title. '''Oily rag''' seemed appropriate. | ||
Anything you read in this | Anything you read in this series requires you to roll up your sleeves and get your hands dirty. | ||
However I take no responsibility for any hair loss, blood dripping down walls (please bang your head against something else) or laptops that are hurled out of windows (could move to a basement flat). | However I take no responsibility for any hair loss, blood dripping down walls (please bang your head against something else) or laptops that are hurled out of windows (could move to a basement flat). | ||
== Skills == | == Skills == | ||
Skills required | Skills required: knowledge of CSS, HTML, be a competent programmer preferably in C++, PERL, PHP, MySQL and machine code and that’s only to service a car. | ||
Actually, to complete any topic in this section, I found copy and paste more that adequate. | |||
For once in my life I will be very serious | For once in my life I will be very serious. No matter what fancy titles or terminology you see, it all boils down to one thing, '''manipulation of text files'''. If you know where to find these text files you can hack them to your heart's content and make them work for you. | ||
'''''[[#top | Top]]''''' | '''''[[#top | Top]]''''' | ||
== Oily Rag - Content == | == Oily Rag - Content == | ||
=== 3.5-Apollo problems and bugs === | === 3.5-Apollo problems and bugs === | ||
In keeping with the oily rag philosophy you will find detailed information on how to correct bugs in Uniform Server 3.5-Apollo. | In keeping with the oily rag philosophy you will find detailed information on how to correct bugs in Uniform Server 3.5-Apollo. | ||
The bug count has increased slightly I have consolidated these in a separate section [[Bugs 3.5-Apollo: Introduction |3.5-Apollo problems and bugs]] | The bug count has increased slightly. I have consolidated these in a separate section [[Bugs 3.5-Apollo: Introduction |3.5-Apollo problems and bugs]] | ||
=== Running 3.5-Apollo as a Service === | === Running 3.5-Apollo as a Service === | ||
I have retained this in the Oily Rag section because various pages require changing | I have retained this in the Oily Rag section because various pages require changing. However installing and running (see [[Oily Rag 1: Running 3.5-Apollo Service| Running 3.5-Apollo Service]]) remain easy. | ||
Check out [[Bugs 3.5-Apollo: Combined bug fix|Combined bug fix]]. It includes all pages that need changing. | |||
=== CD Part 1 === | |||
Introduces techniques required to convert Uniform Server to run from a CD. Highlights files which pose a problem. These contain functions that require read/write access. These are modified to produce a working example with no frills. Check out [[Oily Rag 1: CD Part 1|Part 1]] | |||
=== CD Part 2 === | |||
The example in Part 1 although functional is a one-way process. [[Oily Rag 1: CD Part 2|Part 2]] introduces the concept of file switching, which greatly enhances the plugin's functionality. Concludes with a down-loadable plugin USCD1. | |||
=== CD Part 3 === | |||
[[Oily Rag 1: CD Part 3|Part 3]] highlights problems with plugin '''USCD1'''. Proposes an alternative solution to file switching and introduces Perl commands (instructions) that will be used in a new plugin USCD2. | |||
=== CD Part 4 === | |||
[[Oily Rag 1: CD Part 4|Part 4]] consolidates all the ideas to produce something resembling a usable plugin. You can download [[Oily Rag 1: Downloads#CD Part 4|plugin USCD2]], which provides a reasonable starting point that you can tailor to your own application. | |||
=== CD Part 5 === | |||
[[Oily Rag 1: CD Part 5|Part 5]] Introduce components required to provide a complete CD solution. | |||
=== CD Part 6 === | |||
[[Oily Rag 1: CD Part 6|Part 6]] Looks at making the CD independent of an host PC's browser. It also shows how to host several sites on the same CD. | |||
== Dedicated drive == | |||
Running Uniform Server on a [[Oily Rag 1: Dedicated drive USB|dedicated drive]] is extremely easy. No need to run it as a service. Removes the need for a virtual drive. This gives it a slight speed advantage when run on a USB stick or separate partition on a hard drive or even a separate hard drive. | |||
== Wait for process to start. Includes a batch progress bar== | |||
This [[Oily Rag 1: Wait for process |proposes a solution]] to prevent the dreaded error message "connection was refused" when starting 3.5-Apollo. I have also included a batch file progress bar. | |||
== MySQL server upgrade to 5.0.51b == | |||
A [[Oily Rag 1: MySQL upgrade 5.0.41 to 5.0.51b | step-by-step guide]] how to upgrade Uniform Server 3.5-Apollo's MySQL server to 5.0.51b. | |||
'''''[[#top | Top]]''''' | '''''[[#top | Top]]''''' | ||
| Line 93: | Line 117: | ||
|} | |} | ||
[[Category: Oily Rag]] | [[Category: Oily Rag]] | ||
Latest revision as of 19:43, 14 July 2011
| Oily Rag: Be prepared to get your hands dirty. |
UniServer 3.5-Oily Rag Introduction
I am slightly saddened by the fact; Uniform Server 3.5 is the last in its series. The new model "four" series will eventually supersede it. However before that time comes with its boast of go-faster stripes, super plugins and 0-60 in the blink of an eye, I thought it worthwhile having an in-depth look at 3.5, sort of lift the bonnet and have a poke around.
Analogy
I use a car analogy because Uniform Server 3.3 is reminiscent of older cars where you can dive in, get your hands dirty, fine tune and bolt on a few goodies to make it uniquely yours.
Like a car you would not recast an engine block or camshaft; these are fixed components. Similarly DLLs and exe files are pre-complied, hence are fixed components. In both scenarios you can tweak, move components around, add little extras, even move the air intake to act as a vacuum cleaner. This blows your engine apart as it sucks up a puddle of water.
Leads me onto component reuse. Buried within 3.5’s architecture are some very elegant, standalone components just asking to be reused, perhaps in other projects. However I am thinking more in terms of tweaks saving extra work when coding.
That dream
Ever purchased a brand new car, sat there looking at the dashboard wishing you could remove or add a new switch?
Not a chance, for fear of devaluing the car. However take a look at 3.5's admin panel and wreak your revenge; it won’t be devalued when you break it. Just install a brand new one.
Opulence
Well if you are feeling opulent, you can have a model 3.5 for every day of the week.
I purposefully neglected to state what the model refers to, thus giving me the opportunity to emphasize that Uniform Server is much more than a web server.
Just get on with it!
If I were reading this article (instead of writing it), by now I would be screaming! Show me something new and shut up. OK, at least it’s not full of those irritating adverts.
|
|
So I lied! Could not resist it. |
|
|
|
At best they provide eye candy. |
|
After a time it becomes so irritating | |
|
|
Result Click through Bandwidth is valuable, don't waste it |
|
Title
For this series I could not think of a better title. Oily rag seemed appropriate.
Anything you read in this series requires you to roll up your sleeves and get your hands dirty.
However I take no responsibility for any hair loss, blood dripping down walls (please bang your head against something else) or laptops that are hurled out of windows (could move to a basement flat).
Skills
Skills required: knowledge of CSS, HTML, be a competent programmer preferably in C++, PERL, PHP, MySQL and machine code and that’s only to service a car.
Actually, to complete any topic in this section, I found copy and paste more that adequate.
For once in my life I will be very serious. No matter what fancy titles or terminology you see, it all boils down to one thing, manipulation of text files. If you know where to find these text files you can hack them to your heart's content and make them work for you.
Oily Rag - Content
3.5-Apollo problems and bugs
In keeping with the oily rag philosophy you will find detailed information on how to correct bugs in Uniform Server 3.5-Apollo.
The bug count has increased slightly. I have consolidated these in a separate section 3.5-Apollo problems and bugs
Running 3.5-Apollo as a Service
I have retained this in the Oily Rag section because various pages require changing. However installing and running (see Running 3.5-Apollo Service) remain easy.
Check out Combined bug fix. It includes all pages that need changing.
CD Part 1
Introduces techniques required to convert Uniform Server to run from a CD. Highlights files which pose a problem. These contain functions that require read/write access. These are modified to produce a working example with no frills. Check out Part 1
CD Part 2
The example in Part 1 although functional is a one-way process. Part 2 introduces the concept of file switching, which greatly enhances the plugin's functionality. Concludes with a down-loadable plugin USCD1.
CD Part 3
Part 3 highlights problems with plugin USCD1. Proposes an alternative solution to file switching and introduces Perl commands (instructions) that will be used in a new plugin USCD2.
CD Part 4
Part 4 consolidates all the ideas to produce something resembling a usable plugin. You can download plugin USCD2, which provides a reasonable starting point that you can tailor to your own application.
CD Part 5
Part 5 Introduce components required to provide a complete CD solution.
CD Part 6
Part 6 Looks at making the CD independent of an host PC's browser. It also shows how to host several sites on the same CD.
Dedicated drive
Running Uniform Server on a dedicated drive is extremely easy. No need to run it as a service. Removes the need for a virtual drive. This gives it a slight speed advantage when run on a USB stick or separate partition on a hard drive or even a separate hard drive.
Wait for process to start. Includes a batch progress bar
This proposes a solution to prevent the dreaded error message "connection was refused" when starting 3.5-Apollo. I have also included a batch file progress bar.
MySQL server upgrade to 5.0.51b
A step-by-step guide how to upgrade Uniform Server 3.5-Apollo's MySQL server to 5.0.51b.
 |
Ric |