Installing Symfony 3 on Synology has some tricky bits to make it run. This post essentially addresses the fatal errors when trying to write cache or logs, which is a common issue that has some documented solutions at Symfony’s site – and issue being that ACL permissions cannot be changed as those instructions suggest.
Synology’s DSM has a builtin tool for this: synoacltool (use synoacltool -h for help).
Terminal / SSH:
To make this run on your development server follow these steps for each affected directory (e.g. logs):
sudo rm -r logs/
sudo mkdir logs
sudo synoacltool -set-owner logs/ user http
sudo synoacltool -enforce-inherit logs/
In my case I had to do this for the logs, cache and sessions folders on my app’s folders.
GUI (should work):
This should do it!
If you have a Synology DiskStation and you have shared your public NAS link on…
Ubuntu initial setup does not do expand the virtual disk image to it's full size.…
A common issue that appeared with DSM 7 is that some well known containers started…
The Windows Sandbox image is useful for many test setups, but it lacks much of…
If you're used to Snip & Sketch for adding some scribbles placed over desktop screenshots,…
On some occasions Microsoft 365 Office applications might open a popup with "Contacting server for…