Yeah, I know home directory MUST be writable. I do fight with that all the time. I've always guessed is some sort of weird security thing. Never asked. I'm not asking fossil to change because of that. As you say, is an OpenShift issue.
Just thought fossil was of better use without global config that not usable at all. But you're right, now that I think about it, is the only time I've ever seen a home directory not owned by the corresponding user but by root. Even when I knew about the global config, I actually didn't know about the ALL command. That changes the things. I believe I've gone over it every time I run fossil help, but never stopped to learn more about it, so thanks for opening my eyes. On Thu, Mar 19, 2015 at 4:14 PM, Warren Young <w...@etr-usa.com> wrote: > On Mar 18, 2015, at 5:04 PM, Abilio Marques <abili...@gmail.com> wrote: > > > *home directory /var/lib/openshift/54fb48714382ecec880000eb/ must be > writeable* > > > That sounds like just cause to complain to OpenShift tech support. > There’s no good justification for $HOME to be read-only on a web platform > provider. You’re renting that space. > > I see it writes a .fossil file (sqlite database), but is it that important? > > > According to this, yes, it’s somewhat important: > > http://fossil-scm.org/index.html/doc/trunk/www/tech_overview.wiki > > By giving Fossil a place to write that file, you give it a place to store > global settings and to remember which Fossils it has opened, so that > commands like “fossil all sync” work as expected. > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
