I am working on sequencing of how to setup a forked App.

(WHAT does this README.rst do besides give documentation?)

root@tkldev fab/products# wc -l $(find core -type f|grep -v '\.git\|png\|jpg\|changelog\|README.rst\|txt$')

  3 core/Makefile
  1 core/plan/main
  2 core/conf.d/main
  6 total

However in more complicated Lamp etc below:

Again the Readme.rst - is it giving any sequencing information?

root@tkldev fab/products$ wc -l $(find lamp -type f|grep -v '\.git\|png\|jpg\|changelog\|README.rst\|txt$')

  11 lamp/plan/main
   1 lamp/overlay/etc/skel/.bashrc.d/php-xdebug
  17 lamp/overlay/etc/apache2/mods-available/status.conf
  23 lamp/overlay/etc/apache2/sites-available/default
  10 lamp/overlay/var/www/cgi-bin/test.cgi
  73 lamp/overlay/var/www/index.php
   1 lamp/overlay/var/www/phpinfo.php
   5 lamp/conf.d/main
   1 lamp/removelist
   5 lamp/Makefile
 147 total

So I am seeing that the Overlays, are going in AFTER MAIN, and Creating Folders to Load the CONF.D /MAIN file into.  (not yet clear about removelist)

---

So Finally, Why Does the LAPP (app) not have a "conf.d" folder or "main" file in it?  I was wanting to try a Mod of Lapp.  Want to compare that set up to on w/ Nginx and one with simple Postresql  (adding Odoo on top)

I will also add my question just posted on Tracker.  Why does the Conf.d/main in the LAPP app call Lapp itself?  I would think it should perhaps call Postgresql, then add Apache/SSL to it.  I have more questions but will leave them from here.

Thanks for the post above.  It is helpful.  Somewhat daunting.  Sequence and simplicity of understanding on my side is my goal just now.