V1.7.0 My app disappeared from the store but works

morgyann · July 29, 2026, 11:13pm

Since update 1.7.0, I have a MediaCMS application that no longer appears at all. It is no longer displayed in the summary, nor in tile form.
However, it works normally when I open it on its internet address. It appears functional in Dockhand containers.

Bin · July 30, 2026, 2:58am

@morgyann Did you manually execute docker compose up to start MediaCMS? You try to execute docker compose ls-a to see if the docker-compose yaml file is in the correct location.

morgyann · July 30, 2026, 10:16am

For this application to work correctly you must clone the repository. It works poorly with a simple YAML.

To deploy this application, you must therefore go through the SSH Terminal.

A developer, WisdomSky, offers us a single command line installation that compiles the cloning of the folder and its YAML specially adapted for CasaOS/ZimaOS.

gist.github.com

https://gist.github.com/WisdomSky/f6d0db67dc8378941c8dcb7a436c1c74

casaos-mediacms-install.sh

#!/bin/bash

echo "Downloading MediaCMS into /DATA/AppData/mediacms..."
mkdir -p /DATA/AppData/mediacms
cd /DATA/AppData/mediacms
git clone https://github.com/mediacms-io/mediacms.git
cd mediacms
echo "Starting MediaCMS docker-compose.yml..."
curl -fsSL https://gist.githubusercontent.com/WisdomSky/f6d0db67dc8378941c8dcb7a436c1c74/raw/docker-compose.yaml > docker-compose.yaml
docker compose up -d

This file has been truncated. show original

docker-compose.yaml

services:
  migrations:
    image: mediacms/mediacms:latest
    volumes:
      - ./:/home/mediacms.io/mediacms/
    environment:
      ENABLE_UWSGI: 'no'
      ENABLE_NGINX: 'no'
      ENABLE_CELERY_SHORT: 'no'
      ENABLE_CELERY_LONG: 'no'

This file has been truncated. show original

I just deployed MediaCMS on my test machine. The application works normally. But does not appear as a tile, nor in the listing of my applications in the new app store.

I have not yet tested with other applications that require cloning a repository and installation by the SSH terminal. Except those developed by @Lintux (ZFW) which work normally.

Bin · July 31, 2026, 2:18am

@morgyann At present, it is temporarily impossible to manage the container group started manually by docker compos up. We will deal with this problem as soon as possible. At present, you can access it quickly by adding links for the time being. Thank you for your understanding.

morgyann · July 31, 2026, 9:55am

THANKS. I actually created a shortcut. Looking forward to resolving this issue.

morgyann · July 31, 2026, 8:25pm

In fact, it’s better that way.

This allows applications to be deployed with another management interface (Portainer, Dockhand) or via the SSH terminal.
ZimaOS no longer wants to appropriate them to manage them. Which gets really awesome. We are no longer limited to just the ZimaOS management console.

Don’t correct it! I just tested it and it’s great.