NextExplorer Custom App?

Insight & Feedback
1

Has anyone succeeded in getting NextExplorer to work using the custom app feature in ZimaOS?

2

services:
nextexplorer:
image: nxzai/explorer:latest
container_name: nextexplorer
restart: unless-stopped
ports:

  • ‘3000:3000’
    volumes:
  • ./config:/config
  • ./cache:/cache

Each /mnt/ mount becomes a top-level volume in the UI

#####################################################################

In addition to the configuration recognized by the import, we also need the following information:

1. Port and path to the app's WebUI
2. Location of the directory or file to be mounted
3. Port mapping from host to container
4. Other optional configurations

These include but are not limited to these cases and still need to be confirmed or modified by you.

3

I did finally get NextExplorer to work. Here is the exported compose file ZimaOS created after I got it to work like I wanted. The “volume-name” after each instance of “source” and “target” were put there by me to edit out any personal naming styles I have. In my case they are all SSDs and HHDs.

#Here is the file. Feel free to use.

name: nextexplorer
services:
nextexplorer:
cpu_shares: 90
command:
container_name: nextexplorer
deploy:
resources:
limits:
memory: 12383318016
reservations:
devices:
environment:

  • NODE_ENV=production
  • PUBLIC_URL=http://:3000
    image: nxzai/explorer:latest
    labels:
    icon: https://icon.casaos.io/main/all/nextexplorer.png
    ports:
  • target: 3000
    published: “3000”
    protocol: tcp
    privileged: true
    restart: unless-stopped
    volumes:
  • type: bind
    source: /DATA/AppData/nextexplorer/config -./cache
    target: /config -./cache
  • type: bind
    source: /media/volume-name
    target: /mnt/volume-name
  • type: bind
    source: /media/volume-name
    target: /mnt/volume-name
  • type: bind
    source: /media/volume-name
    target: /mnt/volume-name
  • type: bind
    source: /media/volume-name
    target: /mnt/volume-name
  • type: bind
    source: /media/volume-name
    target: /mnt/volume-name
    devices:
    cap_add:
    network_mode: bridge
    x-casaos:
    author: self
    category: self
    hostname: 192.168.8.218
    icon: https://icon.casaos.io/main/all/nextexplorer.png
    index: /
    is_uncontrolled: false
    port_map: “3000”
    scheme: http
    store_app_id: nextexplorer
    title:
    custom: “”
    en_us: nextexplorer
4 
name: nextexplorer

services:
  nextexplorer:
    image: nxzai/explorer:latest
    container_name: nextexplorer
    restart: unless-stopped

    ports:
      - "6000:3000"

    environment:
      - NODE_ENV=production
      - PUID=1000
      - PGID=1000
      
      # ⚠️ IMPORTANT: Set this to your own IP/domain + port
      # Example: https://192.168.1.100:6000
      - PUBLIC_URL=https://YOUR-IP:6000
      
      - MAX_FILE_SIZE=2GB
      - SEARCH_MAX_RESULTS=200
      - SEARCH_TIMEOUT_MS=10000
      - EDITOR_EXTENSIONS=.txt,.md,.json,.yaml,.yml,.conf,.log

    volumes:
      - /DATA/AppData/nextexplorer/config:/config
      - /DATA/AppData/nextexplorer/cache:/cache
      
      # ⚠️ IMPORTANT: CHANGE THIS PATH TO YOUR OWN STORAGE LOCATION
      # Example: /mnt/media or /home/user/data
      - /DATA/storage:/mnt/NAS

    cpu_shares: 90

    deploy:
      resources:
        limits:
          # ⚠️ OPTIONAL: Adjust memory limit to your system
          # Example: 2G, 4G, 8G, etc.
          memory: 32G

    network_mode: bridge
    privileged: false
5

Thanks. Yesterday I posted my compose file that worked successfully, but the mods withheld it for review and have yet to approve it. Mine is very similar to yours except the ports and volumes. I had two internal drives and four external drives in an external drive enclosure.