On 1/20/2016 7:33 PM, [email protected] wrote:
....
i'm currently able to create users and set permissions and such, but
so far i haven't been able to figure out how to set:

project name
> project description
> index page

how can this be done via command-line? and where is this documented?

The most "official" way is probably through the --template option to the "fossil new" command. According to "fossil help new", it specifies a repository to use as a template for the new one, carrying over most settings from the template to the new repository, except for the list of normal users.


After you have a repository, you can copy the configuration from an existing one with "fossil configuration pull AREA".


A trickier by very scripty approach would also be through the "fossil configuration" command. It's export, import, and merge subcommands allow the configuration to be saved and loaded from a file.

On my clone of the fossil repository, the command:

C:\...> fossil configuration export project project.txt

created project.txt containing these lines:

# The "project" configuration exported from
# repository "C:/Users/Ross/Documents/tmp/fossil4/..\fossil.fossil"
# on 2016-01-21 03:54:09
config /config 40
1318883638 'project-name' value 'Fossil'
config /config 51
1318883638 'project-description' value 'Fossil SCM'
config /config 55
1318883638 'index-page' value '/doc/tip/www/index.wiki'
config /config 32
1318883638 'manifest' value 'on'

which by some coincidence covers all three of the items you asked about. I believe that you can generally edit this file, although you probably have to adjust the byte count at the end of each "config /config n" line to be correct for the import or merge subcommands to read the file.

See the output of fossil help configuration for documentation.

The configuration is broken into areas which can be handled individually. The areas are: all email project shun skin ticket user

Most items have a fairly obvious format in the file, a little experimentation will lead you where you want to go.


i'm sure i'll end up wanting more configuration items, but figure if
someone can explain this part to me i'll be able to figure out the
others.

If you have a lot of repositories that should share the same list of users and related login details, you might be better served by using the login group mechanism, although it can be quirky to get set up. Once it is happy, logging in to any repository through the web interface logs you into all of them.

--
Ross Berteig                               [email protected]
Cheshire Engineering Corp.           http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to