# Platform Version Updates {% hint style="warning" %} ### CAUTION Before updating MOTAR, you should take a backup of your instance. See: [Backup & Restore Data](/motar-core-services/intro-to-core-services/admin/owning-company/backup-and-restore-data.md) {% endhint %} The Platform Version tab has a version checker that will tell you when there is a new version available to update: When a new version is available, (!) will show next to the Platform Version tab. Note the Installed Version vs Available Version in the image below. \\

The Platform Version tab notes a new version is available.

**Updating** your MOTAR Ghost to the latest version is **highly dependent** on your **installation** method. Choose the method below that matches your installation. If you do not know what type of installation you have, consult your platform admin. {% hint style="danger" %} ### WARNING Updating the platform version requires some degree of technical knowledge pertaining to your company's server architecture and installation method. Please review the steps below and if you are unsure of any of the steps, **DO NOT PROCEED,** reach out to your company administrator or [Contact Us!](/support/contact-us.md) {% endhint %} Choose the guide based on your installation method:
HELM Installation #### Upgrade {% hint style="danger" %} ### WARNING If you did not provide **secrets** for HELM install, **do NOT** **delete** the **secrets** . The update process will recreate secrets and motar won't be able to access your data. {% endhint %} To update the MOTAR version on your HELM install, run: {% code overflow="wrap" %} ```shell # Replace {new version} with the latest release number (e.g. 1.2.3) # Replace {yourvalues.yaml} with your Helm values file helm upgrade motar --version {new version} oci://harbor.dynepic.net/helmrelease/motar -f {yourvalues.yaml} -n motar ``` {% endcode %} #### Uninstall/Upgrade {% hint style="warning" %} If you **uninstall** instead of upgrade, you need to **backup** your secrets and your instance first! {% endhint %} * *Backup your secrets file (secrets backup is not covered in this guide. If you need assistance on how to backup your secrets, refer to your IT administrator.* * *Backup your MOTAR Instance:* [Broken mention](broken://pages/QByNki2DLeUSI013uSpN) Once you have backed up everything, you can run: ```sh helm uninstall motar -n motar ``` Once the uninstall process completes you can start the install process by running: 
# Replace {new version} with the latest release number (e.g. 1.2.3)
# Replace {yourvalues.yaml} with your Helm values file

helm install motar --version {new version} oci://harbor.dynepic.net/helmrelease/motar -f {yourvalues.yaml} -n motar
{% hint style="warning" %} The relevant **secrets** will persist (do not delete the ones that stayed) {% endhint %} If secrets were deleted you will need to destroy persistent volumes If you uninstall MOTAR before updating, you will need to restore from backup.\ Follow this guide to restore your data: [Broken mention](broken://pages/QByNki2DLeUSI013uSpN)
***
ARGO Installation Update the MOTAR version number to in your settings to the latest version number listed in your Platform Verision tab. *See example below.*
***
DOCKER Installation {% hint style="warning" %} The following guide is for Docker installtion/update on a Linux/Mac machine. For Windows machines, see the Tutorial setup installation guide: [/pages/C4IBgTqQMu1wRhcgqfTh#id-2.-installing-motar-with-docker](https://docs.motar.com/motar-core-services/intro-to-core-services/admin/owning-company/pages/C4IBgTqQMu1wRhcgqfTh#id-2.-installing-motar-with-docker "mention") For an **easier** install process, **download** the MOTAR Installer for **Windows**: {% embed url="" %} **Instructions** can be found here: [Broken mention](broken://pages/1i9AjJkceAKzepNzLT4P) {% endhint %} Installing via Docker * Download the correct install package for your operating system. * * *If you do not have access to this link, please reach out to*[ *motar@dynepic.com*](mailto:motar@dynepic.com) *for assistance.* If you want to shut down your instance during the update run: ``` docker compose down ``` {% hint style="success" %} Take note of where you download the MOTAR installation package because you will need it to configure the MOTAR Environment. {% endhint %} *** {% code overflow="wrap" %} ```sh # Replace with the MOTAR version you downloaded (e.g., 1.2.3) cd /path/to/motar/download/directory/motar--beta-docker-compose/EasySetup ``` {% endcode %} ### Check and Configure Docker {% hint style="warning" %} Before running Docker commands, ensure the Docker desktop app is running. {% endhint %} * Open your terminal window 1. Search **Terminal** in Spolight or find it in Application > Utilities * Run the following **command** to check if Docker Compose is installed: ```shell docker compose version ``` * You should see a result like this example *(your result may vary):* ```sh Docker Compose version v2.31.0-desktop.2 ``` * If no errors, continue, otherwise if you encounter a permission error, prepend sudo to the command: ```sh sudo docker compose version ``` * Make sure your Docker is running by typing: ```sh docker ps ``` * As an **example**, if docker is running, but there are no containers running you may see output like this *(if you have containers running you may see additional details beneath these headings)*: ```sh CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` * If you get the proper response, continue to [#linux-mac-1](#linux-mac-1 "mention"), otherwise if you encounter a permission error, use the sudo command: ```sh sudo docker ps ``` {% hint style="warning" %} If you still encounter an error or do not see the expected output (see below), please follow Docker’s documentation for fixing your Docker or Docker Compose. {% endhint %} **With Docker running it is time to Configure your MOTAR Environment** ### Configure Your MOTAR Environment While in Terminal, you will configure your MOTAR Docker package. 1. **Change directory** to the location you saved the MOTAR docker compose install package from [#motar-installation-packages](#motar-installation-packages "mention") {% hint style="info" %} This is the folder where you saved your **motar-**[**3.0.1**](#user-content-fn-1)[^1]**-docker-compose.tar.gz** file. {% endhint %} {% code overflow="wrap" %} ```sh cd / # Change to your MOTAR download directory # Example: cd /downloads/ ``` {% endcode %} 2. **Unpack** the MOTAR installation file (if you already unpacked the file, you may skip to step 3) 
# Replace <version-number> with the MOTAR version you downloaded (e.g., 1.2.3)
tar -xvf motar-3.0.1-beta-docker-compose.tar.gz
3. Once the file is **unpacked**, you will need to change directory into the EasySetup folder. 
cd motar-3.0.1-beta-docker-compose/EasySetup
{% hint style="warning" %} For other more **advanced** options, replace the child sub-directory with ‘SelfProxy-Advanced’ or ‘EasyDNS’. **This walk-through will only provide instructions for ‘EasySetup’.** Reach out to with questions. {% endhint %} 4. **Before** launching MOTAR, you'll need to **copy sample environment files** and update with your deployment’s specifics. Sample environment files are provided to help you get started. {% code overflow="wrap" %} ```sh #Replace with the MOTAR version you downloaded (e.g., 1.2.3) cd /path/to/motar/download/directory/motar-3.0.1-beta-docker-compose/EasySetup ``` {% endcode %} ```sh cp ../sample_env .env ``` 
cp ../sample_motar_env motar.env
{% hint style="info" %} For this demo the URL for your MOTAR intance will be set to "motarghost.com". {% endhint %} {% hint style="success" %} **MOTAR images** are hosted in Dynepic’s private **Harbor** repository. Follow these steps to authenticate {% endhint %} ### Deploying MOTAR with Docker Compose {% hint style="success" %} MOTAR can be deployed in different configurations. Choose the setup that best suits your needs. {% endhint %} 1. Ensure you are still in the EasySetup folder in **Terminal** {% code overflow="wrap" %} ```sh #Replace with the MOTAR version you downloaded (e.g., 1.2.3) cd motar-/EasySetup #Your installation directory docker compose up -d # brings up the deployment in the background ``` {% endcode %} {% hint style="danger" %} Deployment of MOTAR on your local machine will take 3-5 minutes. {% endhint %} *You should see the following progress/message(s)* ```sh ✔[+] Running 19/19 ✔ Network motar_motar Created ✔ Container minio Healthy ✔ Container motar-traefik-1 Started ✔ Container nats Started ✔ Container dnsmasq Started ✔ Container postgres Healthy ✔ Container clamav Started ✔ Container db-init Exited ✔ Container obj_init Exited ✔ Container assets Healthy ✔ Container scanner Started ✔ Container devices Started ✔ Container hub Started ✔ Container admin Started ✔ Container studio Started ✔ Container login Started ✔ Container studio-permissions Started ✔ Container hub-permissions Started ✔ Container devices-permissions Started ``` {% hint style="warning" %} **Launching** a browser window may direct your admin page to **https\://**\ to avoid this, launch in a private window. This should keep the path **http\://** {% endhint %} ### Configuring Network & Domain Routing To ensure your client device can resolve domain names correctly, configure your DNS settings. 1. Use the following **Terminal** command to backup your 'hosts' file: ```sh cp /etc/hosts /etc/hosts_bak ``` 2. Append your 'hosts' file with the following command: {% code overflow="wrap" fullWidth="true" %} ```sh IP="127.0.0.1" BASE_URL="motarghost.com" echo "$IP admin.$BASE_URL hub.$BASE_URL studio.$BASE_URL devices.$BASE_URL api-minio.$BASE_URL login.$BASE_URL console-minio.$BASE_URL minio" | sudo tee -a /etc/hosts ``` {% endcode %}

[^1]: Version numbers may vary. Please refer to the downloaded file. [^2]: Replace with the MOTAR version you downloaded (e.g., 1.2.3) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.motar.com/motar-core-services/intro-to-core-services/admin/owning-company/platform-version-updates.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.