Difference between revisions of "Jorgal"
| Line 1: | Line 1: | ||
Docs for updating |
Docs for updating https://gtweb.uit.no/jorgal because I never remember how to edit the gt docs: |
||
==Installing new pairs== |
==Installing new pairs== |
||
See https://github.com/unhammer/gtweb-apy-conf#installing-new-language-pairs |
|||
If you want the new pair to appear on Jorgal, you'll first have to edit <code>/home/apy/apertium-html-tools/config.conf</code> on gtweb and append mode-name(s) to the comma-separated list <code>ALLOWED_PAIRS</code>. |
|||
The install the pair with <pre>sudo dnf install apertium-from-to</pre> after ssh-ing into gtweb, then run <pre>sudo /home/apy/update</pre> |
|||
Read /home/apy/README for more info. |
|||
You also want to: <pre>sudo dnf clean metadata |
|||
sudo dnf upgrade -y</pre> since nightly updates don't always happen. |
|||
==Ensuring current pairs are up-to-date== |
==Ensuring current pairs are up-to-date== |
||
ssh into gtweb and run |
ssh into gtweb and run |
||
<pre>sudo dnf clean metadata |
|||
sudo |
<pre>sudo systemctl start dnf-automatic</pre> |
||
(This command will take care of cleaning metadata first, and restarting apy afterwards.) |
|||
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. |
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== |
==Automatic updates and restarts== |
||
| Line 33: | Line 29: | ||
We also restart Apy twice more a day, just in case it gets stuck or something: |
We also restart Apy twice more a day, just in case it gets stuck or something: |
||
<pre> |
<pre> |
||
systemctl cat restart-apy.service |
systemctl cat restart-apy.service |
||
systemctl cat restart-apy.timer |
systemctl cat restart-apy.timer |
||
</pre> |
</pre> |
||
More info at https://github.com/unhammer/gtweb-apy-conf#README.org |
|||
==What versions are running?== |
==What versions are running?== |
||
Latest revision as of 12:03, 28 February 2017
Docs for updating https://gtweb.uit.no/jorgal because I never remember how to edit the gt docs:
Contents
Installing new pairs[edit]
See https://github.com/unhammer/gtweb-apy-conf#installing-new-language-pairs
Ensuring current pairs are up-to-date[edit]
ssh into gtweb and run
sudo systemctl start dnf-automatic
(This command will take care of cleaning metadata first, and restarting apy afterwards.)
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[edit]
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
More info at https://github.com/unhammer/gtweb-apy-conf#README.org
What versions are running?[edit]
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.)
How do I see unknown words?[edit]
ssh gtweb /home/apy/dump-missing-words
