|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SessionCommon Configuration for the LAMP Stack
Corey Williams, Director of Product Management, SpikeSource
MySQL is commonly deployed on servers along with other components, such as PHP and Apache. While it is possible to configure each component separately, there are several advantages to managing system configuration as a unit. This talk covers a method for using one common XML-based file to set all configuration items for a server, instead of having to edit each component's configuration in a different syntax. By storing configuration in one place, users can set a parameter for one component, such as a datasource definition. including the port number, and automatically update the corresponding dependent parameters for other components. In order to make performance tuning easier, users can save a configuration for the entire stack in a snapshot, then revert it or clone it to other hosts.
|
Diamond SponsorPlatinum SponsorsGold SponsorsMedia SponsorsIn-Kind SponsorsSponsor OpportunitiesFor information on exhibition and sponsorship opportunities at the conference, contact us at Download the MySQL Users Conference Sponsor/Exhibitor Prospectus Conference NewsTo stay abreast of conference news and to receive email notification when registration opens, please sign up here. Press and MediaFor media-related inquiries, contact Suzanne Axtell at |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||