Page History
...
TODO: Martin Walk or TUBerlin provide details on the infrastructure behind https://depositonce.tu-berlin.de, especially in terms of the Node.js setup/configuration and setup/configuration of proxies.
Our servers run at the university's IT department in an Open Stack environment with these specs:
Server | Cores | RAM |
---|---|---|
Backend | 16 | 64GB |
Frontend | 8 | 32GB |
PostgreSQL | 4 | 16GB |
SOLR | 2 | 8GB |
This is our PM2 configuration file:
Code Block | ||||
---|---|---|---|---|
| ||||
{
"apps": [
{
"name": "dspace-ui",
"cwd": "/srv/dspace-ui-deploy",
"script": "dist/server/main.js",
"node_args": "--max_old_space_size=8192",
"env": {
"NODE_ENV": "production",
"DSPACE_REST_SSL": "true",
"DSPACE_REST_HOST": "api-depositonce.tu-berlin.de",
"DSPACE_REST_PORT": "443",
"DSPACE_REST_NAMESPACE": "/server"
}
}
]
} |
The frontend runs behind an Apache proxy, as described in the Installing DSpace page.
The backend also runs behind an Apache proxy, as described in the Installing DSpace page. I increased the Java memory significantly:
Environment="JAVA_OPTS=-Djava.awt.headless=true -Xmx8G -Xms2G -Dfile.encoding=UTF-8"
Optimization Strategies
Node.js configuration for multi-threading
...