Earlier quoted context omitted.
There is an enormous reason if you work on, or use, systems designed for massive parallelism.
I still don't see the necessity... Develop locally, test remotely.
[deleted]
Ask HN: How do you work efficiently on remote servers?
41–50 of 87 posts
Re: Ask HN: How do you work efficiently on remote servers?
#42ssh, tmux, vim, git, more ssh, python, bash.
Depends on project, if it is JavaEE app, or Android, then you're screwed and might as well work on a local version, because you need IntelliJ.
Re: Ask HN: How do you work efficiently on remote servers?
#43I only work on a remote 'server', by which I mean my ubuntu desktop. I hate linux gui's so I use a mac laptop and ssh into the linux box, and run emacs in Terminal.app.
For the occasional times that I need to step through java code with a debugger, I chromote in and fire up the IDE, but I don't actually use it to code.
Re: Ask HN: How do you work efficiently on remote servers?
#44Earlier quoted context omitted.
"Remote Server" Doesn't necessarily mean "Production Server"
True, but wouldn't you use Vagrant, Doccker or something similar to develop on? Can't speak for the OP's situation, but it seems a strange set-up that's all.
A Vagrant or Docker VM is still remote as far as the local desktop is concerned.
Re: Ask HN: How do you work efficiently on remote servers?
#45Earlier quoted context omitted.
There is an enormous reason if you work on, or use, systems designed for massive parallelism.
I still don't see the necessity... Develop locally, test remotely.
Some examples that just come to my mind:
- You need software/dependendencies/licences you don't have in your local machine.
- You need to edit a config file (/etc/hosts or whatever) in your server
- You are in a Windows computer (that's not yours) and you need to make a quick change in your Ubuntu development server.
- You need to edit some files when deploying (databases are no longer in localhost, /home/myname/ is /home/servername/, etc.)
- You launched a large script in your server and need to (view or parse logs | edit the code and re-launch it | check why it didn't work)
- etc.
Re: Ask HN: How do you work efficiently on remote servers?
#46Earlier quoted context omitted.
have a buildbot/jenkins set up which runs your test suite on a buildslave automatically when you push to a git branch? I would still run my editor locally (your pick. I use vim almost exclusively).
and do that for every project, even small throwaway experiments?
If it's a throwaway experiment, it shouldn't take too long to compile locally, I would think.
Re: Ask HN: How do you work efficiently on remote servers?
#47TRAMP mode in emacs let's you edit remote files, do dired etc through ssh, so that mitigates the dotfile syncing problem. edit: also sshfs, tho that isn't always a smooth experience
I came to mention TRAMP. A couple weeks ago I started running the server parts of my dev environment on a little laptop that was laying around and using tramp for all source code editing. Its pretty transparent and not having to run any VM's on my poor little aging mac is awesome.
Re: Ask HN: How do you work efficiently on remote servers?
#48Earlier quoted context omitted.
Thanks for answer. I'd love to learn about what solution your Sublime coworkers use, as most people here use emacs / vim and I'm most proficient with Sublime.
Probably they're using the "Sublime SFTP plugin" by wbond... I usually use nano on the remote server and sublime remotely via ssh with this plugin. But to be honest it is just for small tasks. 95% of the time we work in local servers with Vagrant/Docker (shared folder --> git push), since our deployments aren't that big.
Yep, Sublime SFTP.
Re: Ask HN: How do you work efficiently on remote servers?
#49I find WinSCP to be a good way to work with remote servers. It can use whatever editor you may like (ST3 in my case).
Supports full directory synchronization, has a nice UI and can be installed on a flash drive.
Re: Ask HN: How do you work efficiently on remote servers?
#50I also suggest keeping your .vimrc / .bashrc / .screenrc / whatever other config files you like in some kind of git repo so you can sync your config files to the remote machine nicely. The other nice thing about this is that if you have a remote that you don't use very often, you can either git clone the repo and rake / make to install, or even wget the file and move it in place manually.