Update dstack-proxy contributing guide #2683
Conversation
| ssh -i /path/to/the/gateway/key [email protected] | ||
| ``` | ||
|
|
||
| 1. Prepare an environment with your development branch on the gateway: |
There was a problem hiding this comment.
I wish the recommended approach wouldn't involve pushing changes to a remote branch. Previously, the guide suggested ssh/scp. Not ideal, but do you think this one is better?
There was a problem hiding this comment.
The previous guide suggested building and uploading a wheel. I think running from source is preferable, as it allows to iterate faster, run a debugger, and possibly edit the code on the gateway.
I've tried using rsync to upload the source code, but it's difficult to set up to upload a correct copy of the repo without uploading unnecessary files, like the local venv, and without deleting the necessary remote files, like the remote venv.
But I can include an example on how to push the code via git without the GitHub repo.
Also drop the dependency on `build`, since the guide no longer suggests building wheels
Closes #2252