<div dir="ltr"><div>Except for the URL (lack of smartness of scripting on our end) and
your misunderstanding that apache is needed for tomcat (tomcat is a
completely independent server then devel/apache22 [if it also installed
devel/apache22 let me know this is a bug]) the instructions have been
tested end to end at least 10 times I know of including a successful
install in Canada and I suspect more people have not reported since we
keep no stats on this.<br><br>To start tomcat do<br><br> sudo service tomcat7
onestart<br><br>(you need to do TOMCAT7="enable" in /etc/rc.config to make it
rebootable)....<br><br>the reason for the long ports build vs. packages is
since we are in active development (the current version is late alpha
early beta quality and will be fully beta by mid Aug when we will be
adding a much better security layer including HIPAA compliance) we need
to be sure we are compiling against the most recent versions of stuff
(packages often lag by upto a month).... during this process we will be
drastically streamlining the install process and improving the
instructions with user feedback (your the first with feed back who was
not also on the core team)... <br><br>as to the question if we are a proof of
RMCH I certainly hope not seeing that paper was written in 98 and I have
been using cook (the program based on it) since 2002 (I wrote the
official tutorial).... our current build system needs a lot of help and
is also due for a rewrite in 0.3 <br><br></div><div>We use make in our port because FreeBSD requires the use of make in ports. However, the makefile is strictly boilerplate that calls cook. We do not use make in our development work. Instead we use cook exclusively. We also use aegis as our change management system.<br>
</div><div>
<br></div>For more info on why we use aegis and cook see <br><br><a href="http://hv-allconnections.quora.com/SE-Peter-Miller-the-first-and-totally-forgotten-modern-software-engineer" target="_blank">http://hv-allconnections.quora.com/SE-Peter-Miller-the-first-and-totally-forgotten-modern-software-engineer</a><br>
<br><a href="http://hv-allconnections.quora.com/SE-Cliff-notes-to-Millers-3rd-law-of-modern-software-engineering-aka-Recursive-Make-Considered-Harmful" target="_blank">http://hv-allconnections.quora.com/SE-Cliff-notes-to-Millers-3rd-law-of-modern-software-engineering-aka-Recursive-Make-Considered-Harmful</a><br>
<br><a href="http://hv-allconnections.quora.com/SE-Aegis-The-solution-to-Millers-1st-and-2nd-laws-of-modern-software-engineering" target="_blank">http://hv-allconnections.quora.com/SE-Aegis-The-solution-to-Millers-1st-and-2nd-laws-of-modern-software-engineering</a></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Jun 16, 2014 at 5:09 PM, Dave Smith <span dir="ltr"><<a href="mailto:dsmith@johncompanies.com" target="_blank">dsmith@johncompanies.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi All,<br>
<br>
Is PetiteCloud just a hoax to prove the premise that recursive make is<br>
harmful (as stated in one of your links)?<br>
<br>
Has anyone tried following the directions described on the website to<br>
install PetiteCloud on a fresh FreeBSD 10.0 installation using bhyve?<br>
<br>
Here are my results. I installed FreeBSD 10.0 and did a freebsd-update<br>
to get to patch level 5. I tried at least 4 times using some binary<br>
installs and at least one complete port install.<br>
<br>
1. The make install takes about 2-4 hours on a fairly fast machine.<br>
<br>
2. It tries to recompile everything from the ports collections instead<br>
of using any binary pkg installs. This includes gcc, perl5, xlib, qemu,<br>
and many other things that take enormous amounts of time to re-compile.<br>
<br>
3. It does not install Apache, which is required to run the Tomcat that<br>
PetiteCloud appears it use to implement the user interface.<br>
<br>
4. The directions say to use port 8080, but I can not find any attempt<br>
to set up Apache on port 8080.<br>
<br>
5. The make system fails and stops for missing pieces or sources at<br>
least 3 times. It also stops very many times to demand configuration<br>
input, which requires constant monitoring during the entire make<br>
process. (I realize these are probably problems with the FreeBSD ports<br>
collection.)<br>
<br>
6. Instructions telling me to go to<br>
<a href="http://127.0.0.1:8080/petitecloud-aryeh-0.2.6" target="_blank">http://127.0.0.1:8080/petitecloud-aryeh-0.2.6</a><br>
assumes I am running this on my work station and not on a server.<br>
<br>
I am not a complete novice at this. I have a long career writing<br>
software and doing system administration. I was unable to get this to<br>
install and operate correctly with 4 attempts. I could probably<br>
continue and eventually get PetiteCloud to work, but I am not sure I<br>
have the time to invest anymore.<br>
<br>
I wanted to use this in a production environment, but it appears that<br>
PetiteCloud is not ready for that.<br>
<br>
I would really like to know if anyone has successfully followed the<br>
instructions as I have done?<br>
<span class="HOEnZb"><font color="#888888"><br>
Dave Smith<br>
_______________________________________________<br>
petitecloud-general mailing list<br>
<a href="mailto:petitecloud-general@lists.petitecloud.nyclocal.net">petitecloud-general@lists.petitecloud.nyclocal.net</a><br>
<a href="http://lists.petitecloud.nyclocal.net/listinfo.cgi/petitecloud-general-petitecloud.nyclocal.net" target="_blank">http://lists.petitecloud.nyclocal.net/listinfo.cgi/petitecloud-general-petitecloud.nyclocal.net</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr">Aryeh M. Friedman, Lead Developer, <a href="http://www.PetiteCloud.org" target="_blank">http://www.PetiteCloud.org</a><br></div>
</div>