A developer or sys admin would use it to keep track of changes a site owner would do via ftp/sftp. We made it for this specific reason. Track everything! :)
So is this intended as a single user sort of tool? I'm curious how merges, conflicts & branching would interact w/ a tool like this, or whether it's just intended as a way to implement a versioned file system essentially where files can be rolled back to previous states.
Currently it follows a single branch. The merge strategy is to merge with local changes taking priority over remote ones but this can be plugged-in.
Rollbacks can be done by copying from history to current version.
The only thing shaky thing is when there is a force push because local commits will be pushed back.
makes sense as a simple deployment tool too i guess? simply mount the stable branch in your 'www' directory and you can push to deploy (for a static files based site at least).
No, I think the question is, what do you as an author of the software have in mind as a particular use case? Some examples of why someone would use this would be great.
We are using it to expose website code through SFTP to non-developers.
Another possible use case can be publishing static sites using jekyll or another tool.
We have given some answers (together with vtemian) related to some of the use cases that we see possbile and to the need that it led to its creation in the first place. But since it's open-source, we are also expecting fresh scenarios in which people would like to use it. Also, contributions are more than welcome! :)
