You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of scanning all the GET routes available in the app without parameters to crawl the pages,
allow to provide a single entrypoint URL from where to start crawling the pages.
building multiples, distinct sections of a single Symfony app into multiple dedicated static builds
naturally ignore some of the existing GET routes that are not meant to be included in the static build
Additionnal needs:
we might need a way to register some additional routes that are not referenced on any page, but should still be included.
➜ To solve such a need, we currently can register a listener on the stenope:build command to add such routes, as we do for member signatures pages on our elao website: https://github.com/Elao/elao_/blob/master/src/Stenope/Listener/BuildListener.php
But we might need a more official way and allow the user to choose if it should be included or not according to the entrypoint. ➜ Simply create a dedicated event where one could access the entrypoint and add routes to the collection?
One could also simply rely on an env var as a flag when calling the build command.
The text was updated successfully, but these errors were encountered:
Instead of scanning all the GET routes available in the app without parameters to crawl the pages,
allow to provide a single entrypoint URL from where to start crawling the pages.
This would allow:
Additionnal needs:
➜ To solve such a need, we currently can register a listener on the
stenope:build
command to add such routes, as we do for member signatures pages on our elao website: https://github.com/Elao/elao_/blob/master/src/Stenope/Listener/BuildListener.phpBut we might need a more official way and allow the user to choose if it should be included or not according to the entrypoint. ➜ Simply create a dedicated event where one could access the entrypoint and add routes to the collection?
One could also simply rely on an env var as a flag when calling the build command.
The text was updated successfully, but these errors were encountered: