Dolibarr ERP CRM Wiki - User contributions [en]

Cloud con Redhat OpenShift Flex

2014-08-20T20:27:15Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Obtenemos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.
Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud with Redhat OpenShift Flex

2014-08-20T20:25:18Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.

For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. To extend or create your own modules. 
2 -. To put in production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We obtain the hostname and port of MySQL to connect to Dolibarr database. Top image 33.
Fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T21:07:13Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud with Redhat OpenShift Flex

2014-05-14T21:06:37Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.

For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. To extend or create your own modules. 
2 -. To put in production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-14T21:06:08Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.

For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. To extend or create your own modules. 
2 -. To put in production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T21:05:00Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T21:04:35Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T21:00:59Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 33.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T20:53:15Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos en nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-14T20:47:01Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un Cartridge de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud with Redhat OpenShift Flex

2014-05-08T19:19:45Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.

For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. To extend or create your own modules. 
2 -. To put in production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-08T19:19:15Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.

For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. To extend or create your own modules. 
2 -. To put in production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud con Redhat OpenShift Flex

2014-05-08T14:43:55Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para Dolibarr, desde la puesta en marcha, hasta la puesta en producción.

1.- Extender o crear nuestros propios módulos. 
2.- Poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-08T14:37:58Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Gears
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-08T14:37:20Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños Cartridges
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-07T20:14:02Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de [http://en.wikipedia.org/wiki/Secure_Shell SSH].

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor [http://en.wikipedia.org/wiki/InnoDB InnoDB], imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL], en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como [http://sourceforge.net/projects/winscp WinSCP] y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare [http://sourceforge.net/projects/heidisql HeidiSQL], que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud with Redhat OpenShift Flex

2014-05-07T20:08:07Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 18.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud con Redhat OpenShift Flex

2014-05-07T20:07:44Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 18.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-07T20:05:10Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 41.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Y con esto terminamos este tutorial.

Cloud con Redhat OpenShift Flex

2014-05-07T20:01:52Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

Y con esto terminamos este tutorial.

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 41.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Cloud con Redhat OpenShift Flex

2014-05-07T20:01:22Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

Y con esto terminamos este tutorial.

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 41.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app 
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar a ctl_app pero podemos controlar todo el Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Citados aquí www.openshift.com/developers/remote-access donde encontraremos más comandos útiles.

Cloud con Redhat OpenShift Flex

2014-05-07T20:00:03Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

Y con esto terminamos este tutorial.

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 41.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

Nota.- También en la parte remota de WinSCP, podemos navegar hacia carpetas como /var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr donde esta físicamente nuestra base de datos o podemos ir a /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs para ver los logs de MySQL.

Si escribimos help, en la ventana de PuTTY, nos mostrará algunos comandos importantes.

Entre los comandos más comunes están:

ctl_app
Controle su aplicación (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

Cloud con Redhat OpenShift Flex

2014-05-07T19:57:43Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

Esta página es un tutorial para explicar cómo instalar Dolibarr ERP-CRM en la plataforma Redhat OpenShift Flex www.openshift.com

''haga clic dos veces sobre la imagen que desea agrandar''

Image 1 
[[File:Url_openshift.JPG‎]]

= Un poco sobre OpenShift =

'''OpenShift plataforma como servicio'''

OpenShift es Plataforma como Servicio (PaaS) de Red Hat, que permite a los desarrolladores crear rápidamente aplicaciones escalables host, en un entorno de nube. Con OpenShift tienes elección de ofertas, en línea, en la premisa, y las opciones de proyectos de código abierto.

OpenShift brinda ayuda para construir y desplegar aplicaciones web, backends móviles, arquitecturas orientadas a servicios, y recibe sus servicios favoritos.

Openshfit trabaja con Gears y Cartridges, que son términos, con los que tendremos que familiarizarnos.

'''Que es un Gear?''' 
Un gear es un contenedor de recursos limitados que ejecuta una o más pilas de software especificados por el usuario, también conocidas como cartridges. Cada gear tiene una cantidad limitada de memoria RAM y espacio en disco.
Si una aplicación necesita más recursos, puede ser configurado para utilizar automáticamente más gears.

'''¿Cómo trabajan los Gears?''' 
Echemos un vistazo a una aplicación de ejemplo basada en Drupal que se ejecuta en OpenShift. Podemos estimar las necesidades y los costos de la aplicación en las diferentes etapas.

*15 páginas / segundo
*Cientos de artículos
*~ 50k visitantes por mes
*3 pequeños engranajes
*Plan Libre

Como vemos, un plan libre, puede ser suficiente, para una Empresa pequeña o mediana.
Para empresas más grandes, se puede cambiar al plan siguiente.

En OpenShift, tenemos dos posibilidades claras, para poner en marcha Dolibarr.

1.- Como desarrolladores, nos da la posibilidad de extender o crear nuestros propios módulos. 
2.- Como empresarios, nos da la posibilidad de poner en producción nuestro DoliBarr.

'''Ventajas que nos ofrece OpenShift'''

Es un sitio seguro, al cual se accede a través de SSH.

Es escalable 
Aplicación escalable, permite a la aplicación reaccionar a los cambios en el tráfico y automáticamente asignar los recursos necesarios para manejar su demanda actual. La infraestructura OpenShift monitorea el tráfico de Internet entrante y automáticamente trae copias de su cartucho de Web en línea para manejar las peticiones.

Nos da control total, sobre nuestra base de datos, para conectarnos remotamente a través de un cliente GUI como HeidySQL.

En caso de decantarnos por MySql, tenemos a disposición, el motor InnoDB, imprescindible para transacciones.

Nos da la posibilidad, de compartir Certificados SSL de RedHat o personalizar nuestro propio SSL, en caso de tenerlo. Imprescindible, para enviar nuestros datos, tanto de logín o de transferencias bancarias, encriptadas y seguras.

Dicho todo esto, comencemos, la puesta en marcha de nuestra aplicación DoliBarr.

= Create an account =
Click en SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Rellenamos nuestros datos, para crear una cuenta.
Click en Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

Nos enviaran, un email, a nuestra cuenta de correo, para confirmar.

= Cree una instancia =

== Parte 1 - Creando una instancia ==

Click en LOG IN nuevamente y nos mostrara el aspecto inicial de nuestra Consola de Aplicaciones.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click en Create your first application now

Elija un cartucho de programación web

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Busque el tipo de aplicación

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure la aplicación.

Es importante, definir bien el nombre de dominio, para este tutorial, hemos usado sdme. El dominio, no se puede cambiar más a menos que, borremos todas nuestras aplicaciones y empecemos nuevamente de cero y eso es algo que nadie quiere.

También, tendremos que informar, si tenemos un repositorio externo Git, con nuestro código.

Aquí viene lo divertido.

En scaling cambiaremos a Scale with web traffic.

La creación de esta aplicación, usara un Gear de los 3 que disponemos, lo indica justamente, al lado del botón Create Application.

Click en Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

Cuando la aplicación es escalable, no se puede añadir más Cartridges, al Gear. Por ejemplo sí queremos usar MySql, deberá ir aparte, en otro Gear.

En la imagen, de arriba, vemos que a nuestro Gear, se ha añadido el balanceador de carga, que hará nuestra aplicación escalable.

Arriba en el extremo derecho, existe también un botón, por si necesitamos reiniciar el Gear.

Nota.- Con PuTTY, podríamos solventar necesidades más explicitas, para controlar nuestros Gears, con línea de comandos.

Click en el enlace Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy en Acción.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

Si vemos nuestra url startdolibarr-sdme.rhcloud.com este es el aspecto inicial, que tiene.

== Parte 2 - Configuración de Herramientas de administración ==

Hasta aquí todo bien. Ahora, pasemos a la segunda parte, de nuestro tutorial.

Para esta parte, que será la referida a la administración de nuestra aplicación, existen dos caminos, el primero es por CLI (línea de comandos basado en Ruby) y el segundo, de forma más declarativa, por consola y con SSH.

Para este tutorial, he elegido la forma más fácil he intuitiva, que es la segunda opción.

Manos a la obra.

Necesitamos un cliente SSH/FTP como WinSCP y PuTTY.

Los Bajamos y los instalamos.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Dentro la carpeta donde se instaló WinSCP, encontraremos la carpeta PuTTY y dentro de esta carpeta, el programa puttygen.exe, este programa es importante, ya que, es el que nos ayudara a generar nuestro acceso SSH, para conectarnos a nuestro Gear.

Doble Click en puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

Dejamos los valores por defecto, SSH-2 RSA y el número de bits en 2048.

Con estos valores ya tendremos una key, fuertemente encriptada.

Click en Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

Para que genere de nuestra key, debemos mover el puntero del ratón, constantemente en el espacio en blanco del programa.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Una vez que ha finalizado la generación de nuestra key, tendremos que poner una passphrase.

Click en Save public key, para guardar nuestra key publica, le damos el nombre de rsa.pub, hacemos lo mismo con Save private key, y le damos el nombre de rsa.ppk.

Una key pública, es como la cerradura de una puerta y la key privada es como la llave que abre esa cerradura.

Marcamos el código generado en el área de texto y lo copiamos, luego nos vamos a nuestra consola de OpenShift.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Pegamos el código en Paste the contents of your public key file (.pub) y click en Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfecto ahora OpenShift, tiene nuestra cerradura, y nosotros la llave.

Ahora vamos al tab Applications en nuestra consola de OpenShift

Click sobre nuestra aplicación startdolibarr.

Click en Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copiamos el código ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

Abrimos nuestro WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

Ponemos la primera parte, 53641a41e0b8cdf5ec000b76 antes de la @ en el campo User name, y la segunda parte, startdolibarr-sdme.rhcloud.com después de la @ en el campo Host name.

Es aconsejable no colocar el password/passphrasse, en este punto, por motivos de seguridad. La usaremos más adelante.

Click en Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

En Private key file: seleccionamos nuestra clave privada rsa.ppk, click en OK, click en guardar y click en Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

Cuando nos salga esta agradable ventanita click en Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Aquí colocamos nuestra passphrase y click en OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola tenemos acceso vía SSH a nuestro Gear.

En la parte izquierda esta nuestro espacio local y a la derecha el remoto.

= Enviar archivos de Dolibarr =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

Bajamos la versión genérica de Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

En la parte remota seleccionamos la ruta
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transferimos la carpeta dolibarr, de nuestra máquina local a Openshift, presionando F5. Este proceso, puede tardar varios minutos, así que mientras esperamos, nos dedicaremos a crear nuestro Gear, para la base de datos.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

Volvemos a la consola de OpenShift y con nuestra aplicación seleccionada, hacemos click en la parte inferior, del apartado Databases y seleccionamos Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click en add Cartridge.

Nota.- En una aplicación normal sin Scale activado, el Cartridge Mysql se añadiría al Gear actual, pero en nuestro caso, openShift nos informa que se ocupará un nuevo Gear para MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copiamos los credenciales de acceso a MySQL. Los usaremos más adelante, para acceder a nuestra base de datos.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Una vez que ha terminado el upload de dolibarr, descrito en la imagen 23. Editamos el file index.php.

Lo abrimos nuestro editor de texto favorito y reemplazamos con el siguiente código.

<?php 
header("Location: dolibarr/htdocs"); 
?>

Hacemos una copia del index.php en la carpeta dolibarr y volvemos a editarlo y quitamos dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

Lo que acabamos de hacer, sirve, para que no se muestre la estructura de nuestros folders y files de dolibarr en el navegador web, con el index.php obligamos a que se redirija al inicio de DoliBarr.

Por último y antes de empezar con la configuración de dolibarr, conviene usar SSL (protocolo criptográfico), que nos proporciona seguridad a la hora de enviar nuestros datos desde el Navegador web al servidor. El uso de SSL es para dar un plus extra a las medidas de seguridad propias de dolibarr, que ya son buenas.

Abrimos nuestro editor de textos una vez más y añadimos lo siguiente.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Guardar con el hombre de .htaccess justo al lado de nuestro folder dolibarr y del index.php

Como se muestra en la siguiente imagen.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

Vemos como el certificado SSL es aceptado por el navegador.

= Ejecutar el asistente de instalación Dolibarr =

Comenzamos con la configuración de DoliBarr.

Seleccionamos del desplegable, Default language to use (language code): , el idioma correspondiente y click en Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click en start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

Revisamos la imagen 26, cuando creamos el Cartridge MySQL.

Y nos enfocamos en las líneas.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

Para crear la conexión con la base de datos, OpenShift nos proporciona unas variables de entorno. Para que dolibarr pueda conectarse a la base de datos, necesitamos saber el valor, de estas variables, así que volvamos a WinSCP y en la carpeta .env/mysql encontraremos dichas variables, como se muestra en la imagen de arriba.

Click con el botón derecho sobre OPENSHIFT_MYSQL_DB_HOST, click en edit y nos mostrara el valor que tiene la variable, copiamos y pegamos en el campo Server como se muestra en la imagen de abajo. Hacemos lo mismo para la variable OPENSHIFT_MYSQL_DB_PORT y pegamos su valor en el campo Port.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Nota.- Para cuando sigan estos pasos, el host y el puerto, para su instalación particular, debería ser diferente, al mostrado en este ejemplo.

Nota2.- En este pasó, también podríamos crear una Base de datos diferente y un propietario diferente, ya que poseemos las credenciales de súper usuario de MySQL, pero este paso no lo tocaremos aquí hoy.

Click en Next Step y nos muestra la siguiente ventana.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

Esta pantalla, básicamente nos informa que, la conexión a la base de datos se ha establecido y que se ha guardado esta información, en el file de configuración de dolibarr conf.php.

Click en Next Step y comenzará la creación de las tablas en la base de datos, necesarias para el trabajo de DoliBarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

Esta pantalla informa que, ha terminado la creación de las tablas.

Click en Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

Llenamos los campos con el username y password, del que será el administrador, para este ejemplo he usado admin/admin. Para el caso real debería ser un password más fuerte.

Click en Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click en Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Introducimos el username y password del administrador, definido anteriormente y Viola. Estamos dentro de DoliBarr.

= Apéndice: MySQL conexión remota =

Como paso final, veremos la conexión, desde un cliente local de Base de datos, hasta nuestro MySQL remoto.

Para este ejemplo usare HeidiSQL, que sirve tanto para base de datos MySQL o PostgreSQL y es Gratuito.

Abrimos HeidiSQL.

Lo primero que debemos hacer es seleccionar MySQL (SSH tunnel) del desplegable Network type, al hacer esto, HeidiSQL añade un nuevo tab llamado SSH tunnel, como se muestra en la imagen de abajo.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Tenga en cuenta que, en el campo plink.exe location: de deberá especificar la ruta de PuTTY.exe, en el campo Password introducidos la passphrase y el campo Local Port debe estar siempre en 3307.

Volvemos al tab Settings.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

Llenamos los campos, con las credenciales de la base de datos, seleccionamos la base de datos y click en guardar y en Open para probar la conexión.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

Y con esto terminamos este tutorial.

== Adición ==

=== Conexión al Gear MySQL ===

Recordaréis cuando obtuvimos el hostname y el port, de MySQL, para conectar DoliBarr a la Base de datos. Arriba en la imagen 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

La primera parte del Host name: es también el User name: 5364c670e0b8cd09f500036d-sdme.rhcloud.com damos click en Advanced y verificamos, que todo este como en la imagen 41.

Click en Save y click en Login.

Con WinSCP abierto, vamos al menú Options --> preferences --> Integration --> Applications como se muestra en la imagen de abajo.

Image45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

En el campo PuTTY/terminal client path: seleccionamos la ruta, donde tenemos el putty.exe y marcamos los tres CheckBoxes. Cada vez que iniciemos sesión con WinSCP también se iniciará sesión en PuTTY. Como vemos en la imagen de abajo.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Tener PuTTY abierto y conectado a la misma sesión, nos permitirá ejecutar sentencias de línea de comandos, para parar o arrancar el Gear o el servidor MySQL.

File:Preferences winscp run putty.JPG

2014-05-07T19:54:25Z

Gpaint: uploaded a new version of "File:Preferences winscp run putty.JPG"

File:WinSCP connect MySQL Gear.JPG

2014-05-07T19:51:57Z

Gpaint: uploaded a new version of "File:WinSCP connect MySQL Gear.JPG"

Cloud with Redhat OpenShift Flex

2014-05-07T07:52:54Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-07T07:52:26Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control the whole Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-06T22:25:17Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control all Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-06T22:23:36Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control all Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

And with that we end this tutorial.

Cloud with Redhat OpenShift Flex

2014-05-06T22:22:49Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control all Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cited here www.openshift.com/developers/remote-access where we find most useful commands.

Cloud with Redhat OpenShift Flex

2014-05-06T22:21:54Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

If we write help in the PuTTY window, will show some important commands.

Among the common commands are:

ctl_app 
Control your application (MySQL)

*ctl_app start
*ctl_app stop
*ctl_app restart
*ctl_app status

ctl_all 
Similar to ctl_app but we can control all Gear.

*ctl_all start
*ctl_all stop
*ctl_all restart
*ctl_all status

Cloud with Redhat OpenShift Flex

2014-05-06T22:19:37Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

Having PuTTY open and connected to the same session, allow us to execute command line statements to stop or start the MySQL server or Gear.

Note -. Also in the remote part of WinSCP, we can navigate to folders as
/var/lib/openshift/5364c670e0b8cd09f500036d/mysql/data/startdolibarr where this physically our database or we can go to /var/lib/openshift/5364c670e0b8cd09f500036d/app-root/logs to see MySQL logs.

Cloud with Redhat OpenShift Flex

2014-05-06T22:18:04Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Image 46 
[[File:Initialize_session_winscp_with_putty.JPG|500px]]

File:Initialize session winscp with putty.JPG

2014-05-06T22:17:48Z

Gpaint:

Cloud with Redhat OpenShift Flex

2014-05-06T22:16:31Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu --> preferences --> Integration --> Applications as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

In the PuTTY/terminal client path: field select the path where we have the putty.exe and mark the three checkboxes.

Each time you start in with WinSCP session also will start session in PuTTY. As seen in the image below.

Cloud with Redhat OpenShift Flex

2014-05-06T22:15:26Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.

Click in Save and click in Login.

With open WinSCP, go to the Options menu -> preferences -> Integration -> Applilcations as shown in the image below.

Image 45 
[[File:Preferences_winscp_run_putty.JPG|500px]]

File:Preferences winscp run putty.JPG

2014-05-06T22:14:54Z

Gpaint:

Cloud with Redhat OpenShift Flex

2014-05-06T22:11:11Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL Gear ===

You remember when we obtained the hostname and port of MySQL to connect to Dolibarr database. Top image 34.

Image 44 
[[File:WinSCP_connect_MySQL_Gear.JPG|500px]]

The first part of the Hostname: is also the Username:
5364c670e0b8cd09f500036d-sdme.rhcloud.com click in Advanced and verify that everything be as the image 41.
Click in Save and click in Login.

File:WinSCP connect MySQL Gear.JPG

2014-05-06T22:10:14Z

Gpaint:

Cloud with Redhat OpenShift Flex

2014-05-06T18:47:55Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use [http://sourceforge.net/projects/heidisql HeidiSQL], which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:43:11Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like [http://sourceforge.net/projects/winscp WinSCP] and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:39:14Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share [http://en.wikipedia.org/wiki/Transport_Layer_Security SSL] Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:37:39Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the [http://en.wikipedia.org/wiki/InnoDB InnoDB] engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:36:40Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through [http://en.wikipedia.org/wiki/Secure_Shell SSH].

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:26:58Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service ([http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:24:22Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:19:13Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.

If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial well, we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:15:02Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.
If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates of RedHat or customize our own SSL, if you have one. Essential to send our data of login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial well, we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:10:47Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.
If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

Gives us total control on our database for us to connect remotely to via a GUI client.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates RedHat or customize our own SSL, if you have one. Essential to send our data both login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial well, we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===

Cloud with Redhat OpenShift Flex

2014-05-06T18:01:36Z

Gpaint:

[[Category:Admin]]
[[Category:Cloud]]
{{TemplateDocUser}}

This page is a tutorial to explain how to install Dolibarr ERP-CRM on the Redhat OpenShift Flex Platform www.openshift.com

''click twice on image to enlarge''

Image 1 
[[File:Url_openshift.JPG‎]]

= A little about OpenShift =

'''OpenShift Platform as a Service'''

OpenShift is Red Hat's Platform-as-a-Service (PaaS) that allows developers to quickly develop, host, and scale applications in a cloud environment. With OpenShift you have choice of offerings, including online, on premise, and open source project options.

OpenShift provides help to build and deploy web applications, mobile backends, service-oriented architectures, and get your favorite services.

Openshfit works with Gears and Cartridges, which are terms with which we have to familiarize ourselves.

'''What's a Gear?''' 
A gear is a resource-constrained container that runs one or more user-specified software stacks, also known as cartridges. Each gear has a limited amount of RAM and disk space.
If an application needs more resources, it can be configured to automatically use more gears.

'''How Do Gears Work?''' 
Let's look at an example Drupal-based app running on OpenShift. We can estimate the needs and costs of the app at different stages.

*15 pages/second
*Hundreds of articles
*~ 50k visitors per month
*3 Small Gears
*Free plan

As we see, a free plan, it may be sufficient for a small or medium company.
For larger companies, you can switch to the next plan.

In OpenShift, we have two possibilities, to launch Dolibarr.

1 -. As developers, it gives us the ability to extend or create your own modules. 
2 -. As entrepreneurs, it gives us the opportunity to put into production our Dolibarr.

'''Advantages offered OpenShift'''

It is a secure site, which is accessed through SSH.

It is scalable 
Application scaling enables your application to react to changes in traffic and automatically allocate the necessary resources to handle your current demand. The OpenShift infrastructure monitors incoming web traffic and automatically brings copies of your web cartridge online to handle requests.

It gives total control on our database to connect remotely via a GUI client HeidySQL.

If we opt for MySql, we feature the InnoDB engine, essential for transactions.

It gives us the possibility to share SSL Certificates RedHat or customize our own SSL, if you have one. Essential to send our data both login or bank transfers, encrypted and secure.

= Create an account =
Click in SIGN UP

Image 2 
[[File:Sing_up.JPG|500px]]

Fill your data to create an account.
Click in Sign Up

Image 3 
[[File:Verify_your_account_with_OpenShift_Online.JPG|500px]]

They will send an email to your email account to confirm. Click in Verify your Account.

= Create an instance/domain =

== Part 1 - Create instance ==

Click LOG IN back and show us the initial aspect of our console applications.

Image 4 
[[File:Control_panel_openshift_account.JPG|500px]]

Click in Create your first application now

Choose a web programming cartridge

Image 5 
[[File:PHP_apart.JPG|300px]]

1. Choose a type of application

Image 6 
[[File:Configure_de_application.JPG|500px]]

2. Configure the application.

It is important to define the domain name, for this tutorial well, we used sdme. The domain, you cannot change it unless, we delete all our applications and start again from scratch and that is something that nobody wants.

Also, we will have to report, if we have an external git repository with our code.

Here comes the fun part.

In scaling change to Scale with webtraffic.

The creation of this application, used a Gear of the 3 that we have, indicates precisely next to the Create Application button.

Click in Create Application.

Image 7 
[[File:Console_startdolibarr_Application.JPG|500px]]

When the application is scalable, you cannot add more Cartridges, the Gear. For example we do want to use MySQL, you must go apart, another Gear.

In the image above, we see that our Gear, has added the load balancer, which will make our scalable application.

Up on the right end, there is also a button, in case we need to restart the Gear.

Note. - With PuTTY, we could resolve more explicit requirements to control our Gears with command line.

Click on the link Web load Balancer.

Image 8 
[[File:HAProxy.JPG|500px]]

HAProxy in Action.

Image 9 
[[File:Aspect_your_webpage.JPG|500px]]

If we see our url startdolibarr-sdme.rhcloud.com this is the initial appearance, it has.

== Part 2 - Setup admin tools ==

So far so good. Now to the second part of our tutorial.

For this part, will be referred to the administration of our application, there are two ways, the first is by CLI (command line based Ruby) and the second, more declarative form, console and SSH.

I chose the easiest way I've intuitive, which is the second option for this tutorial.

Hands to work.

We need a SSH / FTP client like WinSCP and PuTTY.

We download and install.

Image 10 
[[File:Folder_WinSCP_-_PUTTY.JPG|500px]]

Inside the folder where you installed WinSCP, find the folder PuTTY and inside this folder, the puttygen.exe program, this program is important because it is the one that will help us generate our SSH access, to connect to our Gear.

Double Click in puttygen.

image 11 
[[File:Puttygen_initial.JPG|400px]]

We leave the default values, SSH-2 RSA, and the number of bits in 2048.

With these values and will have a key, heavily encrypted.

Click in Generate

Image 12 
[[File:Puttygen_generating.JPG|400px]]

To generate our key, we must move the mouse pointer constantly in the blank space of program.

Image 13 
[[File:Puttygen_generate_end.JPG|400px]]

Once our key generation is complete, we will add a passphrase.

Click Save public key to save our public key, we give the name of rsa.pub, do the same with save private key, and give the name of rsa.ppk.

A public key is like a lock on a door and the private key is like a key that opens the lock.

We mark the generated code in the text area and copy it, then we go to our OpenShift console.

Image 14 
[[File:Settings_openshift_copy_public_key.JPG|500px]]

Paste the code into Paste the contents of your public key file (. Pub) and click Save.

Image 15 
[[File:Settings_openshift_public_key_saved.JPG|500px]]

Perfect OpenShift now has our lock and we have the key.

Now we go to the Applications tab in our console OpenShift.

Click on our application startdolibarr.

Click in Want to log in to your application?.

Image 16 
[[File:SourceCode_and_Remote_Access.JPG|500px]]

Copy the code ssh 53641a41e0b8cdf5ec000b76@startdolibarr-sdme.rhcloud.com

We opened our WinSCP.

Image 17 
[[File:Login_WinSCP.JPG|500px]]

We put the first part, 53641a41e0b8cdf5ec000b76 before the @ in the User name field, and the second part, startdolibarr-sdme.rhcloud.com after the @ in the Host name field.

It is advisable not to place the password / passphrasse, at this point, for security reasons. We'll use it later.

Click in Advanced.

Image 18 
[[File:Login_WinSCP_SSH_private_Key.JPG|500px]]

In Private key file: select your private key rsa.ppk, click OK, click save, and click Login.

Image 19 
[[File:Warning_connect_to_WinSCP.JPG|500px]]

When we leave this nice window click Yes.

Image 20 
[[File:WinSCP_login_passphrasse.JPG]]

Here we place our passphrase and click OK.

Image 21 
[[File:Session_WinSCP_accept.JPG|500px]]

Viola we have access via SSH to our Gear.

On the left is our local space and right remote.

= Submit Dolibarr files =

Image 22 
[[File:Download_Dolibarr_generic_version.JPG|500px]]

We went down the generic version of Doibarr.

Image 23 
[[File:Uploading_DoliBarr_into_repo.JPG|500px]]

In the remote part, selected route
/var/lib/openshift/53641a41e0b8cdf5ec000b76/app-root/runtime/repo

Transfer the Dolibarr folder on the local machine to OpenShift, pressing F5. This process may take several minutes, so while we wait, we will work to create our Gear for the database.

Image 24 
[[File:Add_MySQL_5.5.JPG|500px]]

We return to the console and with our OpenShift application selected, we click on the bottom of the Databases section and select Add MySQL 5.5

Image 25 
[[File:Add_Cartridge_MySL_to_startdolibarr.JPG|500px]]

Click in add Cartridge.

Note -. In a normal application without Scale, the Cartridge Mysql be added to current Gear, but in our case, OpenShift reports that will address a new Gear for MySQL.

Image 26 
[[File:Add_MySQL_Please_make_note_of_these_credentials.JPG|500px]]

Copy the MySQL access credentials. They will be used later to access our data base.

Image 27 
[[File:Delete_Index_php.JPG|500px]]

Once you have completed the upload of dolibarr described in picture 23. Edit the index.php file.

We opened our favorite text editor and replace with the following code.

<?php 
header("Location: dolibarr/htdocs"); 
?>

We make a copy of index.php in dolibarr folder and re-edit it and remove dolibarr/.

<?php 
header("Location: htdocs"); 
?>

Image 28 
[[File:Index_php_inside_dolibarr_folder.JPG|500px]]

What we have just done, serves don't shown the structure our folders and files of dolibarr from the web browser, with the index.php we force redirect to the home of Dolibarr.

Finally, before starting the configuration of dolibarr, should use SSL (encryption protocol), which provides security when sending our data from the web browser to the server. The use of SSL provides plus extra measures of the dolibarr security, which are already good.

We opened our text editor again and add the following.

*RewriteEngine on 
*RewriteCond %{HTTP:X-Forwarded-Proto} !https 
*RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

Save with the name .htaccess right next to our dolibarr folder and index.php.

As shown in the following image.

Image 29 
[[File:Add_htaccess.JPG|500px]]

[[File:HttpAndhttps.JPG]]

Image 30 
[[File:Dolibarr_con_SSL.JPG|500px]]

Image 31 
[[File:Dolibarr_con_SSL_unfoll.JPG|500px]]

We see the SSL certificate is accepted by the browser.

= Run Dolibarr install Wizard =

We start the Dolibarr setup.

We select from the drop down, Default language to use (language code):, the appropriate language and click Next step.

Image 32 
[[File:Start_Install.JPG|500px]]

Click in start.

Image 33 
[[File:Environment_Variables_conextion_MySQL.JPG|500px]]

We review the image 26, when we created the MySQL Cartridge.

And we focus on the lines.

*Root User: adminCRERXju 
*Root Password: tccRTZ8-xCnK 
*Database Name: startdolibarr 
*Connection URL: mysql://$OPENSHIFT_MYSQL_DB_HOST:$OPENSHIFT_MYSQL_DB_PORT/

To create the connection to the database, OpenShift gives us some environment variables. For dolibarr can connect to the database, we need to know the value of these variables, so back to WinSCP and the .env/mysql folder find these variables, as shown in the picture above.

Click the right mouse button on OPENSHIFT_MYSQL_DB_HOST, click on edit and show us the value of the variable, copy and paste into the Server field as shown in the image below. We do the same for OPENSHIFT_MYSQL_DB_PORT variable and paste its value in the Port field.

Image 34 
[[File:Create_DDBB_in_configure_DoliBarr.JPG|500px]]

Note.- When you will these follow steps for the host and port for your particular installation, should be different than shown in this example.

Note2. - In this step, we also could create a different data base and a different owner, because be have the superuser credentials of MySQL, but this step does not touch it here today.

Click Next Step and displays the following window.

Image 35 
[[File:Confirm_configuration.JPG|500px]]

This screen basically tells us that the connection to the database has been established and this information is saved in the configuration file conf.php of dolibarr.

Click Next Step and start creating tables in the database, necessary for the work of Dolibarr.

Image 36 
[[File:Database_susetfull_created.JPG|500px]]

This screen reports that have completed the creation of the tables.

Click in Next step.

Image 37 
[[File:Insert_admin_credentials.JPG|500px]]

We fill the fields with the username and password, which will be the administrator, for this example I used admin/admin. For the real case should be a stronger password.

Click in Next step.

Image 38 
[[File:End_of_setup.JPG|500px]]

Click in Go to Dolibarr (setup area).

Image 39 
[[File:Insert_admin_credentials.JPG|500px]]

Insert the username and password of the administrator, as defined above and Viola. We are within Dolibarr.

= Appendix: Connection remote MySQL =

As a final step, we will see the connection from a local client database, to our remote MySQL.

For this example I will use HeidiSQL, which serves both MySQL or PostgreSQL database and is Free.

Open HeidiSQL.

The first thing to do is select MySQL (SSH tunnel) Network type drop down, in so doing, HeidiSQL adds a new tab called SSH tunnel, as shown in the image below.

Image 41 
[[File:Ssh_tunnel_HeidiSQL.JPG|500px]]

Note that, in the plink.exe location: field must specify the path PuTTY.exe, in the Password field entered the passphrase and Local Port field should always be in 3307.

We return to the Settings tab.

Image 42 
[[File:Settings_heidisql.JPG|500px]]

We fill the fields with the credentials of the database, select the database, click in Save and click in Open to test the connection.

Image 43 
[[File:HeidiSQL_has_established_connection.JPG|500px]]

And with that we end this tutorial.

== Addendum ==

=== Connection to MySQL gear ===