Skip to main content

How to update proximamp

Update proximamp the same way you installed it. Once a day a command in the terminal checks whether a newer version is out and, if so, says so in a line at the end of its output. The PROXIMAMP_NO_UPDATE_CHECK variable, with any value, turns that check off; with --json and without a terminal the command neither checks nor tells.

Update​

proximamp update                               # the script in ~/.local/bin, Windows
sudo proximamp update                          # the script in /usr/local/bin
sudo apt update && sudo apt upgrade            # apt
sudo dnf upgrade                               # dnf
npm i -g proximamp@latest                      # npm (with sudo if installed with sudo)
                                               # npx with @latest needs no update
docker compose pull                            # Docker Compose
docker compose up -d
docker pull proximamp/proximamp                # docker run
docker rm -f proximamp                         # docker run

Start the docker run container again with the tunnel command from the Docker page, with your port and address: the sign-in and the address stay in the volume.

If the script put the program in /usr/local/bin, on RHEL, AlmaLinux, Rocky Linux and Oracle Linux (why) sudo doesn't find it: type this, and replace sudo proximamp the same way in the service command below:

sudo env "PATH=$PATH" proximamp update

If the download of proximamp update breaks off, the old version stays as it was: run the command again.

If a package manager, npm or a Docker image installed the program, proximamp update doesn't change it and names the command that updates it. Other answers of proximamp update:

  • "could not reach the releases: …": check the internet and try again;
  • "no rights to replace …": run it with sudo, and on Windows in a terminal opened as administrator;
  • "there is no release for this system (…)": the program isn't released for this system; what it needs is on the install page;
  • an answer ending in "nothing was changed": the program stayed as it was; try again later, and if the answer is the same, click "Ask a question" at the bottom of the page and include it.

Commands already running keep the old version until they exit, and while any of them runs, new commands go through the old version too: close them all and start them again.

The service​

The service runs on its own copy of the program. To move it to the new version, install it again from the folder with the same proximamp.yml (on Windows, without sudo, in a terminal opened as administrator):

sudo proximamp service install -c proximamp.yml

A new version of the apt or dnf package updates the service's copy and restarts it by itself.

Check​

proximamp version
npx -y proximamp@latest version                   # without installing
docker compose exec proximamp proximamp version   # Docker Compose
docker exec proximamp proximamp version           # docker run

The command prints the new version number. The service's copy prints its own version:

/usr/local/lib/proximamp-cli/proximamp version    # Linux
& "$env:ProgramFiles\proximamp\proximamp.exe" version   # Windows