Today, you need to follow complicate (and outdated) documentation to finally having some kind of development environment. By development, I mean somethings were you don't need to do a drush cr every time you modify you CSS or twig template.
Just before peoples say "no this is perfect right now", this is the steps you have to follow now:
- in settings.php uncomment
# if (file_exists($app_root . '/' . $site_path . '/settings.local.php')) {
# include $app_root . '/' . $site_path . '/settings.local.php';
# }
- rename example.settings.local.php in settings.local.php
- move settings.local.php in /sites/default
- in development.service.yml add
parameters:
twig.config:
debug: true
auto_reload: true
cache: true
- pray... refresh.. clear cache..
This can be drastically simplified and works out of the box.
One solution would be to have two front controllers like in symfony. Something like index.php dev.php . If you load dev.php you get to load dev settings and services.
I think we need to think first of newbie and themer. Peoples that don't care about multi-site and the name of all Drupal's cache layer.
Comments
Comment #11
JohanKleene CreditAttribution: JohanKleene at iO commentedAlthough this would be a nice feature to have, I would not consider this a bug. Rather a feature request, so changing to feature request.