Copyright (c) 2.007 Copiar Pegar Digital S.L., David Vaquero Santiago <pepesan_mail@yahoo.es>
.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
Historial de revisiones | ||
---|---|---|
Revisi�n 1.0 | 11-04-2007 | David Vaquero Santiago |
Tabla de contenidos
Lista de figuras
Tabla de contenidos
Bienvenidos a esta documentaci�n sobre La Teor�a de funcionamiento de la plataforma LAMP. Espero que os sea grata y que os ayude a entender mejor el desarrollo de aplicaciones mediante los ordenadores con GNU/Linux.
A fin de poder entender correctamente el comportamiento de la arquitectura LAMP es importante describir el funcionamiento de la arquitectura de aplicaciones Cliente-Servidor. En Dicha arquitectura disponemos de dos tipos de agentes:
Cliente: Ordenador o programa inform�tico que solicita informaci�n.
Servidor: Ordenador o programa inform�tico que dispone de informaci�n.
Dentro de este tipo de arquitectura podemos definir distintos tipos de Agentes dependiendo del tratamiento que se realice con la informaci�n
Activo: El Agente realiza un procesado activo de la informaci�n. Calculo intensivo, c�lculo de la presentaci�n gr�fica de la informaci�n, acceso a datos son algunas de las tareas t�picas de un Agente Activo.
Pasivo: El agente se limita a manejar informaci�n en bruto o preprocesada.
A continuaci�n se detallan los distintos tipos de Arquitecturas de Cliente - Servidor:
Cliente Activo, Servidor Pasivo: El cliente realiza la practica totalidad del trabajo de procesado de la informaci�n. Ejemplo: Google Earth.
Cliente Pasivo, Servidor Pasivo: Tanto el cliente como el Servidor simplemente pasan informaci�n. Ejemplo: Gateways de comunicaciones VoIP.
Cliente Pasivo, Servidor Activo: El Servidor realiza todo el trabajo de procesado y el cliente simplemente presenta los datos. Ejemplo: Servidores de terminales.
Cliente Activo, Servidor Activo: Tanto el Servidor como el Cliente procesan la informaci�n. Ejemplo: Servicios de Correo Electr�nico.
Tabla de contenidos
Dependiendo de la aplicaci�n LAMP que el tipo de arquitectura puede variar, pero por simplicidad en el presente manual s�lo va a tratarse del Tipo Cliente Activo - Servidor Activo.
A continuaci�n se detallan un glosario de t�rminos que permiten entender mejor la arquitectura LAMP:
HTML: Hyper Text Markup Language. Lenguaje que permite definir el contenido y su presentaci�n para que el cliente web permita visualizar la informaci�n que contiene. Dicho lenguaje permite la inclusi�n de medios (gr�ficos, sonidos, v�deos, etc.).
Etiqueta o TAG: Unidad m�nima de representaci�n en el Lenguaje HTML. Permite definir: p�rrafos, tablas, enlaces, im�genes, etc...
CSS: (Cascading Style Sheets) Hojas de Estilo en Cascada . Permiten generar clases de estilo que se pueden aplicar a etiquetas HTML. Dichas hojas de estilo se pueden definir dentro de los ficheros HTML o incluso referenciarlos. Los TAG permiten agrupar cambios en las propiedades de un determinando TAG.
Java Script (JS): Lenguaje de programaci�n que permite en la parte cliente procesar y realizar cambios en la presentaci�n. Dichos Scripts suelen estar referenciados desde el fichero HTML.
P�gina Web: Unidad de contenido de un servidor web. Normalmente est� compuesta de un fichero formateado en HTML y sus referencias.
Sitio Web: Conjunto de reglas del Servidor Web y las p�ginas Web que lo componen.
Servicio DNS: Servidor que entre otras funciones permite traducir nombres de m�quinas en Internet a direcciones IP.
Navegador Web: Cliente que permite consultar a Servidores Web y presentar la informaci�n HTML. Ejemplos: Firefox, Konqueror, Opera, Internet Explorer, etc.
Plugin Web: Extensi�n de un navegador web que permite a�adir una funcionalidad a un navegador web, por ejemplo la visualizaci�n de elementos no est�ndar. Ejemplos: Flash Player, JVM, etc.
Apache: Servidor Web Libre. Dicho servidor es altamente flexible y actualmente el 60% de los sitios web funcionan con Apache.
M�dulo de Apache: Conjunto de funcionalidades agrupadas que permiten extender el tratamiento de la informaci�n por parte del servidor Web Apache.
URL: Uniform Resource Locator. Definici�n del acceso a un recurso. El concepto de URL ha sido incorporado dentro del m�s general de URI (Uniform Resource Identifier - Identificador Uniforme de Recurso), pero el t�rmino URL a�n se utiliza ampliamente. La URL est� dividida en tres partes: Nombre del Servidor Web, Recurso a acceder y Par�metros GET.
M�todo GET: Forma de paso de par�metros mediante URL.
M�todo POST: Forma de paso de par�metros mediante formulario (normalmente).
PHP: PHP Hypertext Pre-processor. es un lenguaje de programaci�n usado generalmente para la creaci�n de contenido para sitios web. PHP est� preparado para funcionar como un m�dulo de Apache (y otros servidores Web).
Direcci�n IP: Identificativo �nico de un interfaz de red basado en el Protocolo IP.
SGBD: Sistema de Gesti�n de Bases de Datos. Son un tipo de software muy espec�fico, dedicado a servir de interfaz entre la base de datos, el usuario y las aplicaciones que la utilizan. Se compone de un lenguaje de definici�n de datos, de un lenguaje de manipulaci�n de datos y de un lenguaje de consulta. En los textos que tratan este tema, o temas relacionados, se mencionan los t�rminos SGBD y DBMS, siendo ambos equivalentes, y acr�nimos, respectivamente, de Sistema Gestor de Bases de Datos y DataBase Management System, su expresi�n inglesa.
SQL: Lenguaje de Consulta Estructurado (Structured Query Language). Es un lenguaje declarativo de acceso a bases de datos relacionales que permite especificar diversos tipos de operaciones sobre las mismas. Auna caracter�sticas del �lgebra y el c�lculo relacional permitiendo lanzar consultas con el fin de recuperar informaci�n de inter�s de una base de datos, de una forma sencilla.
A continuaci�n se detallar�n los elementos de una arquitectura LAMP:
Cliente Web/DNS: Navegador Web. Por ejemplo: Firefox.
Servidor DNS: Conversor de nombres a IP's. Por ejemplo: BIND.
Servidor Web: Almac�n y procesador de la Informaci�n Web. Apache en nuestro caso.
M�dulo de PHP: M�dulo para apache que permite procesar ficheros escritos en el Lenguaje PHP. Por ejemplo: PHP5
Aplicaci�n LAMP: Conjunto de ficheros PHP que componen una Aplicaci�n Web.Por ejemplo: PhpMyAdmin
SGBD: Sistema de gesti�n de bases de datos que permitir� almacenar la informaci�n din�micamente. En nuestro caso Mysql.
A continuaci�n se detallar�n los pasos que realizan el cliente y el servidor de una arquitectura LAMP
Cliente Web: Solicitud de conversi�n del nombre de una m�quina al Servidor DNS. Por ejemplo: www.google.es
Servidor DNS: Recepci�n y tratamiento de la solicitud. Una vez recibida la petici�n realiza las consultas necesarias para resolver y obtener la direcci�n IP.
Servidor DNS: Devuelve la direcci�n IP que corresponde al Servidor Web al navegador Web.
Cliente Web: Realiza la solicitud de informaci�n mediante una URL(M�todo GET) o un formulario (M�todo POST). Dicha solicitud incluye: la direcci�n IP del servidor web, el puerto del servidor web, URL y par�metros POST(esta s�lo en el caso de formularios normalmente).
Servidor Web: Control de Acceso, An�lisis de la petici�n y localizaci�n del recurso.
Servidor Web: Selecci�n del m�dulo de PHP para interpretar el fichero PHP elegido.
M�dulo de PHP: Ejecuci�n del programa PHP elegido.
Aplicaci�n PHP: Procesado de los par�metros GET o POST.
Aplicaci�n PHP: Realizaci�n de las llamadas SQL al Servidor de SGBD.
SGBD: Recogida y procesado de la petici�n SQL.
SGBD: Retorno de los datos solicitados.
Aplicaci�n PHP: Procesado de los datos devueltos por el SGBD y Generaci�n del HTML resultante.
Modulo PHP: Paso del HTML resultante a Apache.
Apache: Devuelve el HTML al cliente Web.
Cliente Web: Presentaci�n del HTML resultante, CSS y elementos relacionados y ejecuci�n del Javascript.
A continuaci�n se puede visualizar un gr�fico que resume dichos pasos:
Tabla de contenidos
Debido a que la instalaci�n y configuraci�n espec�ficas dependen del sistema operativo y la versi�n escojida, se van a enumerar los pasos necesarios para su configuraci�n, que son los siguientes:
Alta de un dominio. Ejemplo: midominio.com
Alta de las m�quinas que pertenecen al dominio. Ejemplo: servidor.midominio.com. en este paso se relaciona la direcci�n IP de la m�quina con el nombre dentro del dominio.
Alta de los Alias necesarios: www, ftp, correo, etc. Se relacionan los nombre reales de las m�quinas con un alias o apodo de la m�quina.
Esperar de 24 a 48h a que se replique la informaci�n entre los Servidores DNS de todo el mundo.
Realizar una consulta de DNS para ver si ha funcionado correctamente la operaci�n para cada una de las m�quinas y alias creados.
Debido a que la instalaci�n y configuraci�n espec�ficas dependen del sistema operativo y la versi�n escojida, se van a enumerar los pasos necesarios para su configuraci�n, que son los siguientes:
Configuraci�n de los par�metros b�sicos: Directorio principal de directorio, reglas de acceso por defecto, numero de hijos, memoria ram, n�mero m�ximo de peticiones, etc...
Alta y Configuraci�n de los m�dulos b�sicos necesarios: redirecci�n, proxy, configuraci�n, etc...
Prueba de funcionamiento del servidor web con un fichero HTML de ejemplo.
Instalaci�n y Configuraci�n del m�dulo de PHP: inclusi�n del m�dulo, asociaci�n del tipo de fichero al m�dulo, configuraci�n de tama�o m�ximo de upload, memoria por hilo php, acceso a datos, etc...
Alta de un sitio web virtual que permita manejar el sitio principal del dominio. Ejemplo: www.midominio.com relacionado con el directorio /var/www/midominio.com/
Configuraci�n de las reglas especiales para el sitio principal del dominio: control de acceso, etc.
Prueba de funcionamiento de PHP con un fichero de ejemplo.
Debido a que la instalaci�n y configuraci�n espec�ficas dependen del sistema operativo y la versi�n escojida, se van a enumerar los pasos necesarios para su configuraci�n, que son los siguientes:
Configuraci�n b�sica del servidor Mysql: memoria principal disponible, tipos de tabla disponibles, memoria destinada a cache, etc...
Inserci�n de usuarios b�sicos.
Creaci�n de una base de datos de ejemplo.
Creaci�n de una tabla de ejemplo.
Modificaci�n de un usuario para tener acceso a la base de datos creada.
Prueba de funcionamiento con un cliente de Mysql.
Debido a que la instalaci�n y configuraci�n espec�ficas dependen del sistema operativo y la versi�n escojida, se van a enumerar los pasos necesarios para su configuraci�n, que son los siguientes:
Creaci�n de una base de datos en el servidor para la aplicaci�n.
Colocaci�n de las tablas principales necesarias para el funcionamiento de la aplicaci�n LAMP.
Instalaci�n de la aplicaci�n web en el sitio web principal.
Configuraci�n de la aplicaci�n web.
Prueba de la aplicaci�n web.
Version 1.2, November 2002
Copyright � 2000,2001,2002 Free Software Foundation, Inc.
Version 1.2, November 2002
Tabla de contenidos
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
GNU FDL Modification Conditions
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:
Sample Invariant Sections list
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this:
Sample Invariant Sections list
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.