> I do all of my development remotely via ssh and local forwards
I do a little with SSH tunnels, but not much. Do you mean you have it set up so that on your Mac you can go to localhost:8080 (or whatever) in your browser and it will actually go to the remote machine?
Those line's effectively mean forward my local port 8443 to the remote host's 8443. The local port + remote port (and even the remote host) don't need to be the same.
Since it’s forwarding a TCP port your aren’t limited to forwarding just the web traffic either. I forward:
- Database ports (run mysql or psql locally for example)
- Docker socket
- Backend api ports
- Redis port
- Webserver port
And more...
Then you just use local clients as if those things were all running on your local machine
Just one more step missing for a fully remote docker setup: have you ever tried combining this with a sshfs mount so you can also develop an app running in a remote container?
It’s worth reading a bit about sshuttle. It basically leverages ssh into a simple one way VPN as far as ergonomics and user experience go (but the underlying implementation is closer to opening LocalForward connections on demand).
Almost as easy: just setup a point to point WireGuard tunnel. I used sshuttle for remote Docker dev for a while, but found that WireGuard way outperforms it.
sshuttle is definitely no efficiency daemon - however, it only requires being able to ssh to the other side, amd run Python there, and that’s it - whereas for Wireguard you need root on the other side, a sufficiently new kernel (or building an out of kernel module) - it’s way better if you can use it but IME it isn’t “almost as easy” - sshuttle usually just works if you can ssh.
I'm not the person you replied to, but I frequently use the play/pause key and also the volume keys. I occasionally use the function keys in my text editor too.
Based on one of the screenshots, it looks like Guitar doesn't support word diffing. Sourcetree lacks word diffing as well and has had an issue about it since 2012: https://jira.atlassian.com/browse/SRCTREE-888
> If you’d prefer not to install Microsoft Edge manually, you can wait for it to be installed in a future update to Windows 10, following our measured roll-out approach over the next several months. We will start to migrate Windows 10 customers to the new Microsoft Edge in the coming weeks, starting with a subset of Windows Insiders in the Release Preview ring.
I'm guessing 20H1 will be released sooner than several months.
That says they are starting now, so they are starting with 19H2 (in Release Preview to start, which is still 19H2 by the way, then into the wilds). "Several months" here could mean they want everything done by 20H1 (somewhere between March and May, given the usual pattern). I don't know if that also means that they are planning to move to packing New Edge in the RTW images for 20H1; so far 20H1 on Insiders still seems to have Edge Classic. But the clear thing is that these are clearly parallel rollouts right now.