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
Ability to use the https://hardcore-saha2.try.coder.app domains (including wildcards for dev URLs) without the in-memory DB. Currently, you have to use coder start --dev which is not suited for production use
For example:
CODER_PG_CONNECTION_URL=postgresql://... coder start --tunnel
▄█▀ ▀█▄
▄▄ ▀▀▀ █▌ ██▀▀█▄ ▐█
▄▄██▀▀█▄▄▄ ██ ██ █▀▀█ ▐█▀▀██ ▄█▀▀█ █▀▀
█▌ ▄▌ ▐█ █▌ ▀█▄▄▄█▌ █ █ ▐█ ██ ██▀▀ █
██████▀▄█ ▀▀▀▀ ▀▀▀▀ ▀▀▀▀▀ ▀▀▀▀ ▀
coder_1 |> Started in production mode. All data is stored in the
coder_1 | PostgreSQL provided! Press ctrl+c to gracefully
coder_1 | shutdown.
coder_1 |
coder_1 |> Run coder login access-url: https://hardcore-saha2.try.coder.app in a new
coder_1 | terminal to get started.
Why do you want this feature?
This would be great to deploy Coder without owning a domain.
Are there any workarounds to get this functionality today?
I'm not sure I really want this to be a valid use case. Maintenance of the proxy is best effort, and there's no way to reserve names. Every time you restart coderd you get a new URL.
Well I would like this. We could ask people to give a DNS, probably from DuckDNS, then authorize it and then save it as a stored variable. It would be read every time coderd starts so you could have fixed URLs.
Well I would like this. We could ask people to give a DNS, probably from DuckDNS, then authorize it and then save it as a stored variable. It would be read every time coderd starts so you could have fixed URLs.
All you could do is give the proxy DNS on the first prod run and then just start as usual if it ends. It can give a call to the stored string variable that has the DNS name and then get the value for the DNS part. You can try adding a flag for that to happen.
DDNS is something better implemented outside of our development proxy. It's not geo-distributed or highly-available, and we don't monitor it as a production instance. I'd recommend using ngrok or similar for production deployments if reverse tunnels are necessary.
We need to revisit this for a smooth install experience. Here's the criteria for the README-suggested install:
It's local: no one wants to set up a cloud VM just to try a cool github thingy
No Postgres required: for most, this adds a few minutes of googling and will be a major source of drop off
It's persistent: users will be pissed off if their resources disappear because they restart the application
Some options:
SQLite
Add ngrok to docker-compose path
Allow coder.app in docker-compose installs
We should revisit the SQLite issue as well #1417 but @coadler@bpmct what do you think about reconsidering this item? Is there a way we could handle this that also mitigates the concerns you surfaced?
I think there can still be a warning that the tunnel isn't "prod ready", but still works with sqllite or postgres to persist data. As long as that works, option 3 is possible. SQLite support with the tunnel naturally allows 3 to work too.
Unsure how ngrok would work. Their free plan is very limiting, but if there is a way to pass the ngrok URL as an access URL, I'm game as well
Some offline discussion earlier suggested that SQLite may be too hard to use to maintain compatibility, at least given the way our database layer is designed right now and potential future features we want to implement.
Activity
[-]Feat: use coder tunnel without `--dev`[/-][+]Feat: use coder tunnel in production[/+]coadler commentedon Apr 25, 2022
I'm not sure I really want this to be a valid use case. Maintenance of the proxy is best effort, and there's no way to reserve names. Every time you restart
coderdyou get a new URL.bpmct commentedon Apr 26, 2022
That makes sense, I figured I'd ask. 👍🏼
tjcran commentedon May 7, 2022
Closing this issue until we have evidence this is a use-case people would want.
im-coder-lg commentedon May 8, 2022
Well I would like this. We could ask people to give a DNS, probably from DuckDNS, then authorize it and then save it as a stored variable. It would be read every time coderd starts so you could have fixed URLs.
tjcran commentedon May 9, 2022
@coadler what do you think of this idea?
im-coder-lg commentedon May 9, 2022
All you could do is give the proxy DNS on the first prod run and then just start as usual if it ends. It can give a call to the stored string variable that has the DNS name and then get the value for the DNS part. You can try adding a flag for that to happen.
coadler commentedon May 9, 2022
DDNS is something better implemented outside of our development proxy. It's not geo-distributed or highly-available, and we don't monitor it as a production instance. I'd recommend using ngrok or similar for production deployments if reverse tunnels are necessary.
4 remaining items
tjcran commentedon May 24, 2022
We should revisit the SQLite issue as well #1417 but @coadler @bpmct what do you think about reconsidering this item? Is there a way we could handle this that also mitigates the concerns you surfaced?
bpmct commentedon May 24, 2022
I think there can still be a warning that the tunnel isn't "prod ready", but still works with sqllite or postgres to persist data. As long as that works, option 3 is possible. SQLite support with the tunnel naturally allows 3 to work too.
Unsure how ngrok would work. Their free plan is very limiting, but if there is a way to pass the ngrok URL as an access URL, I'm game as well
ammario commentedon May 25, 2022
@kylecarbs seems to have all the technical context on the solution space so he'll follow up here...
tjcran commentedon May 25, 2022
Assigning @kylecarbs for now just so we don't lose track of this one
ketang commentedon May 25, 2022
Some offline discussion earlier suggested that SQLite may be too hard to use to maintain compatibility, at least given the way our database layer is designed right now and potential future features we want to implement.
coadler commentedon May 26, 2022
I'm currently looking into making a more production grade proxy.
[-]Feat: use coder tunnel in production[/-][+]Use coder tunnel in production[/+]bpmct commentedon Jul 22, 2022
This was done