Changes between Version 1 and Version 2 of Version2/Instalacion
- Timestamp:
- Sep 2, 2010, 2:19:03 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Version2/Instalacion
v1 v2 35 35 The server services use a database for persistence. By default it uses an Sqlite database, but you can change the configuration of the database editing the file config.py. After doing this, you have to execute the setup script which creates the tables in the database and generates the translations for the supported languages. 36 36 37 In order to know how to configure the database using mysql, postgres, oracle orany other database we support, take a look at [http://www.sqlalchemy.org/docs/05/dbengine.html#create-engine-url-arguments]37 In order to know how to configure the database using mysql, PostgreSQL, Oracle or any other database we support, take a look at [http://www.sqlalchemy.org/docs/05/dbengine.html#create-engine-url-arguments] 38 38 39 39 Execute the setup script: … … 45 45 == SSL Setup == 46 46 47 Opengnsys uses secure connections between 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 ssslsockets_example how to create your own CA, create certificates and sign them. Acrossthe Opengnsys platform, the SSL connections are always verified on both ends: both the client and the server.47 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:Verson2/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. 48 48 49 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 your own.49 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:Verson2/SSL_Certificate_Authority_Tutorial SSL Certificate Authority Tutorial]. 50 50 51 51 == Launch the server == … … 53 53 To execute the web interface, execute: 54 54 55 $ ./admin.py 55 {{{ 56 ./admin.py 57 }}} 56 58 57 59 The web server will be launched at http://localhost:8080. If you want to launch the server at a different port, use: 58 60 59 $ ./admin.py <port> 61 {{{ 62 ./admin.py <port> 63 }}} 60 64 61 65 Note that any port less than 1024 will need superuser privileged to be executed.
