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.
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? > > > 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 > > > > > -- > --------------------- > 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
