Any step by step guides to using Portainer and YNH?

Discuss
15

In my tests I usually put ./folder:/folder for the volumes. (beware of the dot!) It means that the data for the container will be put in the directory where the docker-compose.yml file lies.

So, I removed everything related to Bookstack too, and tried Lazylibrarian. It worked right away !

LazyLibrarian setup 
---
version: "2.1"
services:
  lazylibrarian:
    image: linuxserver/lazylibrarian
    container_name: lazylibrarian
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - DOCKER_MODS=linuxserver/calibre-web:calibre|linuxserver/mods:lazylibrarian-ffmpeg #optional
    volumes:
      - ./config:/config
      - ./downloads:/downloads
      - ./books:/books
    ports:
      - 5299:5299
    restart: unless-stopped

cd $your_path_to_yml_file
docker-compose up -d
# It will take some time to initialize after starting up the container

# Meanwhile
yunohost app install redirect -a "label=LazyLibrarian&domain=book.domain.com&path=/&redirect_path=http://127.0.0.1:5299&redirect_type=private_proxy"

And it worked directly.

I cannot quite acknowledge everything you did and tried, but I will try.

  1. I am not sure what you copied and where to. This kind of this should be managed by Portainer, you should not have to tinker into that. :confused:
  2. Regarding the network : a bridge, as far as my limited knowledge allows me to understand, makes the container available on a subnetworks managed by the host. Some explainations can be found here. But that’s the default Docker behaviour. There should not be issues as long as you do not open ports on the host or create routing rules between your main network interface and the containers subnetwork.
  3. Yeah, that variable is most likely specific to Bookstack, it tells it to expect browsing with URL starting by that.
  4. For your guide: always use the proxy options (either public or private, that’s up to you). It will not work if you choose the 301 or 302 options. These two latter options will basically make Nginx tell your visitors to go to http://127.0.0.1:port or whatever. But that’s on their own computer, not your host. With the proxy options, it tells Nginx to fetch itself the http://127.0.0.1:port pages, which are indeed the container’s, and serve it to the visitors. So to summarize:
    • public_302 and public_301: not OK
    • public_proxy and private_proxy: OK
  5. Regarding the possibility to have a domain.com/path instead of app.domain.com: that’s up to how the app is made. You have to check the apps README to find out. For Bookstack, since it has a APP_URL variable (it can be named differently for other apps, it’s only a variable), I guess it is open to different paths.