The web resources folder exposes a public url for files contained within, however any files contained within sub-folders are not made public
ie.
$SEARCH_HOME/conf/collection/my-collection/_default/web/style.css === public
$SEARCH_HOME/conf/collection/my-collection/_default/web/styles/style.css !== public
Is there a method to change the server settings to expose sub-folders to a public url?
Hi @vmanera -
Are you finding that the web resources in sub-folders are not accessible via a web browser? The Admin UI doesn’t expose sub-folders in the File Manager, but if you’re placing resources in sub-folders from the command line, they should still be available via the web browser (v12.x+) at URL locations like:
https://SEARCH-SERVER/s/resources/COLLECTION/PROFILE/subfolder/style.css
While they are accessible in a browser, it appears those sub folders do not get public permissions, attempting to access these assets brings up a modal window to login. What i’m looking to do is apply the same ‘public read’ level of permissions down folders and assets deeper under this folder.
Hi Vincent,
How did you create those sub-folders? If you are logged in on the linux shell you should make sure you are the correct user (ie. search) when you create the folders, or that you set the permissions correctly (you want to make sure that these folders are owned by the search user (or the user that Funnelback is running as if you’ve changed this from the default), with any files within having read/write permissions by the same search user.
cheers,
Peter