Discussion:
Hosted fossil solution
(too old to reply)
James Turner
2010-07-21 16:53:03 UTC
Permalink
I'm currently playing around with the idea and code for a hosted fossil
solution. Since each fossil repository already has everything you would
need, the solution would be more of a fossil repository management tool
on the web, that would let you create/manage repositories and provide a
mechanism to serve them (still working on the best solution for this
part).

I was just wondering if this is a service that people might find useful?
I'm still hashing out my ideas and currently have very basic code up and
running (creating/deleting/account mgmt). Since everything is
distributed within fossil there isn't any kind of lockin, so it's more
of a way to remove the small overhead of setting up a fossil repository
somewhere.

Feel free to let me know what you all think, or maybe point me to a
solution that already exists? Thanks.
Richard Hipp
2010-07-21 17:08:54 UTC
Permalink
Post by James Turner
I'm currently playing around with the idea and code for a hosted fossil
solution. Since each fossil repository already has everything you would
need, the solution would be more of a fossil repository management tool
on the web, that would let you create/manage repositories and provide a
mechanism to serve them (still working on the best solution for this
part).
I was just wondering if this is a service that people might find useful?
As you have observed, Fossil strives to be a "hosted-solution-in-a-box".
Just add the host and you are ready to roll. So I'm thinking that the
hosted Fossil idea is not nearly as useful as GitHub, since the distance
between raw Fossil and your hosted solution is far less than the distance
from raw git to GitHub.

That said, even Fossil requires a host. So if you don't already have a host
sitting around (as many people don't) I think such a service would be quite
useful.

Please keep us posted of your progress!
Post by James Turner
I'm still hashing out my ideas and currently have very basic code up and
running (creating/deleting/account mgmt). Since everything is
distributed within fossil there isn't any kind of lockin, so it's more
of a way to remove the small overhead of setting up a fossil repository
somewhere.
Feel free to let me know what you all think, or maybe point me to a
solution that already exists? Thanks.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
***@sqlite.org
Jeff Rogers
2010-07-26 17:48:15 UTC
Permalink
Post by Richard Hipp
That said, even Fossil requires a host. So if you don't already have a
host sitting around (as many people don't) I think such a service would
be quite useful.
It's easy enough to host a fossil repository on sourceforge, tho it
doesn't interoperate with all their other tools. I can post some simple
instructions if anyone's interested.

-J
James Turner
2010-07-28 02:15:24 UTC
Permalink
Alright well I finally managed to sit down over the weekend and get something up and running. You can check out the web app at:

http://chiselapp.com

You can currently create an account, create new repositories as well as clone existing ones. Repositories are served up like:

https://chiselapp.com/user/james/repository/fossil

Currently I'm limiting 5 repositories per account, everything should be considered in an alpha state, but so far everything seems to be running smoothly. Let me know if you run into any issues or have suggestions. Thanks.
Post by James Turner
I'm currently playing around with the idea and code for a hosted fossil
solution. Since each fossil repository already has everything you would
need, the solution would be more of a fossil repository management tool
on the web, that would let you create/manage repositories and provide a
mechanism to serve them (still working on the best solution for this
part).
I was just wondering if this is a service that people might find useful?
As you have observed, Fossil strives to be a "hosted-solution-in-a-box". Just add the host and you are ready to roll. So I'm thinking that the hosted Fossil idea is not nearly as useful as GitHub, since the distance between raw Fossil and your hosted solution is far less than the distance from raw git to GitHub.
That said, even Fossil requires a host. So if you don't already have a host sitting around (as many people don't) I think such a service would be quite useful.
Please keep us posted of your progress!
I'm still hashing out my ideas and currently have very basic code up and
running (creating/deleting/account mgmt). Since everything is
distributed within fossil there isn't any kind of lockin, so it's more
of a way to remove the small overhead of setting up a fossil repository
somewhere.
Feel free to let me know what you all think, or maybe point me to a
solution that already exists? Thanks.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Richard Hipp
2010-07-28 02:42:56 UTC
Permalink
Post by James Turner
Alright well I finally managed to sit down over the weekend and get
http://chiselapp.com
You can currently create an account, create new repositories as well as
https://chiselapp.com/user/james/repository/fossil
Currently I'm limiting 5 repositories per account, everything should be
considered in an alpha state, but so far everything seems to be running
smoothly. Let me know if you run into any issues or have suggestions.
Thanks.
Very nice. Thanks for this!

I added a link to Chisel from the Fossil homepage. Will the mirror of
Fossil that you have on Chisel automatically sync at some point? Do you
have a cron job that does that? How does that work?
Post by James Turner
Post by James Turner
I'm currently playing around with the idea and code for a hosted fossil
solution. Since each fossil repository already has everything you would
need, the solution would be more of a fossil repository management tool
on the web, that would let you create/manage repositories and provide a
mechanism to serve them (still working on the best solution for this
part).
I was just wondering if this is a service that people might find useful?
As you have observed, Fossil strives to be a "hosted-solution-in-a-box".
Just add the host and you are ready to roll. So I'm thinking that the
hosted Fossil idea is not nearly as useful as GitHub, since the distance
between raw Fossil and your hosted solution is far less than the distance
from raw git to GitHub.
That said, even Fossil requires a host. So if you don't already have a
host sitting around (as many people don't) I think such a service would be
quite useful.
Please keep us posted of your progress!
Post by James Turner
I'm still hashing out my ideas and currently have very basic code up and
running (creating/deleting/account mgmt). Since everything is
distributed within fossil there isn't any kind of lockin, so it's more
of a way to remove the small overhead of setting up a fossil repository
somewhere.
Feel free to let me know what you all think, or maybe point me to a
solution that already exists? Thanks.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
***@sqlite.org
James Turner
2010-07-28 02:56:26 UTC
Permalink
Thanks for the mention on the fossil site. Currently when your logged in there is an option pull in the latest changes from a cloned repository, but adding the ability to have changes auto pulled in would be nice. I think I'll make auto pull and option and set a cron that runs every hour or so.
Post by James Turner
http://chiselapp.com
https://chiselapp.com/user/james/repository/fossil
Currently I'm limiting 5 repositories per account, everything should be considered in an alpha state, but so far everything seems to be running smoothly. Let me know if you run into any issues or have suggestions. Thanks.
Very nice. Thanks for this!
I added a link to Chisel from the Fossil homepage. Will the mirror of Fossil that you have on Chisel automatically sync at some point? Do you have a cron job that does that? How does that work?
Post by James Turner
I'm currently playing around with the idea and code for a hosted fossil
solution. Since each fossil repository already has everything you would
need, the solution would be more of a fossil repository management tool
on the web, that would let you create/manage repositories and provide a
mechanism to serve them (still working on the best solution for this
part).
I was just wondering if this is a service that people might find useful?
As you have observed, Fossil strives to be a "hosted-solution-in-a-box". Just add the host and you are ready to roll. So I'm thinking that the hosted Fossil idea is not nearly as useful as GitHub, since the distance between raw Fossil and your hosted solution is far less than the distance from raw git to GitHub.
That said, even Fossil requires a host. So if you don't already have a host sitting around (as many people don't) I think such a service would be quite useful.
Please keep us posted of your progress!
I'm still hashing out my ideas and currently have very basic code up and
running (creating/deleting/account mgmt). Since everything is
distributed within fossil there isn't any kind of lockin, so it's more
of a way to remove the small overhead of setting up a fossil repository
somewhere.
Feel free to let me know what you all think, or maybe point me to a
solution that already exists? Thanks.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
James Turner
2010-07-30 23:38:31 UTC
Permalink
Post by James Turner
http://chiselapp.com
https://chiselapp.com/user/james/repository/fossil
Currently I'm limiting 5 repositories per account, everything should be considered in an alpha state, but so far everything seems to be running smoothly. Let me know if you run into any issues or have suggestions. Thanks.
Very nice. Thanks for this!
I added a link to Chisel from the Fossil homepage. Will the mirror of Fossil that you have on Chisel automatically sync at some point? Do you have a cron job that does that? How does that work?
If you clone another repository if added an option to have auto pull's happen every hour if desired, like you said this is good for repositories that just mirror other ones. Thanks again for the suggestion.

<snip>
Post by James Turner
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
a***@mail.com
2010-07-31 01:29:17 UTC
Permalink
This site works like a charm... Thanks for the great tool!

- Altu


-----Original Message-----
From: James Turner <***@calminferno.net>
To: fossil-***@lists.fossil-scm.org
Sent: Sat, Jul 31, 2010 5:08 am
Subject: Re: [fossil-users] Hosted fossil solution




On Jul 27, 2010, at 10:42 PM, Richard Hipp wrote:




On Tue, Jul 27, 2010 at 10:15 PM, James Turner <***@calminferno.net>
wrote:

Alright well I finally managed to sit down over the weekend and get
something up and running. You can check out the web app at:


http://chiselapp.com


You can currently create an account, create new repositories as well as
clone existing ones. Repositories are served up like:


https://chiselapp.com/user/james/repository/fossil


Currently I'm limiting 5 repositories per account, everything should be
considered in an alpha state, but so far everything seems to be running
smoothly. Let me know if you run into any issues or have suggestions.
Thanks.


Very nice.  Thanks for this!

I added a link to Chisel from the Fossil homepage.  Will the mirror of
Fossil that you have on Chisel automatically sync at some point?  Do
you have a cron job that does that?  How does that work?




If you clone another repository if added an option to have auto pull's
happen every hour if desired, like you said this is good for
repositories that just mirror other ones. Thanks again for the
suggestion.


<snip>


--
---------------------
D. Richard Hipp
***@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-***@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




_______________________________________________fossil-users mailing
listfossil-***@lists.fossil-scm.orghttp://lists.fossil-scm.org:8080/cgi
-bin/mailman/listinfo/fossil-users
Dig412
2010-07-31 12:09:53 UTC
Permalink
This looks great! I had a similar idea a while back, but I was going to call
it Dig-site (i.e. a place you would find fossils).

Are you planning on releasing the code? This could be really useful for
development shops to run on their own servers to manage projects.

Doug
Post by a***@mail.com
This site works like a charm... Thanks for the great tool!
- Altu
-----Original Message-----
Sent: Sat, Jul 31, 2010 5:08 am
Subject: Re: [fossil-users] Hosted fossil solution
Alright well I finally managed to sit down over the weekend and get
http://chiselapp.com
You can currently create an account, create new repositories as well as
https://chiselapp.com/user/james/repository/fossil
Currently I'm limiting 5 repositories per account, everything should be
considered in an alpha state, but so far everything seems to be running
smoothly. Let me know if you run into any issues or have suggestions.
Thanks.
Very nice. Thanks for this!
I added a link to Chisel from the Fossil homepage. Will the mirror of
Fossil that you have on Chisel automatically sync at some point? Do
you have a cron job that does that? How does that work?
If you clone another repository if added an option to have auto pull's
happen every hour if desired, like you said this is good for
repositories that just mirror other ones. Thanks again for the
suggestion.
<snip>
--
---------------------
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________fossil-users mailing
-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Joshua Paine
2010-07-31 13:10:47 UTC
Permalink
Post by Dig412
Are you planning on releasing the code? This could be really useful for
development shops to run on their own servers to manage projects.
If James wants to share his code of course more power to him, but it
seems like it would be more useful to competing services than
development shops.

If you've got the server access and know-how to install James' app, then
surely you can write a 2-line CGI script and drop all your .fossil files
in an arbitrary directory. See "Serving multiple repositories with one
script" on
<http://www.fossil-scm.org/index.html/doc/tip/www/server.wiki>. (This is
not to diminish James' work--it admirably removes a barrier for people
who don't have appropriate server access or just want to try things out.)

If someone built a repo management tool that could manage users across
multiple repos and/or do ticket or timeline aggregation, that would be
helpful for us "development shops".
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
James Turner
2010-07-31 13:36:25 UTC
Permalink
Post by Joshua Paine
Post by Dig412
Are you planning on releasing the code? This could be really useful for
development shops to run on their own servers to manage projects.
If James wants to share his code of course more power to him, but it
seems like it would be more useful to competing services than
development shops.
If you've got the server access and know-how to install James' app, then
surely you can write a 2-line CGI script and drop all your .fossil files
in an arbitrary directory. See "Serving multiple repositories with one
script" on
<http://www.fossil-scm.org/index.html/doc/tip/www/server.wiki>. (This is
not to diminish James' work--it admirably removes a barrier for people
who don't have appropriate server access or just want to try things out.)
If someone built a repo management tool that could manage users across
multiple repos and/or do ticket or timeline aggregation, that would be
helpful for us "development shops".
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
Like Joshua said, Chisel is really just a simple way to spawn new repositories and keep them under a user structure. At this time I don't plan on releasing the source code, as you might imagine it really isn't all that impressive. However, I do plan on adding new features to chisel, like better repository management. I've been thinking about a better way to link up repository credentials, so you can change your user password and have it be reflective across all repositories, however I haven't come up with a good way to set the password on newly created repositories without storing user password in cleartext, which I really don't want to do. Right now it's a one way hash using a key to compare the hash I have and what you enter at login time.

Right now I'm just having fun using fossil more and more, as you might imagine all chisel development is housed in a fossil repository!
Joshua Paine
2010-07-31 13:41:09 UTC
Permalink
Post by James Turner
however I haven't come up with a good way to set the
password on newly created repositories without storing user password
in cleartext, which I really don't want to do.
You can set the password from the command line, including on an
arbitrary repo that isn't currently 'open'. See `fossil help user`. Not
super elegant to integrate into a web app, but very possible.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
James Turner
2010-07-31 13:54:40 UTC
Permalink
Right I know, fossil repos are also just sqlite databases, thats how I'm getting the default password that gets created. My thing is, what password do I use, like I said I don't store the chisel users password in plain text. I suppose I could ask for a default password on repo creation so you don't have to later change it?
Post by Joshua Paine
Post by James Turner
however I haven't come up with a good way to set the
password on newly created repositories without storing user password
in cleartext, which I really don't want to do.
You can set the password from the command line, including on an
arbitrary repo that isn't currently 'open'. See `fossil help user`. Not
super elegant to integrate into a web app, but very possible.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
James Turner
2010-07-31 14:11:50 UTC
Permalink
Alright, I think I have a decent enough solution. I will just mimic fossil's way of storing passwords, which I believe is either in cleartext or a sha1 of the password. Really if someone can get access to the current chisel password hash they can get access to the key as well so it's would be just as easy to run a dictionary attack against as it would on a sha1 hash. This way I can just insert the sha1 in the the fossil db on creation and then also sync across if you change your chisel password. Of course you can always change the password in the repo if you don't want them to match.
Post by James Turner
Right I know, fossil repos are also just sqlite databases, thats how I'm getting the default password that gets created. My thing is, what password do I use, like I said I don't store the chisel users password in plain text. I suppose I could ask for a default password on repo creation so you don't have to later change it?
Post by Joshua Paine
Post by James Turner
however I haven't come up with a good way to set the
password on newly created repositories without storing user password
in cleartext, which I really don't want to do.
You can set the password from the command line, including on an
arbitrary repo that isn't currently 'open'. See `fossil help user`. Not
super elegant to integrate into a web app, but very possible.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Joshua Paine
2010-07-31 14:34:58 UTC
Permalink
Post by James Turner
Alright, I think I have a decent enough solution. I will just mimic
fossil's way of storing passwords, which I believe is either in
cleartext or a sha1 of the password.
The repo id (and maybe the username?--can't recall) is hashed together
with the password. You should look at the fossil source for this part.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
James Turner
2010-07-31 21:14:15 UTC
Permalink
Your right, the sha1 is of the fossil repo id + username + password. So I guess here is my question for you guys. Would you rather have the random initial password and be forced to change it within the fossil ui on creation or would you rather I store your chisel password in cleartext, then created the sha1 for your fossil repo and set it so you can use the same username/password?
Post by Joshua Paine
Post by James Turner
Alright, I think I have a decent enough solution. I will just mimic
fossil's way of storing passwords, which I believe is either in
cleartext or a sha1 of the password.
The repo id (and maybe the username?--can't recall) is hashed together
with the password. You should look at the fossil source for this part.
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Joshua Paine
2010-08-01 18:31:26 UTC
Permalink
What about give me the option to enter a password on repo creation? Depending on the form layout, my browser will fill in the same one I've used on the site automatically.

Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
James Turner
2010-08-01 19:34:55 UTC
Permalink
Alright you can now set a default password at repo creation, it will generate the correct sha1 based on fossil id + username + password. I also tweaked the creation page by splitting the two types into separate pages.
Post by Joshua Paine
What about give me the option to enter a password on repo creation? Depending on the form layout, my browser will fill in the same one I've used on the site automatically.
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Ross Berteig
2010-07-31 21:26:43 UTC
Permalink
Post by Joshua Paine
Post by Dig412
Are you planning on releasing the code? This could be really
useful for development shops to run on their own servers to
manage projects.
....
If you've got the server access and know-how to install James'
app, then surely you can write a 2-line CGI script and drop all
your .fossil files in an arbitrary directory. ....
The 2-line cgi script isn't the interesting part. The interesting
part is the surrounding management interface that provides a web
face for creating and cloning new repositories and otherwise
managing the repositories themselves. IMHO, there really is a
value add to that, but it also isn't the sort of thing that
belongs inside of the fossil executable.

After all, SourceForge, GitHub and their ilk are successful
because providing the right amount of administrative capability
over and above the hosted repository makes them useful to people.

I've taken a similar approach myself. I've been working on a
package I've been calling Museum (where else do you find
fossils?) which is consists of native builds of fossil and thttpd
to run in a D-Link DNS-323 NAS box. My plan is to eventually
share this with any interested parties, but it is still in a
pre-alpha works-for-me kind of state at the moment.

Its primary use case in my shop is to provide a self-contained
set of clones of my project work. It needs a web face because the
DNS-323 doesn't naturally provide a console of any sort, or even
a telnet server.

None of the CGI scripting is particularly innovative or even
complicated, other than the goal of requiring as few new ARM
executables as possible both because cross-compilation adds its
own joys, and because there is only a limited amount of room
available in the RAM disk that its linux boots from.
Post by Joshua Paine
If someone built a repo management tool that could manage users
across multiple repos and/or do ticket or timeline aggregation,
that would be helpful for us "development shops".
That is another piece of integration that is also outside the
scope of the fossil executable. But it certainly would be
valuable to be able to group several related repositories
together in some kind of a unified view. There is a lot to work
out about how that would work in practice, of course. Can you
create a new ticket in that view? Move it from repo to repo? Copy
it? Refer to it in wiki/comment text from a different repo? Clone
the unified view as if it were a single repo?

If anyone is interested in my toy Museum, contact me on or off
list and I will happily push things from pre-alpha to alpha.
Perhaps I should just clone it to chiselapp.com and let the
interested parties have at it?

Ross Berteig ***@CheshireEng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
s***@flashingtwelve.brickfilms.com
2010-07-28 06:19:13 UTC
Permalink
Post by James Turner
Currently I'm limiting 5 repositories per account, everything should
be considered in an alpha state, but so far everything seems to be
running smoothly. Let me know if you run into any issues or have
suggestions. Thanks.
I have registered and am attempting to learn how to work all this (I
have used Fossil on remote servers on my home network but not over the
Internet).

One issue encountered was that my e-mail domain was flagged as
invalid. I believe this was owing to it containing more than a single
period (flashingtwelve.brickfilms.com). You may want to check your
validation algorithm.

I screwed up and did not properly note the password assigned after
creating my first repository
(https://chiselapp.com/user/saulgoode/repository/script-fu/) and can
not log in as administrator now. If you would be so kind as to remove
it when you get the chance, it would be much appreciated.

I created a second repository
(https://chiselapp.com/user/saulgoode/repository/script-fu-sg/) and
have been able to clone it successfully; however, when I tried to PUSH
some changes back (I'd disabled autosync), I received a 302 Re-direct
error. I think it may be trying to re-direct from HTTP to HTTPS but I
am not sure (if I use the HTTPS URL then Fossil reports that it does
not support HTTPS). It is quite possible that I am doing something
wrong at this point as I am inexperienced at using some of Fossil's
multi-user features.

Thank you for the opportunity to use your hosting. I will spend more
time experimenting tomorrow but if there is anything you wish me to
try, please ask.

Regards.
James Turner
2010-07-28 13:15:52 UTC
Permalink
Post by s***@flashingtwelve.brickfilms.com
Post by James Turner
Currently I'm limiting 5 repositories per account, everything should
be considered in an alpha state, but so far everything seems to be
running smoothly. Let me know if you run into any issues or have
suggestions. Thanks.
I have registered and am attempting to learn how to work all this (I
have used Fossil on remote servers on my home network but not over the
Internet).
One issue encountered was that my e-mail domain was flagged as
invalid. I believe this was owing to it containing more than a single
period (flashingtwelve.brickfilms.com). You may want to check your
validation algorithm.
I will fix this validation rule asap.
Post by s***@flashingtwelve.brickfilms.com
I screwed up and did not properly note the password assigned after
creating my first repository
(https://chiselapp.com/user/saulgoode/repository/script-fu/) and can
not log in as administrator now. If you would be so kind as to remove
it when you get the chance, it would be much appreciated.
When you log into chiselapp.com you can remove repositories you created
from the Dashboard.
Post by s***@flashingtwelve.brickfilms.com
I created a second repository
(https://chiselapp.com/user/saulgoode/repository/script-fu-sg/) and
have been able to clone it successfully; however, when I tried to PUSH
some changes back (I'd disabled autosync), I received a 302 Re-direct
error. I think it may be trying to re-direct from HTTP to HTTPS but I
am not sure (if I use the HTTPS URL then Fossil reports that it does
not support HTTPS). It is quite possible that I am doing something
wrong at this point as I am inexperienced at using some of Fossil's
multi-user features.
I will look into this issue today as well, funny thing, I never tested
pushing to a cloned repository, did I mention this was still alpha :)
Post by s***@flashingtwelve.brickfilms.com
Thank you for the opportunity to use your hosting. I will spend more
time experimenting tomorrow but if there is anything you wish me to
try, please ask.
Regards.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
James Turner
2010-07-28 13:29:45 UTC
Permalink
Post by James Turner
Post by s***@flashingtwelve.brickfilms.com
Post by James Turner
Currently I'm limiting 5 repositories per account, everything should
be considered in an alpha state, but so far everything seems to be
running smoothly. Let me know if you run into any issues or have
suggestions. Thanks.
I have registered and am attempting to learn how to work all this (I
have used Fossil on remote servers on my home network but not over the
Internet).
One issue encountered was that my e-mail domain was flagged as
invalid. I believe this was owing to it containing more than a single
period (flashingtwelve.brickfilms.com). You may want to check your
validation algorithm.
I will fix this validation rule asap.
Should be fixed, email containing subdomains should work.
Post by James Turner
Post by s***@flashingtwelve.brickfilms.com
I screwed up and did not properly note the password assigned after
creating my first repository
(https://chiselapp.com/user/saulgoode/repository/script-fu/) and can
not log in as administrator now. If you would be so kind as to remove
it when you get the chance, it would be much appreciated.
When you log into chiselapp.com you can remove repositories you created
from the Dashboard.
I noticed there is a bug where all repositories have the option to pull
next to them in the Dashboard, I will fix this so it only shows up for
cloned repositories.
Post by James Turner
Post by s***@flashingtwelve.brickfilms.com
I created a second repository
(https://chiselapp.com/user/saulgoode/repository/script-fu-sg/) and
have been able to clone it successfully; however, when I tried to PUSH
some changes back (I'd disabled autosync), I received a 302 Re-direct
error. I think it may be trying to re-direct from HTTP to HTTPS but I
am not sure (if I use the HTTPS URL then Fossil reports that it does
not support HTTPS). It is quite possible that I am doing something
wrong at this point as I am inexperienced at using some of Fossil's
multi-user features.
I will look into this issue today as well, funny thing, I never tested
pushing to a cloned repository, did I mention this was still alpha :)
Alright so the reason for the redirect is I do not allow repositories to
be served over anything but https. It's strange that you were able to
clone over https, but when you try to push over it fossil complains that
it doesn't support https. I am able to push to a cloned repository just
fine myself, my suggestion is to make sure your running a recent
snapshot of fossil, the lastest is 2010-07-03 15:33:59 and make sure
-DFOSSIL_ENABLE_SSL is set in your Makefile.
Post by James Turner
Post by s***@flashingtwelve.brickfilms.com
Thank you for the opportunity to use your hosting. I will spend more
time experimenting tomorrow but if there is anything you wish me to
try, please ask.
Regards.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Wolfgang
2010-07-28 18:37:38 UTC
Permalink
Post by James Turner
Alright well I finally managed to sit down over the weekend and get something
http://chiselapp.com
Thank for the work. This looks realy nice for a alpha-version.

I've added a public repository
https://chiselapp.com/user/wst/repository/WST-Skin-1
to show/test my own skin for fossil.

I cannot clone the repo to my own machine, because i have to use the published
windows version without https support :-(
James Turner
2010-07-28 18:57:34 UTC
Permalink
Post by Wolfgang
Post by James Turner
Alright well I finally managed to sit down over the weekend and get something
http://chiselapp.com
Thank for the work. This looks realy nice for a alpha-version.
I've added a public repository
https://chiselapp.com/user/wst/repository/WST-Skin-1
to show/test my own skin for fossil.
I cannot clone the repo to my own machine, because i have to use the published
windows version without https support :-(
I have removed the forced redirect for now, be warned everything
will be transfered in clear text! https is still available, I will tweak
the copy tonight.
Post by Wolfgang
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Wolfgang
2010-07-28 19:41:54 UTC
Permalink
Post by James Turner
.....
I have removed the forced redirect for now, be warned everything
will be transfered in clear text! https is still available, I will tweak
the copy tonight.
.....
Using standard http works. I was able to clone and sync the repository with my
official windows build of fossil.

It's OK for, that there is a security hole, while using your hosted fossil. But
the repository doesn't contain important information.

I'm using fossil in my local network, so it's not a problem, to use http. I
don't have the frameworks to build a https-version for windows (and no time :-).

Thanks
Wolfgang
Arnel Legaspi
2010-07-30 06:46:09 UTC
Permalink
Post by Wolfgang
I'm using fossil in my local network, so it's not a problem, to use http. I
don't have the frameworks to build a https-version for windows (and no time :-).
I have Win32 builds of Fossil (including the HTTPS version) available if
anyone needs it. The Fossil version I'm using is [93d7f371cc] 2010-07-21.

For those who are curious, I used the steps listed by Rob Powell from a
previous thread:
http://www.mail-archive.com/fossil-***@lists.fossil-scm.org/msg01749.html

Here's the direct link:
http://dl.dropbox.com/u/1822010/fossil-scm_nuwen-build.zip

N.B.: The builds were made using the latest MinGW distro from
http://nuwen.net/mingw.html. The HTTPS version also uses OpenSSL v1.0.0a.

Thanks,
Arnel
Joshua Paine
2010-07-28 19:02:06 UTC
Permalink
Post by Wolfgang
I cannot clone the repo to my own machine, because i have to use the published
windows version without https support :-(
This is why I have concluded it's not practical to use HTTPS with
fossil. If I'm going to be working with someone from a client on an app,
they probably aren't familiar with SCM at all or at least aren't
familiar with fossil, and I can't make it any more cumbersome or
sketchy-looking by asking them to download fossil from anywhere
unofficial (and I sure don't want to maintain a windows build of my
own--not that that would solve the problem, as it would make fossil look
like my own pet thing).
--
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
Loading...