Currently it uses datalad branded favicon, which should be the default. But a custom one is also useful. It can be specified in the same way as the custom logo via config.json, e.g. with the favicon_path field:
and we would need to double check whether all are necessary or used, and in which contexts. It could be sufficient for users to perhaps only supply a .ico file, so the code that copies the supplied custom favicon will have to do either expect specific files or have some logic to put files in the right place and/or rename as necessary.
Currently it uses datalad branded favicon, which should be the default. But a custom one is also useful. It can be specified in the same way as the custom logo via
config.json, e.g. with thefavicon_pathfield:the current favicon files include:
and we would need to double check whether all are necessary or used, and in which contexts. It could be sufficient for users to perhaps only supply a
.icofile, so the code that copies the supplied custom favicon will have to do either expect specific files or have some logic to put files in the right place and/or rename as necessary.