Overview: Support for Docker image arch-rider in the binhex repo.

Application: Rider- https://www.jetbrains.com/rider/

Docker Hub: https://hub.docker.com/r/binhex/arch-rider/

GitHub: https://github.com/binhex/arch-rider

Documentation: https://github.com/binhex/documentation

 

Note:- This application requires a licence, otherwise it will run in Evaluation Mode for 30 days.
 

If you appreciate my work, then please consider buying me a beer

 

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

Edited May 9, 20197 yr by binhex

reserved.

Hey @binhex,

 

As usual for your containers, it all seems to be working swimmingly! I did want to ask though, if you had dabbled at all in adding the container to nginx and/or through organizr. I seem to be able to get to a noVNC error page once I get it added to the config files, but can't get it to the interface itself. 

This is obviously stretching to the point of possible irrelevancy for this thread, but, wanted to ask, just in case!

 

Thanks!

 

# RIDER reverse proxy
location /rider {
        proxy_pass http://192.168.86.63:6080/vnc.html?resize=remote&host=192.168.86.63&port=6080&autoconnect=1;
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        index vnc.html;
        alias /path/to/noVNC/;
        try_files $uri $uri/ /vnc.html;
}

 

14 hours ago, omninewb said:

I did want to ask though, if you had dabbled at all in adding the container to nginx and/or through organizr.

sorry, i have literally zero experience with reverse proxy stuff, you are probably best asking over on the support thread for nginx/organizr and see if they have any suggestions.

It's all good man, like I said, the docker itself is running perfectly and I have no issues at all, just looking to expand functionality a bit through that remote access.

 

Thanks for another great product!

On 1/7/2019 at 8:16 AM, omninewb said:

It's all good man, like I said, the docker itself is running perfectly and I have no issues at all, just looking to expand functionality a bit through that remote access.

 

Thanks for another great product!

Is your Rider config inside the default config of letsencrypt? or are you using something else? I don't use Rider but when I created my Seafile config for letsencrypt and nginx I had to create a separate config file just for Seafile and setup my proxy as seafile.DomainName.com. You should be able to reverse proxy any docker container although it may take more tweaking for Rider. I have Pycharm and if I get that to reverse proxy it should be similar, I will let you know.

10 hours ago, ucliker said:

if I get that to reverse proxy it should be similar, I will let you know.

please post the solution here if you do get it work, as this information could/should be able to be applied to all other novnc based images i have produced.

On 1/16/2019 at 3:57 PM, ucliker said:

Is your Rider config inside the default config of letsencrypt? or are you using something else? I don't use Rider but when I created my Seafile config for letsencrypt and nginx I had to create a separate config file just for Seafile and setup my proxy as seafile.DomainName.com. You should be able to reverse proxy any docker container although it may take more tweaking for Rider. I have Pycharm and if I get that to reverse proxy it should be similar, I will let you know.

I appreciate you letting me know, and I had tried a bunch of different setups in my attempts to get it routed through, the closest I got was in my setup up above, posted again here for posterity: 

In my default config: 

location /rider {
auth_request /auth-1;
include /config/nginx/proxy-confs/rider.conf;
}

and in the rider.conf:

# RIDER reverse proxy
location /rider {
        proxy_pass http://192.168.86.63:6080/vnc.html?resize=remote&host=192.168.86.63&port=6080&autoconnect=1;
        proxy_set_header Host $http_host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        index vnc.html;
        alias /path/to/noVNC/;
        try_files $uri $uri/ /vnc.html;
}

with the result being that noVNC error page. It's definitely connecting to the docker image, just not connecting all the way through the noVNC portion, some nginx pass-through setting somethingorother I assume but don't pretend to understand, ha!

I got it working with letsencrypt with the following: (subdomain)

# make sure that your dns has a cname set for code-server

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name rider.*;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_rider binhex-rider;
        proxy_pass http://$upstream_rider:6080/vnc.html?resize=remote&autoconnect=1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection upgrade;
    }
}

set $upstream_rider binhex-rider;  =  binhex-rider is the name of the Docker cointainer

after that I had to delete cache and hard reload in Chrome and it worked.

Thanks binhex for this docker