Plan a remote development setup over SSH
Plans how to develop on a remote machine over SSH, in numbered steps with a check per step and the security habits to keep.
Task:
Plan how I set up remote development on a server so that I can edit and run code there from my laptop.
Context:
My laptop runs [operating system] and my editor is [editor or IDE]. The remote machine is [cloud VM, office server or home machine] running [remote operating system]. I need it for [reason, such as a large dataset or more CPU], and I work from [network situation].
Rules:
- Use SSH keys instead of passwords. Never ask me to paste a private key or a password in the chat, and tell me to keep the private key on my laptop only.
- Explain each command in one line before I run it, and say which ones change the SSH server config or the firewall.
- Warn me before any step that could lock me out of the machine, and give a way back in.
- Give a check after every step that shows it worked.
- Where steps depend on my provider or editor version, say so and tell me to check their docs.
Result:
A numbered list of at most 8 steps, each with the action, the command or setting, and the check. End with 3 habits that keep the setup safe.