<html><head></head><body><div>On Mon, 2017-08-21 at 21:47 -0500, o1bigtenor wrote:</div><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 21, 2017 at 7:50 PM, r hayman <span dir="ltr"><<a href="mailto:rhayman@pureice.com" target="_blank">rhayman@pureice.com</a>></span> wrote:<br><blockquote type="cite"><div><div><div class="h5"><div>On Mon, 2017-08-21 at 19:32 -0500, o1bigtenor wrote:</div><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 21, 2017 at 6:39 PM, r hayman <span dir="ltr"><<a href="mailto:rhayman@pureice.com" target="_blank">rhayman@pureice.com</a>></span> wrote:<br><blockquote type="cite"><div><div class="m_-2253691861314083826h5"><div>On Mon, 2017-08-21 at 17:55 -0500, o1bigtenor wrote:</div></div></div><blockquote type="cite"><div><div class="m_-2253691861314083826h5"><div dir="ltr">Greetings<div><br></div><div>I am trying to effect a server installation comprising of </div><div><br></div><div>Apache2</div><div>Postgresql</div><div>php7.0</div><div><br></div><div>On an initial attempt to do this a mountain of problems were uncovered.</div><div>It would seem that there is a preferred order in which to do things.</div><div>I.e. to achieve the expected result with a minimum of pain.</div><div>Some of the 'guides' download everything all at once and then work at setting things up and configuring things. There seem to be some different possibilities for order i.e. </div><div><br></div><div>1. database </div><div>2. php</div><div>3. apache</div><div><br></div><div>or </div><div>1. apache</div><div>2. database</div><div>3. connect the two </div><div>4. php</div><div><br></div><div>Is there anyone who has an install 'recipe' that works for installing </div><div><br></div><div>1. Postgresql</div><div>2. web server (haven't used any so am open just want good reasons as to why the recommendation)</div><div>3. php (because that is what one has to use to get web sites to work aiui!)</div><div><br></div><div>TIA</div><div><br></div><div>Dee</div></div>
</div></div><pre>______________________________<wbr>_________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/ma<wbr>ilman/listinfo/tclug-list
</a></pre></blockquote><div><br></div><div>Hi Dee - Have you looked at <a href="https://supermarket.chef.io/" target="_blank">https://supermarket.chef.io<wbr>/</a>, there's also a tutorial at <a href="http://gettingstartedwithchef.com/" target="_blank">http://gettingstartedwithch<wbr>ef.com/</a> that sets up a website using Chef recipes and a cookbook:</div><br></blockquote><div><br></div><div>Greetings</div><div><br></div><div>The tutorial is quite detailed. My concern would be that I was having lots of issues getting apache2 and php7.0 working. This adds another layer of complexity.</div><div>Chef doesn't seem to use postgresql as primary database, websites seem to have to have wordpress (I've seen a few too many security bulletins about that one) and then they like the cloud (something I'm not going to touch).</div><div><br></div><div>Thanks for the idea though - - - had never heard of 'chef'.</div><div><br></div><div>Dee</div></div></div></div>
<pre>______________________________<wbr>_________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a href="mailto:tclug-list@mn-linux.org" target="_blank">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/<wbr>mailman/listinfo/tclug-list
</a></pre></blockquote><div><br></div><div>Hi Dee -</div><div><br></div></div></div><div>Chef is a tool to configure what you need in an idempotent manner. The tutorial was an example of setting up a website with all of its software installs and dependencies. </div><div><br></div><div>If you are doing a one-off setup, look at the tutorial as a means to set up your own dependencies manually. </div><div><br></div><div>If you may need to repeat this setup one or more times in the future and get the same exact results (using different URLs or not), then you probably should look into using a tool like Opscode's Chef (or Dockerfiles and Docker, or Vagrantfiles and Vagrant, or Puppet, or ansible, ... - there are many ways to skin this cat and this problem has been solved for many use cases already, don't reinvent the wheel here is all that I'm saying)</div><div><br></div></div><br></blockquote><div>Looked at Docker, have been using virtualbox, now also looking into lxc/lxd.</div><div>There just are so many way to do this and few paths that don't create that wonderful vertical learning curve so endemic to linux.</div><div> </div><blockquote type="cite"><div><div></div><div>Just trying to help...</div></div><br></blockquote><div><br></div><div>I appreciate it - - - just not sure that this tool (chef and its group) is what I need for my long term.</div><div>(There are so many things to do and I would rather be working on doing things that beating my head against the wall trying to figure out the arcanities in too many software setup scenarios - - - sorry.) </div><div><br></div><div>Thank you for your ideas!!!!</div><div><br></div><div>Dee</div></div></div></div>
<pre>_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list
">http://mailman.mn-linux.org/mailman/listinfo/tclug-list
</a></pre></blockquote><div><br></div><div>For the most part, Docker and Chef are mutually exclusive - the use cases for each are divided around your infrastructure: if using containers, Docker (a wrapper around lxc) is the way to go. If using VMs then Chef, Puppet, or Ansible can be used. If you want an agent-less way to build and idempotently configure VMs, then you can eliminate Chef as your option, if you want to use an endpoint agent installed on your target VMs then Chef is a great choice for idempotent configurations. Your specific use cases for what you are trying to accomplish will steer you towards a tool to make your job easier than manually doing everything from an ssh session to the target server. Everything as code is a reality today - hardware is thought of and built using software.</div><div><br></div><div>The leading edge of agile architecture is based on microservices deployed as containers into a cloud. This movement started about 10 years ago; and about 15 years ago loosely coupled meant Enterprise Service Bus architectures; prior to that monolithic architectures were all we knew how to do. Without knowing your use cases I can only give a broad brush stroke of solutions.</div><div><br></div><div>Perhaps an out of the box solution to your use case may already exist in <a href="https://servicebot.io/?">https://servicebot.io/</a> ? </div><div>You didn't elaborate what your end goal was other than setting up a business web server, or did I miss what you specified? Apologies if I did miss that.</div><div><br></div><div>Still trying to help <img src="cid:1503450866.2962.35.camel@pureice.com" alt=";-)"></div><div><br></div></body></html>