syntro-opensource/ansible.silverstripe

Ansible role to deploy silverstripe

ansible.silverstripe's Issues

add the possibility to add things to the .htaccess file

currently, we render a simple .htaccess file containing just the bare minimum necessary to run silverstripe. In practice however, more things might be needed in order to run a performant and flexible app/website.

The resource directory does not include root dependencies if no public directory is present

vendor directories are correctly exposed in every case. however, theme directories and local resources asre only exposed via resource directory if a public/ directory is present. This poses problems for projects which do not come with a public directory and are developed around not having one.

We need to find a way to patch this issue, as it basically means that in order to use this role, a project needs to be refactored to use a public/ directory.

The decision wether to expose a directory is made via https://github.com/silverstripe/vendor-plugin/blob/0705b1944e5e9b55fe62c3d417143da560698e7f/src/Library.php#L187.

For themes, all we need to do would be to basically render and move a link to the themes/ directory if it exists and no public/ directory exists. In the case of other directories, things get more complicated. While we could read the composer.json file and extract the extra.expose key, this means we would have to build a directory-structure similar to the one in the ressouces dir, and this would make a downtimeless deploy much harder.

Ill leave this issue here as a starting point, as we are currently only working with public installations and syntro/ssto contains one by default.

Bug: if the playbook fails, the lockfile does not get deleted

The handler which should delete the lockfile does not get called