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
Can you try favicon-path: favicon.png? I glanced at one of our config files which used a similar Dockerfile.
Depending on your setup, you can run your applications with app_direct/ (no iframe) instead of app/ (iframe) and then add the favicon to the Shiny application's head section. Of course, the login page of ShinyProxy would still have a favicon that needs to be customised then.
when I use app_direct/my_app for direct access to shiny app without iframe I should add tags$head(tags$link(rel = "icon", type = "image/png", href = "favicon.png")) to shiny app. It's work!
when I use custom login template, I should add <link rel="shortcut icon" href="/assets/img/favicon.png" type="image/png"> to login.html file.
FYI
There is some info about login page modification #148
Hello!
I can't add favicon.png when ShinyProxy is running as docker container.
Dockerfile:
`FROM openjdk:8-jre
RUN mkdir -p /opt/shinyproxy/
RUN wget https://www.shinyproxy.io/downloads/shinyproxy-2.3.0.jar -O /opt/shinyproxy/shinyproxy.jar
COPY application.yml /opt/shinyproxy/application.yml
RUN mkdir /opt/shinyproxy/templates
ADD templates /opt/shinyproxy/templates
ADD favicon.png /opt/shinyproxy/favicon.png
WORKDIR /opt/shinyproxy/
CMD ["java", "-jar", "/opt/shinyproxy/shinyproxy.jar"]`
And application yml:
`spring:
servlet:
multipart:
max-file-size: 300MB
max-request-size: 300MB
proxy:
title: Myapp
template-path: ./templates/1col
favicon-path: /opt/shinyproxy/favicon.png
logo-url: http://www.openanalytics.eu/sites/www.openanalytics.eu/themes/oa/logo.png
landing-page: /
port: 8080
authentication: webservice
webservice:
authentication-url: http://127.0.0.1:9010/api/auth/check
authentication-request-body: "{email: '%s', password: '%s'}"
hide-navbar: true
admin-groups: admins
container-backend: docker
docker:
internal-networking: true
container-memory-limit: 400m
specs:
display-name: Hello Application
description: Application which demonstrates the basics of a Shiny app
container-cmd: ["R", "-e", "shinyproxy::run_01_hello()"]
container-image: openanalytics/shinyproxy-demo
container-network: amrcloud-net
container-cmd: ["R", "-e", "shinyproxy::run_06_tabsets()"]
container-image: openanalytics/shinyproxy-demo
container-network: amrcloud-net
logging:
file:
shinyproxy.log`
Maybe something is wrong with configuration files?
The text was updated successfully, but these errors were encountered: