Replies: 2 comments 1 reply
-
code-server also has `/absproxy` which passes the request as-is so
`/absproxy/8000/` instead might do the trick here.
We currently have no way of choosing which proxy to use in the
ports panel but it would be nice to add some kind of toggle in the
future.
For now you could manually change this by setting an environment
variable, for example:
```
docker run --env 'VSCODE_PROXY_URI=https://domain.tld/absproxy/{{port}}/' codercom/code-server
# Or use the more dynamic form //{{host}}/absproxy/{{port}}/
```
Or you could of course manually type/change the URL.
If you can get a wildcard certificate for your domain another idea
is to use the subdomain proxy which circumvents all the issues
with path-based routing.
Lastly, I have seen mention of a method for configuring Django to
work behind a rewriting reverse proxy; looks like you would have
to set `FORCE_SCRIPT_NAME = /proxy/8000/` in `settings.py` but I
have not tested that myself.
|
Beta Was this translation helpful? Give feedback.
1 reply
-
Anyone found a way to get Django working? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thank you so much for this project.
I have been trying to get Django to work with a Docker image for code-server from linuxserver.io. Everything works great so far except for static files. Code-server serves the Django app with a suffix /proxy/8000/. I have looked at the documentation and it says that code-server strips /proxy/ from the request path. This is true only for static files but is not ideal for the django development server. Static files are reachable when the suffix is added. I would really appreciate help setting up serving static files with a prefix /proxy/8000/ or any other suggestion
Many thanks!
Beta Was this translation helpful? Give feedback.
All reactions