Hi Simon
Firstly, as Dan mentioned, AMOS was never expected to be run in multiple instances. There were a lot of low-level tweaks, hacks and direct SQL statements executed during the initial import of data and even later after that. At lang.moodle.org, we have a couple of additional shell scripts run via crontab that actually control all the AMOS jobs (tracking for changes in Moodle branches etc).
As mentioned by Dan, more effective way seems to be to implement your Totara extensions either via new plugins (forked off the standard ones) or via a custom local_totara plugin that would just provide extra strings you added to your own versions of plugins. That way, this local_totara plugin could be imported into lang.moodle.org and be translated as an ordinary plugin.
- AMOS_REPO_LANGS points to a local clone of the Git mirror of the CVS repository with translations. It was used to read all translations for Moodle 1.x (as since 2.x AMOS only is used). AMOS_REPO_MOODLE is path to the clone of moodle.git that AMOS tracks and gets English string changes from it.
- AMOS requires 2.3 because lang.moodle.org runs at 2.3. I'm not sure (can't remember) if it relies on some 2.3 specific features though.
- As you can easily find by grepping for that constant, it is not used any more in the code. It was required for the initial bootstrap (git log might tell you more). Those root commits in config-dist.php are probably just some fake commits that were replaced with real values in config.php.
- As said, we never expected someone being that crazy to run their own AMOS instance
so yes, modifications would be required and no HOWTO-RUN-OWN-AMOS.txt should be expected to be honest. Sorry.
In summary, let me discourage you from this approach. Better to reorganise your Totara modifications in a way that will allow you to use standard AMOS interface (via local_totara for example as mentioned above).
HTH
