-
-
Notifications
You must be signed in to change notification settings - Fork 835
Make specific access on dev environment optional #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
It is not straightforward for newcomers. You cannot start coding without Uncommenting those lines... |
Why? It's quite the opposite! Most of the time, even if you have exported |
It works on Linux and Mac but it seems to not work as expected on Windows. |
Can you just update this PR to remove this block totally as I've done in the framework bundle's recipe? Thanks Mickaël! |
Yes Kevin, I'll do it probably tonight :) Mickaël |
ae5308f
to
7f900dd
Compare
Done (sorry for the delay) and thank you to have done it at Symfony's level :) |
In fact, you can just remove the |
Yeah, I wanted to ask you why we keep the web folder :D I do it now sir :) Do I have to update the docker-compose configuration too? I'm worried about theses lines:
I don't know well Flex, will it create a new |
Yes it will. No problem for this line. |
Thanks @mickaelandrieu! |
Make specific access on dev environment optional
Why? Because as you now have only one front controller, it is always deployed in production :)
By default, this part should be now disabled and let advanced users write every custom action they need to do instead of force every Symfony developer to remove this damn piece of code every time on every project.
And don't tell me it's insecure: it's really hard to make
APP_DEBUG
env variable in production by mistake 👍