Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Babel / Server Tool Admin Guide"
< Babel
(Created page with "Category:Babel The server at babel.eclipse.org runs the typical LAMP stack -- Linux, Apache, MySQL, PHP. To manage the server, committers must SSH to build.eclipse.org u...") |
|||
| Line 4: | Line 4: | ||
To manage the server, committers must SSH to build.eclipse.org using their committer account, then SSH into babel.eclipse.org using a local Babel account. | To manage the server, committers must SSH to build.eclipse.org using their committer account, then SSH into babel.eclipse.org using a local Babel account. | ||
| + | |||
| + | Most of the daily work is done by the 'genie' account. Her home directory looks like this: | ||
| + | |||
| + | * backups/: directory that contains backup files from the deployment process | ||
| + | * backup.sh: launched from cron, this backs up Babel content | ||
| + | * dbmaintenance_15min.sh: launched from cron, this performs database maintenance | ||
| + | * deployBabelLive.sh: Main Babel deployment script. See: https://wiki.eclipse.org/Babel_/_Server_Tool_Development_Process | ||
| + | * import_bugzilla.sh: launched from cron, this regularly imports Bugzilla email addresses for accounts | ||
| + | * max_userid.txt: this file is used to determine if new Bugillz accounts are used. | ||
| + | * publishPackFromLive.sh: this script builds the language packs from the live database, and publishes them to download.eclipse.org | ||
| + | * publishPackFromStaging.sh: as above, but build language packs from the staging database | ||
| + | |||
| + | See also: https://wiki.eclipse.org/Babel_/_Server_Background_jobs | ||
| + | |||
| + | |||
| + | |||
| + | == Databases == | ||
| + | The MySQL database server on babel.eclipse.org only contains an old snapshot of the Babel database. The babel.eclipse.org server tool uses another physical server for database. | ||
| + | |||
| + | Please ask the Eclipse Webmasters if you need to perform maintenance on the databases. | ||
| + | |||
| + | |||
| + | == Web Server === | ||
| + | |||
| + | Use the '''rcapache2''' command (as root) to manage the Apache web service. | ||
| + | rcapache2 configtest | ||
| + | rcapache2 restart | ||
Revision as of 13:33, 16 June 2015
The server at babel.eclipse.org runs the typical LAMP stack -- Linux, Apache, MySQL, PHP.
To manage the server, committers must SSH to build.eclipse.org using their committer account, then SSH into babel.eclipse.org using a local Babel account.
Most of the daily work is done by the 'genie' account. Her home directory looks like this:
- backups/: directory that contains backup files from the deployment process
- backup.sh: launched from cron, this backs up Babel content
- dbmaintenance_15min.sh: launched from cron, this performs database maintenance
- deployBabelLive.sh: Main Babel deployment script. See: https://wiki.eclipse.org/Babel_/_Server_Tool_Development_Process
- import_bugzilla.sh: launched from cron, this regularly imports Bugzilla email addresses for accounts
- max_userid.txt: this file is used to determine if new Bugillz accounts are used.
- publishPackFromLive.sh: this script builds the language packs from the live database, and publishes them to download.eclipse.org
- publishPackFromStaging.sh: as above, but build language packs from the staging database
See also: https://wiki.eclipse.org/Babel_/_Server_Background_jobs
Databases
The MySQL database server on babel.eclipse.org only contains an old snapshot of the Babel database. The babel.eclipse.org server tool uses another physical server for database.
Please ask the Eclipse Webmasters if you need to perform maintenance on the databases.
Web Server =
Use the rcapache2 command (as root) to manage the Apache web service.
rcapache2 configtest rcapache2 restart