3 ms·
I guess this makes sense if you already know what Gitpod does? It seems to be some kind of shortcut for opening a terminal in a browser.
by skybrian 4y ago
I guess this makes sense if you already know what Gitpod does? It seems to be some kind of shortcut for opening a terminal in a browser.
- rgoulter 4y agoTraditionally, I'd think of setting up my developer machine as spending a day or so to install all the programs I need to work on whatever projects. Services like GitPod are about serving a development environment remotely. The blogposts discusses dotfiles as a social thing. e.g. you should be able to fork someone's dotfiles repository as a good starting point for your dotfiles. The idea in the blogpost is a suggestion which combines this idea of sharing dotfiles, with the idea of being able to quickly spin up a developer environment.
- capableweb 4y agoBypassing the whole set of issues that "having a development environment remotely" introduced (isn't that just "testing" environment at that point by the way?), dotfiles are inherently personal configuration files, otherwise it's just application configuration, so not dotfiles anymore. Nothing wrong with sharing dotfiles, I do that plenty myself, both sharing and using parts from others, but it's on my own accord and system-wide, not project specific. Project-specific configuration is just that, project-specific configuration, and you would not call it dotfiles anymore.
- woojoo666 4y agoI found a good explanation on stackoverflow [1] by one of the co-founders. It let's you can spin up a newly provisioned dev environment from any github repository, so you can work from any client (like an iPad). Also by defining dev environments in code that can be deployed on-the-fly (aka infrastructure-as-code), that allows you to do things like share the code with others, who can "fork" your dev environment with their own customizations. This seems to be what OP's article is about. [1]: https://stackoverflow.com/a/63595356 https://stackoverflow.com/a/63595356