![]() # (forwards remote ports to localhost - sudo is required for 443 forwarding) # optional (in a new iTerm tab, on the host machine): To start working, I simply run the following commands: ssh devbox ![]() The server has all my dotfiles installed, so I have access to all my aliases, command-line tools and vim config. Thanks to tmux -CC, iTerm turns SSH sessions into regular macOS terminal tabs, making the whole experience seamless. Apart from VSCode, iTerm with its amazing tmux integration plays a huge part. There are a few essential tools that make working on a remote server possible. If I ever need to scrape it and set up a new one, I run my provisioning scripts and I’m ready to go within minutes. The dev machine is a VPS, running latest Ubuntu. ![]() I initially wanted to set up an Intel NUC in my local network to reduce latency, but thanks to VSCode Remote Development, latency is not really a problem when editing, so I’d much rather not have to deal with an extra computer at home. That’s never going to change, so the best way to get the most out of Docker is to run it on the platform it was built for: Linux.Īnd that’s my solution: I now have a remote Linux development server with Docker.Ĭurrently, I’m using a droplet on DigitalOcean. Docker Will Never be Fast on the Macĭocker for Mac will always need some kind of virtualization and file sync. And ironically, the solution is to not run it on macOS. While Ubuntu Desktop has improved significantly since the last time I tried it, I depend too heavily on macOS software to give it up altogether.Īfter a few attempts, I’ve found a way to make Docker work for me on macOS. Why not simply use an Ubuntu laptop instead? I’ve tried it (with a Dell XPS) and, for me, it doesn’t work. MacBook with Docker will always run hot, battery will drain in less than an hour, fan speed is high enough for the laptop to take off and I need an external SSD disk to fit all the images. But on macOS, despite every possible performance tweak, Docker had been a huge pain. Docker helps us make sure the whole stack works for everyone, every time.įor those using Linux, it works without noticeable downsides. It’s a medium-sized Rails monolith with a bunch of resource-heavy dependencies (Postgres, PostGIS, ElasticSearch, Redis, Next.js and a few more). The app I’m currently working on runs on Docker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |