forked from ReviveNetwork/ASP
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Single image containing nginx
and php
#69
Comments
leojonathanoh
added a commit
that referenced
this issue
Nov 7, 2023
…P` and `bf2sclone` with env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` and `bf2sclone` containers - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 7, 2023
…P` with env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` and `bf2sclone` containers - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 7, 2023
…P` with env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 7, 2023
…P` with env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 22, 2023
…th env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 22, 2023
…th env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 22, 2023
…th env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 22, 2023
…th env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
leojonathanoh
added a commit
that referenced
this issue
Nov 22, 2023
…th env var support for configuration In <= v3.2.0, `asp` had separate `nginx` and `php` images. Now: `asp` image containing both `nginx` and `php`, with environment variable support, and entrypoint that sets the correct permissions. Benefits: - Easier to deploy / upgrade. No need to separate `nginx` and `php` containers - Environment variable configuration means no more need to mount config into `asp` container - Entrypoint script sets permissions on volumes. `init-container` should only need to set permissions for `db` volume Notable changes: - Add documentation for upgrading docker images to v3.3.x from prior versions - Update `./docs/examples` - Add tests for production builds for examples in `./docs/examples` Closes #69
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current
Separate
nginx
andphp
imagesExpectation
Single image containing
nginx
andphp
.Discussion
Currently the
nginx
andphp
are in separate images.Benefits:
Drawbacks:
nginx.conf
config file requires hostname ofphp
, which means that either: 1) nginx container may require an env variable likePHP_HOSTNAME
which overrides a value innginx.conf
(which is not conventional and difficult to understand), or 2) user needs to use a customnginx.conf
. Instead, if they were in the same container,127.0.0.1
may simply be used.The text was updated successfully, but these errors were encountered: