As a workaround, copying the icons and manifest from public to domain root seems to work (with Wekan snap running behind Apache here). As the files have a wekan- prefix, collisions shouldn’t be an issue. Naturally, this solution does require write access to the domain root directory.
Replace instruction using
ln -s to enable Apache site to use
a2ensite instead in Debian and derivatives. Closes #884.
Under Apache Web server configuration, there’s a prompt to create a symlink to enable the newly created site:
ln -s /etc/apache2/sites-available/nextcloud.conf /etc/apache2/sites-enabled/nextcloud.conf
As the instructions in this section are written for Debian, Ubuntu, and their derivatives,
a2ensite should be used instead:
The commands are currently functionally equivalent (AFAIK), but should this change sometime, the latter would be more future proof, besides being much shorter and easier to type.
Additionally, immediately following the
ln -s there is a section about Additional Apache configurations, which correctly instructs the use of
a2enmod to create the symlinks. Replacing
ln -s with
a2ensitewould thus harmonize the two sections.
With Gitlab 9.5.4-ce.0 and Apache 2.4.18, I had to set `DirectoryIndex disabled` for the Gitlab directory (in the vhost configuration) to fix this when using RewriteRules. (I’ve now switched to using ProxyPass instead.)
Forgot to mention that my installation is served over https too, on Apache. But for me there are no SSL errors to be seen either.