> On May 6, 2013 4:33 PM, "Jan Nijtmans" wrote: >> 1) modify the setup_settings page such that the related input elements >> are disabled when a versioned setting is present. >> 2) modify db_set such that when a versioned setting is present the value >> is written to the file in stead of the local configuration. >> >> 1) would be easiest to implement. 2) would mean that versioned >> settings would be editable through the /setup_settings page if >> they already exist, but you cannot remove versioned settings or >> create new versioned settings. >> >> I don't really have a preference to either 1) or 2). Any suggestions?
1) is implemented now. If anyone prefers 2) (which would make versionable settings editable through the /setup_settings page), feel free to revert [3cba68a83e] and go along with it. For me this suffices. 2013/5/6 Stephan Beal <[email protected]>: > in my experience as a www admin, writing files is often problematic because > they may (depending on the setup/environment ) have a different owning user > than the user who actually admins the content. I have had systems where i > had no root and the www user writes cache files and such, and my account > could not delete them. That said, i don't think that would be a problem for > cgi fossil, and certainly not when running it in server mode under your own > account. Versionable settings are just special files in the checked-out repository, so you are right: In server mode this is never a problem. In "fossil ui" mode, fossil already has the right permissions to be able to write versionable settings. Regards, Jan Nijtmans _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
