[fossil-users] cannot connect to host
This cannot connect to host question has come up before, but earlier threads on this subject seem to lead to server credentials/certificate re-configuration or mis-configuration, and in this case I'm using chiselapp... Sync to chiselapp was working for me three days ago. The last sync that worked was a configuration push to update the wiki: e$ fossil configuration push all Round-trips: 1 Artifacts sent: 0 received: 0 Push done, sent: 874 received: 260 ip: 216.250.117.7 (Maybe I broke something by pushing 'all' from local to chiselapp?) Today I get: e$ fossil sync Sync with https://e...@chiselapp.com/user/e/repository/myrepo SSL: cannot connect to host chiselapp.com:443 () Sync done, sent: 0 received: 0 ip: I can log onto chiselapp on https://chiselapp.com and access the repo, so the route is fine. I updated and rebuilt fossil and tried again to no avail. e$ fossil version This is fossil version 1.33 [d43847c968] 2015-08-27 14:24:09 UTC This is on Mac OS X 10.10.5 Any ideas? Thanks. e ___ 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] Fossil added to AstLinux
On Thu, Aug 27, 2015 at 9:47 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com
wrote:
On Aug 27, 2015, at 6:27 PM, Ron W ronw.m...@gmail.com wrote:
Why a and not d (developer)? Seems to me that would cover the needed
permissions to manager the Astrix and AstLinux conf files.
I meant 'v', not 'd' ('v' is developer permissions, which is a macro for
the combined permissions assigned to developer, anonymous' and 'nobody'.)
Since the user has lighttpd's admin privileges under the AstLinux web
interface, it seemed reasonable to us that a privileges in Fossil would
be appropriate. Possibly we are allowing some privilege we really don't
want, but in our testing things seemed appropriate.
If there is some reference describing the extra permissions of 'a' vs.
'dei' I would appreciate it.
#1 under Notes in the User admin page states that 'a' (Admin) permissions
are Create and Delete Users. Since your user management is done outside
Fossil, this would seem to not be needed.
Apparently, 'a' inherits 'v' permissions, though this is not mentioned.
(Not sure, have not tested this, but your experience implies it is
inherited.)
BTW, starting Fossil server with fossil server $REPOSITORY --scgi
--localhost --port 8055 (adding the --scgi option) - and configuring lighttpd
to treat Fossil as an SCGI service - will allow Fossil to know the user
name as authenticated by lighttpd. (see Fossil as SCGI on
https://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki)
___
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] providing different commit time possible?
On 28.08.2015 01:41, Richard Hipp wrote: E.g. in mercurial one could do hg ci -d '-mm-dd HH:MM:SS' There is an undocumented --date-override '-mm-dd HH:MM:SS' option. Thanks a lot. This works like a charm. jf ___ 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] Fossil added to AstLinux
On Aug 28, 2015, at 11:40 AM, Ron W ronw.m...@gmail.com wrote:
On Thu, Aug 27, 2015 at 9:47 PM, Lonnie Abelbeck li...@lonnie.abelbeck.com
wrote:
On Aug 27, 2015, at 6:27 PM, Ron W ronw.m...@gmail.com wrote:
Why a and not d (developer)? Seems to me that would cover the needed
permissions to manager the Astrix and AstLinux conf files.
I meant 'v', not 'd' ('v' is developer permissions, which is a macro for
the combined permissions assigned to developer, anonymous' and 'nobody'.)
Since the user has lighttpd's admin privileges under the AstLinux web
interface, it seemed reasonable to us that a privileges in Fossil would be
appropriate. Possibly we are allowing some privilege we really don't want,
but in our testing things seemed appropriate.
If there is some reference describing the extra permissions of 'a' vs. 'dei'
I would appreciate it.
#1 under Notes in the User admin page states that 'a' (Admin) permissions are
Create and Delete Users. Since your user management is done outside Fossil,
this would seem to not be needed.
Apparently, 'a' inherits 'v' permissions, though this is not mentioned. (Not
sure, have not tested this, but your experience implies it is inherited.)
BTW, starting Fossil server with fossil server $REPOSITORY --scgi
--localhost --port 8055 (adding the --scgi option) - and configuring
lighttpd to treat Fossil as an SCGI service - will allow Fossil to know the
user name as authenticated by lighttpd. (see Fossil as SCGI on
https://www.fossil-scm.org/index.html/doc/trunk/www/server.wiki)
Thanks Ron ! That is helpful, much appreciated.
Lonnie
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
