Re: [fossil-users] Hosted fossil solution
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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Hosted fossil solution
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. On Aug 1, 2010, at 2:31 PM, Joshua Paine wrote: 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 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] Hosted fossil solution
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 On 31 July 2010 02:29, altufa...@mail.com wrote: This site works like a charm... Thanks for the great tool! - Altu -Original Message- From: James Turner ja...@calminferno.net To: fossil-users@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 ja...@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 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 listfossil-us...@lists.fossil-scm.orghttp://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] Hosted fossil solution
On Jul 31, 2010, at 9:10 AM, Joshua Paine wrote: On 07/31/2010 08:09 AM, Dig412 wrote: 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! ___ 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] Hosted fossil solution
On 07/31/2010 10:11 AM, James Turner wrote: 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 fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Hosted fossil solution
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? On Jul 31, 2010, at 10:34 AM, Joshua Paine wrote: On 07/31/2010 10:11 AM, James Turner wrote: 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 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] Hosted fossil solution
At 06:10 AM 7/31/2010, Joshua Paine wrote: On 07/31/2010 08:09 AM, Dig412 wrote: 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. 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 r...@cheshireeng.com Cheshire Engineering Corp. http://www.CheshireEng.com/ ___ 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] 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 ja...@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 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] Hosted fossil solution
Quoting James Turner ja...@calminferno.net: 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. ___ 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] Hosted fossil solution
On Wed, Jul 28, 2010 at 02:19:13AM -0400, saulgo...@flashingtwelve.brickfilms.com wrote: Quoting James Turner ja...@calminferno.net: 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. 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 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 :) 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 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] Hosted fossil solution
James Turner ja...@... writes: 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 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 :-( ___ 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] Hosted fossil solution
On 07/28/2010 02:37 PM, Wolfgang wrote: 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 ___ 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] Hosted fossil solution
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. On Jul 21, 2010, at 1:08 PM, Richard Hipp wrote: On Wed, Jul 21, 2010 at 12:53 PM, James Turner ja...@calminferno.net wrote: 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 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] Hosted fossil solution
On Tue, Jul 27, 2010 at 10:15 PM, James Turner ja...@calminferno.netwrote: 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? On Jul 21, 2010, at 1:08 PM, Richard Hipp wrote: On Wed, Jul 21, 2010 at 12:53 PM, James Turner ja...@calminferno.netwrote: 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 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 -- - 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] Hosted fossil solution
Richard Hipp wrote: 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 ___ 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] Hosted fossil solution
On Wed, Jul 21, 2010 at 12:53 PM, James Turner ja...@calminferno.netwrote: 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 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
