On Mon, May 23, 2016 at 10:41 AM, Steve Schow <st...@bstage.com> wrote:
> Is it fair to say, tickets, wikis and checkins are stored in artifacts…. > while pretty much all configuration stuff including TH1 code, SQL, UI > enhancements, etc are probably not artifacted? > I don't know if they are also stored in artifacts. That would be a question either for the Fossil source code or Richard. The "fossil config" command does allow for pushing/pulling configuration, so there might be artifacts, possibly temporary, so that configuration can be pushed/pulled using the same mechanism as repository content. > Except for this .fossil-settings folder you mentioned, which I was not > aware of…what is in there? > In the Fossil web UI of your repo, go to Admin -> Settings (probably http://localhost:8080/setup_settings) Some of the setting listed on that page are marked with (v). those are the version-able settings Under the edit-able list of settings, there is: > Settings marked with (v) are 'versionable' and will be overridden > by the contents of files named .fossil-settings/PROPERTY > in the check-out root. If such a file is present, the corresponding > field above is not editable. Another way to version the settings is to use "fossil config export" and "fossil config import", which save/restore the settings to/from a file that could be versioned. However, settings in that file must be explicitly imported to be used.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
