Difference between revisions of "Jorgal"
Line 4: | Line 4: | ||
==Installing new pairs== |
==Installing new pairs== |
||
If you want the new pair to appear on Jorgal, you'll first have to edit /home/apy/apertium-html-tools/config.conf on gtweb and append mode-name(s) to the comma-separated list ALLOWED_PAIRS. |
|||
⚫ | |||
⚫ | |||
Read /home/apy/README for more info. |
Read /home/apy/README for more info. |
Revision as of 11:01, 13 January 2017
Docs for updating http://gtweb.uit.no/jorgal because I never remember how to edit the gt docs:
Contents
Installing new pairs
If you want the new pair to appear on Jorgal, you'll first have to edit /home/apy/apertium-html-tools/config.conf on gtweb and append mode-name(s) to the comma-separated list ALLOWED_PAIRS.
The install the pair with
sudo dnf install apertium-from-to
after ssh-ing into gtweb, then run
sudo /home/apy/update
Read /home/apy/README for more info.
You also want to:
sudo dnf clean metadata sudo dnf upgrade -y
since nightly updates don't always happen.
Ensuring current pairs are up-to-date
ssh into gtweb and run
sudo dnf clean metadata sudo dnf upgrade -y
The dnf upgrade should happen every morning, but if Tino's nightly repo needs a lot of time to compile, or the build service is down, things may lag a bit more. Look at the bottom of http://apertium.projectjj.com/apt/logs/apertium-sme-nob/stderr.log if you're interested in what might have happened.
Automatic updates and restarts
There are some systemd units that do the automatic package updates and restarting of the MT service (Apy).
To inspect the updating units:
systemctl cat dnf-automatic.service systemctl cat dnf-automatic.timer
The dnf-automatic.service should restart Apy after running (see the ExecStopPost line)).
We also restart Apy twice more a day, just in case it gets stuck or something:
systemctl cat restart-apy.service systemctl cat restart-apy.timer
What versions are running?
gtweb.uit.no/jorgal is running the packages from Tino's nightly repo, so they should be at most 24 hours out-of-date, given the build wasn't broken (if the version in SVN doesn't compile when Tino's machine tries updating, the package isn't updated). There are some more details at ~apy/README on gtweb.
gtweb.uit.no/mt and gtweb.uit.no/mt/testing should also now be running the nightly repo, but see the file /opt/mt/README on gtweb for how to make sure.
(https://build.opensuse.org/package/show/home:TinoDidriksen:nightly/apertium-sme-nob shows the latest available nightly sme-nob package, while http://apertium.projectjj.com/apt/logs/apertium-sme-nob/stderr.log shows the build log of that package.)