Skip to content

PathLMS 0.125.1

Choose a tag to compare

View all tags
@Ottomatic-Mike Ottomatic-Mike released this 28 Sep 06:20
· 3 commits to main since this release
v0.125.1
f4270d0

What changed in this version

A small fix for learners. It installs like any other update.

Fixed

  • A quiz you already passed says so. Coming back to a quiz you passed used to offer "Start the questions". Now the page says "You passed these questions." Press "See your score" to look at how you did.

  • A learning path says what its number counts. The top of a path used to say "0% Complete" even when a learner was well into the first course. It now says "0% of the courses finished", and that a course counts once you finish all of it.

  • A gray brand color is turned down, not turned blue. Choosing a very light or very dark gray could come back as a blue nobody picked. Now it is turned down, as a middle gray already was.

  • Clearer words about how long an update can take. The Update screen's note about moving the database is now a few short sentences. It says that some updates move the database, that nobody can use PathLMS while that runs, and roughly how long that is for a database your size.

  • An update can no longer be run by an old updater. PathLMS keeps a small helper container after it replaces its own updater, so its log can be read. If something started that helper again later, it could put back an older updater, and the next update would then fail and put itself back. The helper now does nothing unless it is replacing the updater it was made for, and the updater removes old helpers when it starts.

  • A learner can no longer raise their own figure on a manager's report. The progress report counted records a learner could write for themselves. It now counts only the items they really finished.

  • The Updates screen says what it means. Where it said "Published without a description", it now says "Nothing needs doing by hand after this update."

Installing this

Download the files below into one empty directory and follow INSTALL.md. You need Docker and nothing else: no copy of the source code, no git, and no Node.

File What it is
docker-compose.yml The whole stack, encryption included. One file, one command.
pathlms.env Your settings, with this release's images already named.
INSTALL.md Numbered steps, from nothing to signed in.
rollback.sh Keep it beside the others. It puts this system back on the version it was running before the last upgrade. Run it as: bash rollback.sh
restore-files.sh Keep it beside the others. It reads a file backup back to prove it is usable, and puts the uploaded files back when they have been lost. Run it as: bash restore-files.sh --verify
check-my-settings.sh Reads your two files and says whether they will work, BEFORE you start anything. It catches the mistakes people make pasting settings into a text box: two settings on one line, the same setting written twice, the address left commented out, image addresses that disagree about the version, a settings file under the wrong name, and an administrator password too short to create an account. Run it as: bash check-my-settings.sh
collect-deploy-evidence.sh Writes one file describing what this installation is actually doing: versions, where the data lives, whether the backups exist, how it is reached, which ports are open. It sends nothing anywhere and prints no password or key. Run it as: bash collect-deploy-evidence.sh
remove-old-images.sh Says how much disk the older versions of PathLMS on this machine are using, and clears the ones nothing is running. It always keeps the two most recent, so going back stays instant, and removes nothing until you add --yes.

If your machine is one of these

Some kinds of server decide one or two things their own way. There is a page for each of those below. Download the one that applies to you and read it beside INSTALL.md; it says what is different and sends you back there for everything else.

Page For
UNRAID.md Unraid, where a stack of containers needs a Compose plugin and the data has to go on the right storage.
BEHIND-A-PROXY.md A deployment with nginx, Caddy or a load balancer in front holding the certificate, which needs one setting here and a few lines there.
CHANGING-THE-PORT.md Anybody moving the port people arrive on, and anybody whose deployment did not come back on the new one. Keep it on the server: its recovery half is written to be read when no screen is reachable.
WHY-THE-COMPOSE-FILE-IS-LIKE-THIS.md Why a line in docker-compose.yml is the way it is, service by service. The compose file carries what you need while editing; this carries the reasoning behind it.

Upgrading an existing installation

Change these three lines in your settings file and run docker compose up -d. The product can also do it for you, taking a backup first and putting everything back if anything fails.

One thing to know before you upgrade into this release. This version opens a second port, 3443, for encrypted connections, so that turning encryption on needs nothing but a certificate you make or paste in on the Settings screen. If something else on your machine already uses 3443, Docker refuses to start and says so, naming the port. Put a free one in PATHLMS_PUBLISHED_TLS_PORT in your settings file and start again.

If something in front of this system holds your certificate and you would rather that port were not reachable from outside, set PATHLMS_PUBLISHED_TLS_ADDRESS to 127.0.0.1: including the colon.

PATHLMS_API_IMAGE=ghcr.io/path-lms/api@sha256:280ccdaaeac55aa797814fdedd4cab9968608f18b44e32790561011ffdfca3f4
PATHLMS_WEB_IMAGE=ghcr.io/path-lms/web@sha256:21126fdb392b61ee329abe0f8aa431e37b7a9d54c8c8b603485021e9c22994da
PATHLMS_DB_IMAGE=ghcr.io/path-lms/db@sha256:8cce3794658baa883c6455cfb27c0a2af8a11d4027dc9c970e11152bfcb5570f

What is published

Three container images and the files above. No source code: the two source archives on this page are added by GitHub itself and hold nothing.

Assets 15
Loading