On Jan 10, 2017, at 11:51 AM, Lutz Filor <l...@pacbell.net> wrote:
>
> But I have problems when I want to propagate the new project.
> a) The new user, can't logout nor login
Your posted command line examples show using “fossil ui”, which means you’re
logged in with the default user on the clone repository.
The user administration stuff you’re talking about applies only to use of a
remote Fossil server, typically via HTTP.
Fossil doesn’t clone the user table when you clone the repository, on purpose,
because that would expose the passwords. I assume it copies the user names,
but only so it can tag contributions to the repo properly.
> b) The clone and the origin .fossil don't synchronize
You’re talking about tickets, which don’t auto-sync. Say “fossil sync” to
force local ticket changes to get pushed up to the repository you cloned from.
This is entirely separate from the previous issue, by the way. Syncing ticket
changes to a local clone like you’ve done should work without HTTP or user
logins and such.
> What is the correct set up flow?
Even within a single machine, I find it convenient to clone via HTTP, as that
manages all the user authentication stuff.
> How should I login in as a user ( automatic without password is fine)
When cloning over HTTP, you must give the user name in the clone URL. The
default user setting you’ve already discovered doesn’t help, since Fossil needs
a way to specify an anonymous clone, so it doesn’t automatically use that
username setting when cloning.
So:
fossil clone http://myuser@localhost/somerepo somerepo.fossil
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
