| 12 | | = Instalación del Repositorio = |
| | 12 | = Instalación del servidor = |
| | 13 | |
| | 14 | En el servidor corren dos servicios el !WebConsole y el OGDaemon Server. Además hace falta un |
| | 15 | |
| | 16 | == Dependencias == |
| | 17 | |
| | 18 | Para ejecutar los servicios de !OpenGnSys hace falta instalar algunas dependencias. |
| | 19 | You need to execute Opengnsys server services (the '''admin interface''' and the '''daemon''') in a UNIX-like operative system as Linux. By default we use Sqlite as the database backend, but you can use any other databases that web.py and Sqlalchemy frameworks support. |
| | 20 | |
| | 21 | === Arch Linux === |
| | 22 | |
| | 23 | {{{ |
| | 24 | pacman -S community/python-sqlalchemy python-pip python-ldap |
| | 25 | easy_install wsgilog |
| | 26 | pip install formalchemy |
| | 27 | }}} |
| | 28 | |
| | 29 | === Debian / Ubuntu === |
| | 30 | |
| | 31 | {{{ |
| | 32 | apt-get install python-sqlalchemy python-pip python-ldap |
| | 33 | easy_install wsgilog |
| | 34 | pip install formalchemy |
| | 35 | }}} |
| | 36 | |
| | 37 | == Configuración == |
| | 38 | |
| | 39 | En el servidor es necesario que exista una base de datos que usarán los dos servicios. Por defecto es Sqlite, pero puedes cambiar la configuración en el fichero config.py para que no sea así. Para saber como configurar la base de datos usando mySQL, PostgreSQL, Oracle o cualquier otra base de datos que soporta SQLAlchemy echar un vistazo a [http://www.sqlalchemy.org/docs/05/dbengine.html#create-engine-url-arguments]. Después de hacer eso sólo habrá que ejecutar: |
| | 40 | |
| | 41 | {{{ |
| | 42 | ./setup.sh |
| | 43 | }}} |
| | 44 | |
| | 45 | Esto generará la base de datos y también los fichero de traducción para los lenguajes soportados. |
| | 46 | |
| | 47 | === SSL Setup === |
| | 48 | |
| | 49 | OpenGnSys uses secure connections among server, repositories and clients. This is done using SSL certificates certified by a CA (Certificate Authority). Note that it only checks that the certificate is valid and the certificate is trusted. You can see in [wiki:Version2/SSL_Certificate_Authority_Tutorial SSL Certificate Authority Tutorial] how to create your own CA, create certificates and sign them. Across all the Opengnsys platform, the SSL connections are always verified on both ends: both the client and the server. |
| | 50 | |
| | 51 | You can configure in the config file (config.py) the path to the private key of the server certificate, the path to the public key, and the path to the public key of the CA certificate. By default we include example files for each of them in the web/ssl directory, and those are the files configured to be used in the default config file. This is done for convenience, but if you want security you should create, use and deploy your own as explained in [wiki:Version2/SSL_Certificate_Authority_Tutorial SSL Certificate Authority Tutorial]. |
| | 52 | |
| | 53 | == WebConsole == |
| | 54 | |
| | 55 | Para ejecutar la WebConsole: |
| | 56 | |
| | 57 | {{{ |
| | 58 | ./admin.py |
| | 59 | }}} |
| | 60 | |
| | 61 | El servicio web será lanzado en http://localhost:8080. Si quieres modificar el puerto usado: |
| | 62 | |
| | 63 | {{{ |
| | 64 | ./admin.py <puerto> |
| | 65 | }}} |
| | 66 | |
| | 67 | Recordad que para un puerto menor que 1024 hace falta tener privilegios de superusuario. |
| | 68 | |
| | 69 | == OGDaemon Server == |
| | 70 | |
| | 71 | Este demonio trabaja por defecto el puerto 1101, pero puede ser modificado en el fichero config.py usando la variable '''server_daemon_port'''. Para ejecutarlo: |
| | 72 | |
| | 73 | {{{ |
| | 74 | ./daemon.py |
| | 75 | }}} |
| | 76 | |
| | 77 | = Instalación del repositorio = |
