A suite is an npm package (@opencore-suites/<name>) that adds designs, blocks, steps or
equipment adapters, from the suites registry, with your licence token. The core works the same with any suite
removed: what a suite leaves stays inert and labelled, never deleted, and works again once it is reinstalled;
every version an installation ran is kept. (The suites store is not open yet.)
Suites : what each installed suite brings, and the copilot version every server runs.Suites : what each installed suite brings, and the copilot version every server runs.
IN-50 Install, update, remove a suite (a plant folder)
Purpose A suite in an installation, and every version it ran kept. Done by IT Before you start A licence token for the suites registry (or the suite's .tgz for a plant without internet access). In the plant folder (on a server, IN-51 first).
# Do this You should see Done
1 Sign in to the registry; paste the token when asked (it is not shown).Copy opencore-mes suite login The token is kept in .local/suites/.npmrc (mode 0600), for this installation only. 2 Install the suite.Copy opencore-mes suite install <name> <name> <version> installed in suites/<name>.3 Without internet access, instead: install it from its file.Copy opencore-mes suite install <name> --from <file> .tgz The same. 4 Restart OpenCore MES. The suite's migrations run; it is listed in the designer, and its designs can be started from it. 5 Later, to see, update, remove, or go back to a kept version (restart after each):Copy opencore-mes suite list
opencore-mes suite update <name>
opencore-mes suite remove <name>
opencore-mes suite use <name> @<version> A replaced or removed version is kept in suites/.versions/, never deleted; use puts one back.
About OpenCore MES : the version, build and runtime this installation runs, and its suites.About OpenCore MES : the version, build and runtime this installation runs, and its suites.
IN-51 Suites on a server
Purpose The suite commands on a server installed as part 2, with the suites kept outside the releases. Done by IT
# Do this You should see Done
1 Open the settings file and add SUITES_DIR=/var/lib/opencore-mes/suites; save and leave.Copy nano /etc/opencore-mes/opencore-mes.env — 2 Open a shell as the service's user, in its data folder.Copy sudo -u opencore bash The prompt changes to opencore@…. 3 In that shell: load the settings, and go to the data folder.Copy set -a; . /etc/opencore-mes/opencore-mes.env; set +a
cd /var/lib/opencore-mes — 4 In that shell, run the suite commands of IN-50, with the command's full path in front instead of opencore-mes, as here:Copy node /srv/opencore-mes/current/app/mes/cli.mjs suite login
node /srv/opencore-mes/current/app/mes/cli.mjs suite install <name> As in IN-50. 5 Leave the shell, and restart the service.Copy exit
systemctl restart opencore-mes —
IN-52 A language for the floor
Purpose Pages in a language besides English: the platform's words from its language pack, the plant's designs translated in the designs themselves. Done by IT, then governance Before you start The pack's name, lang-<tag> (lang-de, lang-ja, lang-ar), or its .tgz. In the plant folder (on a server, IN-51 first).
# Do this You should see Done
1 Install the language pack, as a suite (IN-50).Copy opencore-mes suite install lang-<tag> lang-<tag> <version> installed in suites/lang-<tag>.2 Restart OpenCore MES. The pack is listed on the Suites page, with how much of the platform's words it says, and whether a native speaker reviewed it. 3 Governance: in People & departments → Formats → Language, offer the language (or make it the plant's), and get the change approved. The language is offered in each person's menu and on the sign-in page; dates, times and numbers keep the plant's formats. 4 Designers: translate the plant's own designs on each design's Translations tab, and get them approved. People reading that language see the designs' words in it; a word not translated is shown in English.