can a repo be local and global at the same time, i.e. if I want to
provide access to my repo through apache - do I need to have one repo
for apache and one local or can it be one and the same repo?
If it can be one and the same repo does this mean that I don't need to
make push/pull only commit/update?
Thank you,
ST
_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> can a repo be local and global at the same time, i.e. if I want to
> provide access to my repo through apache - do I need to have one repo
> for apache and one local or can it be one and the same repo?
It can: you do this every time you run `fossil server` in an open
checkout. `fossil ui` basically does kind of the same: it runs fossil
in server mode and spawns a local browser which is then told to connect
to the port opened by the serving fossil instance.
> If it can be one and the same repo does this mean that I don't need to
> make push/pull only commit/update?
That is correct.
Just be aware of the fact that your local checkout is not automatically
updated by "foreign" pushes to the same branch.
I mean, if you have, say, a branch "trunk" currently checked out, and
it's updated externally you'll have to update your checkout or your next
commit will create a fork.