Re: [fossil-users] home directory must be writeable
On Mar 18, 2015, at 5:08 PM, Abilio Marques abili...@gmail.com wrote: HOME=. ./fossil command Here’s a thought: Someone on this list gave me the idea of aliasing “fossil” to “f”. I do it with a symlink instead of a shell alias so that it works even in places like a Vim :! command. If you were willing to develop such a habit, you could do it with a shell script instead, which could always set HOME to someplace writeable. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
Actually they do allow (and sometimes encourage) you to connect over ssh, and they have bash with history... but the file is written inside a directory called $HOME/data (which is writeable). Openshift is a nice service. I've used it for some time now, no issues whatsoever, but (there is always a but)... sometimes they take the way people normally work in UNIX, put it in a blender, and serve that. Even regular applications like wordpress get completely modified beyond recognition (I'm talking about directory structure). I suppose it has something to do with the fact they sell the product as a PaaS, so it's easy to setup and run from the outside. Yet, under the hood, they've got the most complicated ways to make it work. $HOME pointing to a non writable directory goes with that philosophy. On Thu, Mar 19, 2015 at 5:58 PM, Stephan Beal sgb...@googlemail.com wrote: Presumably they don't expect users to use the shell, as the shell history is also (normally) saved in the home dir (except in some ultra-pedantic setups where the history is stored in a place where the user cannot access/edit it). - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Mar 19, 2015 11:24 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ 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 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
On 3/19/15, Abilio Marques abili...@gmail.com wrote: Actually they do allow (and sometimes encourage) you to connect over ssh, and they have bash with history... but the file is written inside a directory called $HOME/data (which is writeable). In your .bashrc script (wherever that is) can you just add a line that says: export FOSSIL_HOME=$HOME/data That will probably get it working better for you. Openshift is a nice service. I've used it for some time now, no issues whatsoever, but (there is always a but)... sometimes they take the way people normally work in UNIX, put it in a blender, and serve that. Even regular applications like wordpress get completely modified beyond recognition (I'm talking about directory structure). I suppose it has something to do with the fact they sell the product as a PaaS, so it's easy to setup and run from the outside. Yet, under the hood, they've got the most complicated ways to make it work. $HOME pointing to a non writable directory goes with that philosophy. On Thu, Mar 19, 2015 at 5:58 PM, Stephan Beal sgb...@googlemail.com wrote: Presumably they don't expect users to use the shell, as the shell history is also (normally) saved in the home dir (except in some ultra-pedantic setups where the history is stored in a place where the user cannot access/edit it). - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Mar 19, 2015 11:24 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ 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 -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
On 3/19/15, Abilio Marques abili...@gmail.com wrote: Yes indeed, and that's something new for me. It was documented just a few weeks ago. Thanks a lot! Looks cleaner that way. So someone was in my same situation, or is there another useful reason for having that var? I remembered that change as having occurred years and years ago. But upon consulting the timeline, I see that Joe put it in two months ago. I don't recall the exact reason. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
Yes indeed, and that's something new for me. It was documented just a few weeks ago. Thanks a lot! Looks cleaner that way. So someone was in my same situation, or is there another useful reason for having that var? On Thu, Mar 19, 2015 at 6:39 PM, Richard Hipp d...@sqlite.org wrote: On 3/19/15, Abilio Marques abili...@gmail.com wrote: Actually they do allow (and sometimes encourage) you to connect over ssh, and they have bash with history... but the file is written inside a directory called $HOME/data (which is writeable). In your .bashrc script (wherever that is) can you just add a line that says: export FOSSIL_HOME=$HOME/data That will probably get it working better for you. Openshift is a nice service. I've used it for some time now, no issues whatsoever, but (there is always a but)... sometimes they take the way people normally work in UNIX, put it in a blender, and serve that. Even regular applications like wordpress get completely modified beyond recognition (I'm talking about directory structure). I suppose it has something to do with the fact they sell the product as a PaaS, so it's easy to setup and run from the outside. Yet, under the hood, they've got the most complicated ways to make it work. $HOME pointing to a non writable directory goes with that philosophy. On Thu, Mar 19, 2015 at 5:58 PM, Stephan Beal sgb...@googlemail.com wrote: Presumably they don't expect users to use the shell, as the shell history is also (normally) saved in the home dir (except in some ultra-pedantic setups where the history is stored in a place where the user cannot access/edit it). - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Mar 19, 2015 11:24 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ 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 -- D. Richard Hipp d...@sqlite.org ___ 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
Re: [fossil-users] home directory must be writeable
Here’s a thought: Someone on this list gave me the idea of aliasing “fossil” to “f”. I do it with a symlink instead of a shell alias so that it works even in places like a Vim :! command. Yeah, After writing yesterday's email, I worked another half hour, and ended up frustrated, so I did something similiar. That made the rest of the night more pleasant. In openshift you normally use git, but I actually love fossil, and as this is a personal project that has been running on a Raspberry for like 3 years, I won't touch git. Thanks On Thu, Mar 19, 2015 at 5:51 PM, Warren Young w...@etr-usa.com wrote: On Mar 18, 2015, at 5:08 PM, Abilio Marques abili...@gmail.com wrote: HOME=. ./fossil command Here’s a thought: Someone on this list gave me the idea of aliasing “fossil” to “f”. I do it with a symlink instead of a shell alias so that it works even in places like a Vim :! command. If you were willing to develop such a habit, you could do it with a shell script instead, which could always set HOME to someplace writeable. ___ 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
Re: [fossil-users] home directory must be writeable
Presumably they don't expect users to use the shell, as the shell history is also (normally) saved in the home dir (except in some ultra-pedantic setups where the history is stored in a place where the user cannot access/edit it). - stephan Sent from a mobile device, possibly from bed. Please excuse brevity and typos. On Mar 19, 2015 11:24 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ 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
Re: [fossil-users] home directory must be writeable
On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
On Mar 19, 2015, at 4:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Yeah, “fossil all sync” is one of several features that make Fossil uncommonly nice to use. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
Not that I'm aware of. I did some googling, and only found upset people, but no justification, nor any kind of special commands. On Thu, Mar 19, 2015 at 5:54 PM, Ron W ronw.m...@gmail.com wrote: On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques abili...@gmail.com wrote: 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. Does the hosting service provide special commands for creating directories and files in your home directory? ___ 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
Re: [fossil-users] home directory must be writeable
On Thu, Mar 19, 2015 at 5:45 PM, Richard Hipp d...@sqlite.org wrote: I remembered that change as having occurred years and years ago. But upon consulting the timeline, I see that Joe put it in two months ago. I don't recall the exact reason. Thanks Joe! This solves an annoyance for me. -- Scott Robison ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] home directory must be writeable
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/54fb48714382ecec88eb/ 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
Re: [fossil-users] home directory must be writeable
On Mar 18, 2015, at 5:04 PM, Abilio Marques abili...@gmail.com wrote: home directory /var/lib/openshift/54fb48714382ecec88eb/ 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 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
Re: [fossil-users] home directory must be writeable
Typo correction: I meant HOME=. ./fossil command On Wed, Mar 18, 2015 at 6:34 PM, Abilio Marques abili...@gmail.com wrote: Hi, I'm using fossil on an openshift gear (www.openshift.com), but I get this error: *home directory /var/lib/openshift/54fb48714382ecec88eb/ must be writeable* I hacked it by running: *$HOME=. ./fossil command* (yeah, I downloaded the binary and put it into the same directory) But I don't know, I guess that fossil shouldn't give up if it fails to access the HOME directory. I see it writes a .fossil file (sqlite database), but is it that important? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] home directory must be writeable
Hi, I'm using fossil on an openshift gear (www.openshift.com), but I get this error: *home directory /var/lib/openshift/54fb48714382ecec88eb/ must be writeable* I hacked it by running: *$HOME=. ./fossil command* (yeah, I downloaded the binary and put it into the same directory) But I don't know, I guess that fossil shouldn't give up if it fails to access the HOME directory. I see it writes a .fossil file (sqlite database), but is it that important? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
