CODEWITHSUNDEEP
version-controlmercurialtortoisehg
holms
holms

Reputation: 9560

Mercurial: Windows client for remote development

We have a test server where every developer has their own sandbox. In fact, our web project is so huge that we can't allow developers to edit everything even in sandbox. For example, there are some password files from some other web services that developers don't have permissions to see. Anyway, the thing is, we can't allow developers to clone whole projects to their own PC's for development. So we want to work remotely.

Which Windows client supports REMOTE mercurial repository exploring? I know that tortoiseHG is not capable of doing this. I tried to mount the project directory with sftpdrive software, but tortoiseHG just froze after I tried to 'explore repository' (it's probably because of low bandwidth in the office).

Please, is there any mercurial GUI client for Windows that can work over sftp?

Upvotes: 1

Views: 796

Answers (2)

shellholic
shellholic

Reputation: 6114

There is no such client. And I don't thing it will exist ever. List of clients.

If your web project is in fact a web multi-project with shared ressources, you can split your repository in subrepositories (subrepo) and fine tune permission at subrepositories level.

EDIT about comments:

if the only environment where all things resources (devices, password files, ...) are only met on the server, you can't make local development on your computer. Either you refactor your code and include mocks for non-existent resources, so your developers' computer can behaves like the server, or you continue to use sandboxes on servers and you make scripts on server that pull changes from a staging repository.

Upvotes: 1

Ry4an Brase
Ry4an Brase

Reputation: 78330

You should decompose your web app into multiple repositories and let the developers only have read/write access (via clone, push, and pull not some nonsense file xfer protocol). Something like:

/webapp  (top level repository)
  |
  +---- secret stuff here
  |
  +---- more secret stuff here
  |
  +---- developer-okay-code-only-repo

Where /webapp is the whole system in revision control, and it has many files in it that developers can't access, and then has within in a subrepo that the developers can clone and pull from (and maybe push-to).

Upvotes: 3

Related Questions