[fossil-users] copy configuration from repo to repo?

57 views
Skip to first unread message

ST

unread,
Mar 20, 2012, 6:19:38 AM3/20/12
to fossil...@lists.fossil-scm.org
Hi,
1) I've just configured my first fossil repo and now would like to copy
this configuration to other projects. Is it possible?
Most problematic part is enabling "assigned_to" and "opened_by" in
tickets as per this:
http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . Why
isn't it actually there out of the box? Or it is there and I just missed
it? It is a bit painful to go through this process for all the project
that I have...

2) Two ideas for future features (please tell me whether you will
consider implementing them):

a) alias for urls: possibility to provide an alias for url of each page
so that it looks cleaner. For example for the page mentioned above alias
could be "custom_ticket", so that the url will look like:
http://fossil-scm.org/custom_ticket

b) a page with a simple contact form (optionaly with captcha and
attachments) that will send the message to a predifined email according
to topic selected by sender.

Thank you,
ST

_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Ron Aaron

unread,
Mar 20, 2012, 6:42:21 AM3/20/12
to fossil...@lists.fossil-scm.org
On 03/20/2012 12:19 PM, ST wrote:
> Hi,
> 1) I've just configured my first fossil repo and now would like to copy
> this configuration to other projects. Is it possible?

Hello -

It is simple: do "fossil help config" for all the options, but you
basically want "fossil config export" and "fossil config import"

> Most problematic part is enabling "assigned_to" and "opened_by" in
> tickets as per this:
> http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . Why
> isn't it actually there out of the box? Or it is there and I just missed
> it? It is a bit painful to go through this process for all the project
> that I have...

It's not too bad, you can copy+paste from one config window to the other
(in your browser)

Richard Hipp

unread,
Mar 20, 2012, 8:27:00 AM3/20/12
to Fossil SCM user's discussion
On Tue, Mar 20, 2012 at 6:19 AM, ST <smn...@gmail.com> wrote:
Hi,
1) I've just configured my first fossil repo and now would like to copy
this configuration to other projects. Is it possible?
Most problematic part is enabling "assigned_to" and "opened_by" in
tickets as per this:
http://fossil-scm.org/index.html/doc/trunk/www/custom_ticket.wiki . Why
isn't it actually there out of the box? Or it is there and I just missed
it? It is a bit painful to go through this process for all the project
that I have...

On the repo you've already set up:

     fossil configuration export all config.txt -R alreadysetup.fossil

Then on your new repo:

    fossil configuration import config.txt -R newrepo.fossil

All the configuration information is transferred through the filed "config.txt" in the example above.  That file is pure SQL so it is ASCII text and readable.  You can move the file across systems in between the two operations, if you need to.

If you only want to transfer some subset of the configuration, you can replace "all" by "email", "project", "shun", "skin", "ticket", or "user".

See "fossil config --help" for additional information.
 

2) Two ideas for future features (please tell me whether you will
consider implementing them):

a) alias for urls: possibility to provide an alias for url of each page
so that it looks cleaner. For example for the page mentioned above alias
could be "custom_ticket", so that the url will look like:
http://fossil-scm.org/custom_ticket

b) a page with a simple contact form (optionaly with captcha and
attachments) that will send the message to a predifined email according
to topic selected by sender.

Thank you,
ST

_______________________________________________
fossil-users mailing list
fossil...@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



--
D. Richard Hipp
d...@sqlite.org

ST

unread,
Mar 21, 2012, 7:20:40 AM3/21/12
to fossil...@lists.fossil-scm.org

I tried that but after this I can no longer login neither with my
password from alreadysetup.fossil nor with the default password
generated by fossil which was created during repo initialization.

Tomek Kott

unread,
Mar 21, 2012, 11:05:08 AM3/21/12
to Fossil SCM user's discussion
I've noticed that myself, so I never to 'fossil config export all'. I only export 'tickets' or 'skins' usually, so not a big deal. I avoid every pulling / pushing the users table.

Tomek

ST

unread,
Mar 21, 2012, 11:19:21 AM3/21/12
to fossil...@lists.fossil-scm.org
Maybe this shoud be reported as bug?

ST

Reply all
Reply to author
Forward
0 new messages