phpMyAdmin in Shinyproxy

I use MySQL database as a docker container. I would like to manage the database via phpMyAdmin image (phpmyadmin/phpmyadmin on Docker.hub). I can build a network and have these two components working together outside of Shinyproxy. But I’d like to put the phpMyAdmin app on the list of application when logging to Shinyproxy. I just don’t know what is the proper command to run the phpmyadmin container. This is what I have in application.yml:

  - name: dbapp
    display-name: MySQL application
    docker-cmd: ["R", "-e shiny::runApp('/data')"]
    docker-image: dbapp
    docker-network-connections: ["db-network"]
    docker-env-file: db.env
    groups: admin
  - name: phpmyadmin
    display-name: phpmyadmin
    docker-cmd: [ "/", "supervisord", "-n" ]
    docker-image: phpmyadmin/phpmyadmin
    docker-network-connections: ["db-network"]
    groups: admin

Networking is done by ‘db-network’, the network used by the database container. The first application is just for testing if all is working properly. It is. I just don’t know what docker-cmd I should use for phpmyadmin application.

Can anyone help me with this?

Hi @Jakub_Malecki,

What you intend should definitely be possible (we have used it for other types of database). This is the configuration I would use (untested):

  - id: dbapp
    display-name: MySQL application
    container-cmd: ["R", "-e shiny::runApp('/data')"]
    container-image: dbapp
    container-network: ["db-network"]
    container-env-file: db.env
    access-groups: admin
  - id: phpmyadmin
    display-name: phpmyadmin
    container-cmd: [ "/", "supervisord", "-n" ]
    container-image: phpmyadmin/phpmyadmin
    port: 80
    container-network: ["db-network"]
    access-groups: admin

A few remarks:

  • I have updated all configuration to the 2.x.y conventions (container-*)
  • I have corrected network specification using container-network
  • the phpMyAdmin server will listen on port 80 by default, so I specified it using port

It may be best to move to ShinyProxy 2.0.2 (released earlier today).

Hope this helps!