![]() If you look at the images on your box you will notice an image called: local_discourse/app (derived from your yml file name), this image can be pushed to your own registry, composed using Docker compose and so on. Launcher reflects this.Īt the end of the day … launcher and Docker Compose are compatible, you can generate the base images you want using launcher and bring up your environment using compose. You can run Discourse as a single “fat” container including pg/redis and the web, you can also run Discourse in multiple containers using launcher keeping db and redis in other containers. Our installation process was always meant to be “philosophy” agnostic. We provide utilities like “cleanup” that allow you to clean up old orphan docker images Unlike Docker compose, Launcher only deal with configuration of a single container ![]() We allow rich semantics with generation of base images, this allows you to mixin support similar to the closed INCLUDE proposal for Docker. We provide lightweight wrappers on top of docker exec, docker start, docker stop and docker rm, these wrappers ensure containers are launched with the correct configuration, automatically restart and so on We have a series of pre-req tests that ensure a system is up to the task of running Discourse (enough memory / disk space and so on) Launcher is a tool used for a wide variety of processes many of which have no parity with Docker Compose It allows simple generation of base images from Dockerfiles (provided they are not local) ![]() It allows you to “define” environments, bring them up and tear them down. This question if far more complicated, so let me start here Compose and launcher operate at different levelsĬompose is a tool used for multi image orchestration. The question is somewhat misguided, but I would like to address a broader one ofĬan Discourse ship frequent Docker images that do not need to be bootstrapped? Overview of Docker Compose | Docker Documentation To define multiple containers (redis, postgres, discourse,…), links and volumes, docker-compose should be used instead. There is this open issue (which I just closed) on Discourse Docker repo askingĭiscourse should behave like a standard docker imageĪ docker user excepts to be able to run discourse without a special launcher.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |