Support to change the output folder when generating static files

[ramsesmoreno]

Sometimes you need the static files to be generated in a folder different from public/docs, so I added a config parameter to change it.

[rahulhaque]

@ramsesmoreno Won't this break the /docs route? If you really want to access the static files from - suppose the root directory of your project, you can make symbolic link or junction for that.

[ramsesmoreno]

Hi, thank you for check this.

Is the docs route also used when using the static generation? My change only affects that. My intention was to be able to generate the doc outside the public folder because, for example, I don't want the documentation to be public.

I'll make some tests and let you know.

[shalvah]

@ramsesmoreno Won't this break the /docs route? If you really want to access the static files from - suppose the root directory of your project, you can make symbolic link or junction for that.

You shouldn't be using routing for static generation. For static generation, just open the HTML file in your browser and you're good.

[shalvah]

Note that the structure of this config file will be changed somewhat in the upcoming v5.

[rahulhaque]

@ramsesmoreno Won't this break the /docs route? If you really want to access the static files from - suppose the root directory of your project, you can make symbolic link or junction for that.

You shouldn't be using routing for static generation. For static generation, just open the HTML file in your browser and you're good.

Now I see, my server is configured to run index.* file by default and that's why I can access the /docs route to serve documentation. Thank you for clearing that up.