Feature Request: Published Docker Image

[DellanX]

Feature Request: Published Docker Image

[ramunasd]

Hi @DellanX , it would be nice to review Your proposal how to build image. Can You submit a PR? Very likely I will follow it to build real image.

[DellanX]

I think it'd just be one of the following:

1. A PHP/Ubuntu/Alpine based docker image that can be inserted into another docker-compose easily.
   This would be just like adding phpmyadmin or similar to a docker-compose file.
2. Adding a stage to the current docker image that runs the composer install command behind the scenes.
   This option would require the consuming developer to use something such as a nginx instance to handle the trafic, as your current docker-compose is setup.

Ideally we can go with route (1). I'll tinker around with it, and submit a PR. The furthermost ideal would be to have a multi-stage dockerfile that defaults to (2) for a creates first a small image, but also (1) for developers who don't have a nginx instance.

classDiagram
class Developer1DockerContainer {
devImageA
devImageB
satis
}
class Developer2DockerContainer {
devImageA
devImageB
nginx
satis
}

Loading

services:
  satis:
    image: satisfy/satisfy # OR stasify/lite for developers who have a NGINX service
    networks:
      - developmentNetwork
    environment:
      APP_ENV: ${APP_ENV:-dev}
      APP_DEBUG: ${APP_DEBUG:-1}
      APP_PATH: /var/www/satisfy
    volumes:
      - .:/var/www/satisfy
      - /var/www/.composer
    restart: always
    ports:
      - "${APP_PORT:-8000}:80"

I'll look into making above, may take me a few weeks as I have a lot going on at the moment.

[ramunasd]

Hi @DellanX , can You check PR #190
I hope this is something we can start on.

[ramunasd]

First precompiled docker image released.