... | ... | @@ -4,7 +4,7 @@ Welcome to the ls.ext wiki! |
|
|
|
|
|
![System components](https://docs.google.com/drawings/d/1fnN3TmRSIy1KjEl5I6fF65v7mLwiOD24MNSUNs7_Tds/pub?w=1068&h=700)
|
|
|
|
|
|
The diagram shows the components of a default setup of LS.ext, and how they are connected. The different components run as docker containers in a closed network and communicate directly to ports only available internally in the network, with only 3 services (ports) exposed: catalinker, patron-client and Koha.
|
|
|
The diagram shows the components of a default setup of the LS.ext system, and how they are connected. The different components run as docker containers in a closed network and communicate directly to ports only available internally in the docker-network, with only 3 services (ports) exposed: catalinker, patron-client and Koha.
|
|
|
|
|
|
* [[System components overview|System components overview]]
|
|
|
* [[Ontology|Ontology]]
|
... | ... | @@ -21,7 +21,14 @@ The diagram shows the components of a default setup of LS.ext, and how they are |
|
|
|
|
|
## Deployment
|
|
|
|
|
|
The system can be deployed in the same manner as how you provision your development environment: by running `docker-compose up`.
|
|
|
We at OPL use `docker-compose` both for provisioning our development machines as well as for provisioning our production servers. Updating a services is just a matter of specifying a different container image in the docker-compose configuration file and restart the service with 'docker-compose up -d <service>`.
|
|
|
|
|
|
|
|
|
## Operations
|
|
|
|
|
|
### Supervision & Metrics
|
|
|
|
|
|
### Backup & restore
|
|
|
|
|
|
## Customizations
|
|
|
|
... | ... | |