On 11/28/16, Warren Young <[email protected]> wrote:
> I’ve noticed that if I make a change to a non-artifact setting in the
> repository on a different machine that re-syncing does not give me a copy on
> my machine.
>
> Examples:
>
> - Skin changes
> - Ticket tracker customizations
> - Everything in Admin > Settings
>
> If I close the repo, re-clone, and reopen it on my local machine, Fossil UI
> locally matches what I see via “fossil server” on the remote machine, so it
> must be sending all of these things with the clone.
>
> Is this intentional or just an oversight waiting for someone to fix it?
>
This is by design.
The idea is that there might be multiple clones of a project that are
under different administrative domains where the various
administrators want different configuration settings. For example,
somebody might want to set up a clone of the Fossil self-hosting
repository that used a different skin. And so the settings are not
synced automatically.
To pull configuration changes use:
fossil configuration pull all
You can substitute various other keywords for "all" to pull only those
parts of the configuration you care about: email, project, shun, skin,
ticket, or user.
To sync up everything on all your repositories, run:
fossil all config pull all
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
