The recent problems (see #150) with deploying the rebuilt site stem from the fact that the rendering was run within the Docker container under the default (root) user. On Linux (the environment under which we run at Circle) this means the rendering products are then owned by root, which can't be deleted outside of the container by the user under which the integration tests run.
This changes this to the rendering running under the same uid and gid as the user running the build does. As a result, any files newly created should be deletable by the host user outside of the container.
To form a complete changeset for testing, this also needs to remove the superfluous bootstrap and jQuery libraries, so I have included #151 here.
The recent problems (see #150) with deploying the rebuilt site stem from the fact that the rendering was run within the Docker container under the default (root) user. On Linux (the environment under which we run at Circle) this means the rendering products are then owned by root, which can't be deleted outside of the container by the user under which the integration tests run.
This changes this to the rendering running under the same uid and gid as the user running the build does. As a result, any files newly created should be deletable by the host user outside of the container.
To form a complete changeset for testing, this also needs to remove the superfluous bootstrap and jQuery libraries, so I have included #151 here.