[Default] On Thu, 18 Aug 2016 12:32:44 +0200, Bertram Scharpf <[email protected]> wrote:
>On Thursday, 18. Aug 2016, 11:36:03 +0200, Stephan Beal wrote: >> On Thu, Aug 18, 2016 at 11:24 AM, Bertram Scharpf <[email protected]> >> wrote: >> >> > as root I say: >> > >> > # fossil init -A jdoe someproject.fossil >> > [...] >> > # fossil server someproject.fossil >> > Listening for HTTP requests on TCP port 8080 >> > >> > Then, in another window as a regular user: >> > >> > % fossil clone -A jdoe http://localhost:8080 someproject.fossil >> > [...] >> > % mkdir someproject >> > % cd someproject >> > (someproject) % fossil open ../someproject.fossil >> > >> >> this doesn't answer your question, but in case you don't know this: you >> don't specifically need the local server: any local copy of the repo can be >> 'open'd any number of times. The repo file would have to be writable by the >> user(s), though, which it likely isn't in your case (because root created >> it). >> >> Is there a requirement that you run it as root? You could also, as any >> non-root user: >> >> fossil init ... blah.fossil >> mkdir blah >> cd blah >> fossil open ../blah.fossil >> >> or, if you prefer the server, you can still run it as non-root (the same >> user as above). > > What I posted is a boiled-down version from what I actually > wanted to do (Apache, CGI, etc.). > > The server is running as root and it is told to access a > file that has read and write permissions for its owner, > which is root. Why should the server fail to access the > file? I decided to post the root solution because it is the > most simple way to do it. I didn't mention that I even tried > a "chmod ugo+w". Please note that fossil also needs write permissions on the directory where the repositoy resides, to be able to create and delete a journal file. > Furthermore, the error message reads "not authorized to > write". In my view this is something different as "no > permission to write". I've never seen the UNIX file access > permissions being called "authorizations". The user jdoe has been given an initial password on both repositories. You have to use the password of jdoe on the 'root' repository for push to succeed. The clone and pull commands succeed because they are probably allowed to any user by default(?). Try: fossil push http://jdoe:password@localhost:8080 See also: fossil help push fossil help clone (for the URL format) HTH -- Regards, Kees Nuyt _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
