Message of the day:
SS 4.4.0-RC1 is out. Changelog: https://github.com/silverstripe/silverstripe-framework/blob/4.4/docs/en/04_Changelogs/4.4.0.md
SilverStripe 4 related information and questions.
What's the 'recommended' way to deal with such things? Have composer on the server?
It's an interesting issue. I do all my dev work locally in docker containers and then push to the relevant server by whatever means. Quite often, this is via (S)FTP onto a client box. I can see headaches in the future
that could potentially present outdated public files when you update modules
hmm, there's an option to copy the public files instead of creating a symlink - I need to look up how to do that
I'm just wondering how someone who needs to upload via (S)FTP will cope
So will there be a zip download of SS4 in the future? Presumably not?
because the modules now live in the vendor folder, the public files they offer aren't accessible without the symlinks
the symlinks are created when you
composer require/install/update a package
Does the installer create the symlinks usually?
unless you ~miraculously~ somehow kept the project root the same on your computer and the web server