`<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jan 1, 2013 at 8:27 PM, Denis Cheong <span dir="ltr"><<a href="mailto:denis@denisandyuki.net" target="_blank">denis@denisandyuki.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div>On Wed, Jan 2, 2013 at 11:45 AM, Brian Hechinger <span dir="ltr"><<a href="mailto:wonko@4amlunch.net" target="_blank">wonko@4amlunch.net</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div>On 1/1/2013 5:09 PM, Denis Cheong wrote:<br>
</div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
The ms is not really useful if you want stuff to 'just work' ... apache from ms takes a LOT of work to get running from the ms repository.<br>
</blockquote>
<br></div></div><div>
Actually, I found apache in ms to not be terribly hard to set up. My main issue with ms is the lack of SMF bits.</div></blockquote><div><br></div><div><div>Apache from ms did not come with anything configured - the /www
directory structure where it stores everything isn't created, the config
file doesn't have any PHP in it, there are missing support programs
(including ones that are not even available) ... no docs means that you have to figure out all this yourself.<br></div></div></div></div></div></div></blockquote><div><br></div><div>As noted here: <a href="http://omnios.omniti.com/wiki.php/Packaging" target="_blank">http://omnios.omniti.com/wiki.php/Packaging</a> the <a href="http://ms.omniti.com" target="_blank">ms.omniti.com</a> packages are what we use internally. We have additional internal setup protocols when we use these packages. They serve our needs, though we don't mind letting others use them. As for docs, everything you need to know about Apache is at <a href="http://httpd.apache.org/docs/" target="_blank">http://httpd.apache.org/docs/</a></div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div><div> </div>
SMF bits are there from ms, they are just not installed by default ... you have to import them in (and of course there's no docs yet). Not sure why these packages only half-install them like that ... other than that because they do not have a working configuration out of the box, installing them into SMF would be premature - you have to finish doing the install manually before there's any use installing the SMF entries.<br>
</div></div></div></div></div></blockquote><div><br></div><div>The SMF manifest that ships with Apache is an example. Each of our internal projects keep their own customized manifests in our configuration management systems. The one in the package is there to serve as a guide for our developers when setting up a new instance.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote"><div>It's early days I guess ... while I understand and appreciate that OmniOS is 'minimalistic' in its base install, it would be nice to be able to say with a few simple commands: Create me a web server zone, and install Apache with PHP and Zend, and have it be up and running with a working configuration without needing to edit a single config file. <br>
<br>Likewise with "create me a MySQL server zone" ...<br><br></div><div>Lack of the ability to get working configs up and running easily is going to hold back OmniOS from broader adoption IMHO...<br></div></div>
</div></div></div>
</blockquote></div><br></div><div class="gmail_extra">It sounds like you want a configuration management tool. An operating system or package install cannot possibly account for all permutations of user requirements. The things you say you want are necessarily site-specific, and these days there are numerous choices for programmatically describing the setup you want. See Chef, Puppet, cfengine, etc. The OS and packages are your raw materials, from which you construct the kinds of systems you want, either hand-crafting them or using additional tools as your "factory".</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><span style="color:rgb(102,102,102)">Another way to get what you want would be to roll your own packages that put things where you want, install your SMF manifests, and contain site-local configs. Feel free to fork <a href="https://github.com/omniti-labs/omnios-build.git">https://github.com/omniti-labs/omnios-build.git</a> and roll your own. We're happy to lend advice with getting a build environment set up.</span><br>
</div><div class="gmail_extra"><span style="color:rgb(102,102,102)"><br></span></div><div class="gmail_extra" style><span style="color:rgb(102,102,102)">Eric</span></div>
</div>
`