lullabot / tugboat-registry Goto Github PK

http://wp-cli.org

I noticed during amp install and bravo install having to apt-get install vim as I can't use vi very well. Can we add this to the default container?

Due to the nature of the underlying filesystem and networking, Tugboat doesn't support official Docker images. VOLUME doesn't work, since by mounting a volume, we lose the availability to clone the data in the volume for Base Previews, and also would blow up disk usage for our cluster. Docker doesn't yet support a method to reset the VOLUME command (see moby/moby#3465).

It's not ideal that Tugboat can't use the official images:

1. We need to maintain our own images—can't rely on community support
2. We may miss critical security updates
3. Deconstructing existing Dockerfiles into Tugboat-compatible ones can be tedious, and when things don't work, difficult to debug.
4. For projects that are already using Docker (for local development or even production hosting), we can't use existing images, resulting in "it works on my machine!" syndrome.

Let's use this issue to:

1. Begin documenting how to best write images for Tugboat as it exists today (things to do / avoid)
2. Discuss the technical hurdles, and brainstorm a world where Tugboat could work with official images in some capacity
3. Note any discovered workarounds

The latest set of images does not allow overrides from .htaccess

It'd be nice on our webheads to install drush with composer global require drush/drush. That way if you want to switch versions, it's a known format.

We often recommend cleaning up the apt, dpkg, /tmp dirs prior to commit, as that reduces the disk size of the Tugboat service. Rather than having this be a step that our users have to remember to perform, it makes sense for Tugboat to handle this directly.