<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mihael,<br>
<br>
Does the new config allow you to specify multiple sites in the
swift.conf and select the site you want to run on from the swift
commandline. <br>
I searched the swift-trunk userguide, but did not see any reference
to this.<br>
<br>
The 0.95 tutorials, which I think are the cleanest our tutorials
have been, let you select the site(s) you want to run on and the <br>
swift.properties sets a default site(s) to use in case no
commandline option is given for site<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
swift.properties:<br>
# default site is local<br>
site=local<br>
site.beagle-remote {<br>
}<br>
<br>
site.local {<br>
<br>
}<br>
<br>
Thanks,<br>
Yadu<br>
<br>
<br>
<div class="moz-cite-prefix">On 07/16/2014 01:04 AM, Mihael Hategan
wrote:<br>
</div>
<blockquote cite="mid:1405490652.15732.23.camel@echo" type="cite">
<pre wrap="">Hi,
I'll be in New York for the remainder of the week and returning Monday
(21st). I might sporadically work on this, but in all likelihood commits
will come after that. However, I wanted so sync on the latest spec:
* releaseConf=$SWIFT_HOME/etc/swift.conf
siteConf=$SWIFT_SITE_CONF (if $SWIFT_SITE_CONF defined)
userConf=$HOME/.swift/swift.conf (if present)
runConf=$PWD/swift.conf (if present)
-config
* The configs should be chained automatically.
* Documentation updated, in particular copying and updating the 0.95
section on the search path and documenting swift-convert-config and how
to migrate from pre-0.95 files. The tool should also be updated to
accept and convert 0.95 configs.
* -noReleaseConf, -noSiteConf, -noUserConf, -noRunConf command-line
flags to be added. Please comment on the equivalent properties and the
difficulty in implementing them. If you feel it's important, it might be
worth conquering those difficulties.
* line numbers for properties in -listconfig and log.
Things that might still merit some discussion:
* -listconfig <files|full> (this is a proposal to add a parameter to
-listconfig that specifies whether only a list of files or a list of
files and all options should be printed).
* Also please comment on the -config file vs. -config file1:file2... and
the need for -reconfig. I can't quite tell whether these were meant to
be discussed or not, and if yes, where we are with that.
- another question is whether we want properties (in -listconfig and
log) to be printed as a flat set of dotted properties or grouped. In
other words:
site.one.workDirectory = ..
site.one.staging = ...
or
site.one {
workDirectory = ...
staging = ...
}
Mihael
_______________________________________________
Swift-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a>
<a class="moz-txt-link-freetext" href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>