Hi all,
I would like to clean up my SilverStripe before putting it into production. Actually the site is running SS 3.1.0-beta2, upgraded from a 3.0.3 as soon as new versions were published.
I have a lot of files that I think are not useful for a production site, for example here you are my root directory purged of installed modules:
######## DIRECTORY ########
assets
cms
framework
mysite
themes
tools <= *** USEFUL FOR PRODUCTION ?
vendor <= *** USEFUL FOR PRODUCTION ?
zzz_admin <= *** CAN BE MOVED ELSEWHERE ?
######## FILES ########
build.properties.default <= *** USEFUL FOR PRODUCTION ?
build.xml <= *** USEFUL FOR PRODUCTION ?
changelog-definitions.default <= *** USEFUL FOR PRODUCTION ?
composer.json <= *** USEFUL FOR PRODUCTION ?
composer.lock <= *** USEFUL FOR PRODUCTION ?
CONTRIBUTING.md <= *** USEFUL FOR PRODUCTION ?
dependent-modules.default <= *** USEFUL FOR PRODUCTION ?
favicon.ico
ignore.txt <= *** USEFUL FOR PRODUCTION ?
index.php
install-frameworkmissing.html <= *** USEFUL FOR PRODUCTION ?
Makefile <= *** USEFUL FOR PRODUCTION ?
phpunit.teamcity.mssql.xml <= *** USEFUL FOR PRODUCTION ?
phpunit.teamcity.postgresql.xml <= *** USEFUL FOR PRODUCTION ?
phpunit.teamcity.sqlite3.xml <= *** USEFUL FOR PRODUCTION ?
phpunit.teamcity.xml <= *** USEFUL FOR PRODUCTION ?
phpunit.xml.dist <= *** USEFUL FOR PRODUCTION ?
README.md <= *** USEFUL FOR PRODUCTION ?
robots.txt
web.config <= *** USEFUL FOR PRODUCTION ?
Is it safe to remove that files/directory?
I have the same problem into *cms* and *framework* directory, and maybe into others... It would be nice to have a script that clean all unnecessary files when going in production, because some of them can lead to information disclosure...
What do you think about that?
g4b0