For what it's worth, for more own testing, I deploy and configure a single
Fedora installer zip multiple times using an (ugly) shell script, setting
configuration parameters as environment variables that then percolate down to
the Fedora instance.
Most configuration settings can be set in the i
I agree that packing a Fedora home (or more than one) into the source tree
is not a good thing. For context, the reason that I tried that for the
client was simply that I had tried that for the server. The reason that I
tried that for the server was because you don't need one Fedora home for
the se
This may be mostly directed at Adam, but just in case anyone else has any
experience or ideas on the matter:
I took another look at
https://github.com/mediashelf/fedora-client/tree/test-with-Cargo (which still
won't run correctly for me anyway), which uses Cargo to start up an instance of
Fedo
Hmm i don't have this Warning in the office, i will have to check when i
come home...
On 08/30/2012 06:40 PM, Benjamin Armintor wrote:
> that looks like it's not finding a schema called fedora-types.xsd to
> import. Is there a file by that name in that directory?
>
> On Thu, Aug 30, 2012 at 7:11
