← Back to context

Comment by oesa

10 days ago

https://trailer.dev, a self-hostable development environment platform.

Been working on it on and off for 4 years now. I used to lead an ML consultancy and one thing I've learned is that data scientist DO NOT understand reverse proxies, nvidia drivers, docker and can not set up complex environments for their projects, especially ones that would support collaborative work.

It's been really fun to work on this, currently working on Kubernetes support.

3 comments

oesa

Reply
skreem  10 days ago

Oh this is awesome, will take a look. I’ve had rough experiences with Kubeflow in the past, recently I’ve been using Coder workspaces https://coder.com/ and it’s pretty good but less ML/AI integrated (but, stitched together with Ray autoscaling nodes it can get really nice)

  • oesa  10 days ago

    Yeah, Kubeflow can be rough, we've been down that road too as well.

    I really like Coder, but one thing for the life of me I couldn't figure out is that even with the self-hosted version, why does anything have to go through their infra?

    With trailer.dev our explicit goal is to have a fulfilling user experience for the following scenario:

      - You have servers you own or rent

  - You have a team that want some persistent developer workspaces that are running on that server

  - You run our 30mb + the server side somewhere and boom, you can have your team(s) work on your project.

    If you want we (the trailer team) can run the server component for you, but that's it.

    I tried spinning up a coder instance just now again, with docker, and I'm being tunneled through US East Pittsburgh with 117ms of latency for a local dev environment tool :(

    • skreem  9 days ago

      Oh interesting… I don’t manage it, but one of our teams does fully self host it

      Have you tried setting CODER_ACCESS_URL to your own hostnamE/IP? I think that disables the tunnel setup