There is a failure mode in composer where if it has a connection trying to get
a dependency tarball from the github API, it will fall-back to
downloading the entire repo for the dependency and use that... and it
will cache it outside of vendor/, using a whopping 1.5G of space
that full 1.5G is _then_ copied into vendor/
```
98M league
100M tecnickcom
133M laravel
323M sebastian
681M aws
```
for a total of a 1.8G vendor/ directory
vs the trimmed-down version with a 552M vendor/ directory
```
53M league
30M tecnickcom
31M laravel
70M sebastian
241M aws
```
This is still a far cry from the proper 150M version when everything
works as it should, but it's still a vast improvement
```
3.2M league
14M laravel
30M tecnickcom
260K sebastian
52M aws
```
Ideally this never happens, but it'd be great tp avoid the bloat if/when
it does..
To wit: Our ARM/Ubuntu Docker images are currently bloated because of this
issue due builds happening on an emulated ARM environment, and the resultant
performance penalties causing composer issues
All that to say, this change sets OMPOSER_CACHE_DIR to /dev/null to
avoid the caching, and then removes vendor/*/*/.git to remove that
needless bloat if it occurs. It's a no-op in general practice.
Fixes#12299, where currently there is no recursive permissions set on
/var/www/html/storage/ during build time. As a result this requires
users to run an exec into the container and change the permissions
before they are able to initiate the setup. Without this a 500 error is
thrown and little is evident in the docker logs as to what the issue
is.
Fixes#10176
The `column-statistics.cnf` file is copied to `/etc/mysql/conf.d/column-statistics.cnf` for each Dockerfile that exists.
This puts it as a system level mysql client change, so the web ui interface also works.
This image is built from the official Debian image as upstream, so there
is no need to do apt-get clean manually.
Ref:
- docs.docker.com/develop/develop-images/dockerfile_best-practices/#apt-get
> Official Debian and Ubuntu images automatically run apt-get clean, so
> explicit invocation is not required.
* docker: Rename /entrypoint.sh to /startup.sh
This script is not configured as the docker image ENTRYPOINT, thus it is
misleading to name it so.
* docker: Terminate supervisord if a process enters the FATAL state
By terminating PID 1, this will also terminate the Docker container.
* docker: Use supervisord to start up apache and cron
Note that this uses `apache2ctl -DFOREGROUND` rather than manually
sourcing /etc/apache2/envvars and running apache2, as recommended at
https://advancedweb.hu/2018/07/03/supervisor_docker/.
* docker: Add artisan schedule:run to crontab
This also switches to executing /var/www/html/artisan directly.
* docker: Run artisan schedule:run directly from supervisor
This has the following benefits over using cron:
- Cron doesn't need to be installed
- Docker-provided environment variables are preserved
- It's easy and explicit to run as the docker user
* updating with changes made to master
apply PR # 3456 to develop as well
* updating develop with changes made to master
apply PR # 3456 to develop as well
* updating paveit with passport-created oauth tables
