Skip to content
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

Flow Default Routes never included in basic flow installation #868

Open
kitsunet opened this issue Feb 12, 2017 · 4 comments

Comments

@kitsunet
Copy link
Member

commented Feb 12, 2017

We removed the default Routes.yaml but also don't include routes via Settings so that a Flow installation is without routes, breaking existing documentation and tutorials.

@bwaidelich

This comment has been minimized.

Copy link
Member

commented Feb 14, 2017

FYI: The default Routes.yaml has been removed with #790 in order to promote Settings-based routes.
The Settings.yaml.example has been adjusted accordingly so new installations should work out of the box.
Do you have an idea on how to improve the situation for upgrades (apart from still missing upgrade instructions)?

@kitsunet

This comment has been minimized.

Copy link
Member Author

commented Feb 14, 2017

I remember we even discussed this, I think I just forgot. For some reason we decided against adding this setting to the default Flow Settings.yaml, right?

We at least need to adjust documentation and tutorials so that people that rely on those fallback rules know what to do.

@bwaidelich

This comment has been minimized.

Copy link
Member

commented Feb 14, 2017

For some reason we decided against adding this setting to the default Flow Settings.yaml, right?

Yes, we decided to do that for the Neos Routes though.

We at least need to adjust documentation and tutorials

Fresh installations should be fine (if they copy the example Settings file). But, yes, it could be mentioned explicitly. And we urgently need upgrade instructions for Neos 3.0/Flow 4.0..

@kdambekalns

This comment has been minimized.

Copy link
Member

commented Mar 28, 2017

Solution: Upgrade the upgrade instructions & tutorial / setup / install documentation as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
You can’t perform that action at this time.