1

i know there are Emoncms Docker...run Emoncms on your machine in 4 commands!

that seems to still have something on the todo list thou, and it deals with the command line too that i’m not a fan of since there is not much ui control

i was wonderin if anybody has done it via portainer?

for esphome i did this to make a “stack”:

version: '3'
services:
  esphome:
    container_name: esphome
    image: ghcr.io/esphome/esphome
    volumes:
      - /path/to/esphome/config:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    privileged: true
    ports:
      - 6052:6052
    network_mode: host

currently i use a combo of GitHub - sprintcube/docker-compose-lamp: A basic LAMP stack environment built using Docker Compose. and adding emoncms to that, but that one is kind of messy too and no control from portainer either

2

@TrystanLea @glyn.hudson

is the stack file i provided the same as docker-compose.yml ?

or do i miss something?

3

image

so no that was not the case

4

Sorry Bo, Im struggling to follow what you are doing above

What is the stack file? Im probably not familiar enough with stacks to help…

5

stack file is prob the wrong term, but its the text you insert in portainer to deploy the stack

image
image1920×1032 98.6 KB

in the above picture you just enter a name, then in the text box insert the text

version: '3'
services:
  esphome:
    container_name: esphome
    image: ghcr.io/esphome/esphome
    volumes:
      - /path/to/esphome/config:/config
      - /etc/localtime:/etc/localtime:ro
    restart: unless-stopped
    privileged: true
    ports:
      - 6052:6052
    network_mode: host

and hit deploy and after a while i have esphome running to compile firmware for my esphome devices

makes it dead simple for os NOOP’s to lunch something and there is no command line work