coapp-developers team mailing list archive

[Garrett Serack <garretts@xxxxxxxxxxxxx>]

Bottom Poster!???!! Arg!  I preferred bottom-posting, but in my world, it's just not done.



>> $base_web_location/<vendor>/<package>/<version>



...\applications\<vendor>\<package-version> or ... \applications \<vendor>\<package>\<version>?



Package-version as the dir name is a bit more traditional, I think.



>> As to the last issue - the idea of "useful scripts"



I added a package spec for "System tools & shared utilities" ... in where I expect all of these types of packages to install to a common /bin directory somewhere. Is that what you're thinking of?





>>  To further complicate things there is the idea of things in the PHP that script libraries like PEAR and Zend Framework...



Ah. Yes.Hmmm.



How about ...\libraries\<vendor>\<package-version> for shared 'web libraries' like PEAR.

This makes the tree (and increases the necessity for \sites , \applications and \libraries)

inetpub

├───applications

│   ├───CoApp

│   │   ├───Gallery-2.0.7

│   │   └───phpBB-3.0.2

│   └───WordPress

│       ├───WordPress-4.3.6

│       └───WordPress-4.3.7

├───libraries

│   ├───Adodb

│   │   └───AdoDB-2.5.6

│   └───Zend

│       └───ZendFrameworks-2.4.1

└───sites

    ├───bar.com

    ├───baz.org

    └───foo.com

_______________________________________________

Mailing list: https://launchpad.net/~coapp-developers

Post to     : coapp-developers@xxxxxxxxxxxxxxxxxxx<mailto:coapp-developers@xxxxxxxxxxxxxxxxxxx>

Unsubscribe : https://launchpad.net/~coapp-developers

More help   : https://help.launchpad.net/ListHelp



Ack - top-posting ;)

Yes, I really think that web applications need their own package, putting them in program files is not only a pain because they might need to write to configuration files/generate images/do other bad stuff but it's also a security issue.  For example apache makes you set up specific
locations that are allowed to run scripts.  I do NOT want that to be in program files but somewhere else I can keep a tighter lock and key on.

In the PHP world GOOD application typically do NOT put their scripts in the web root, but parallel to it (take a look at the general structure that zend framework uses) - basically it sets up their own sub tree of /application /config /lib /htdocs/www/whatever we call it this week (the actual web root)

some kind of setup that uses $base_web_location/<vendor>/<package>/<version> would work fine, with each package having it's own webroot and virtual host

As to the last issue - the idea of "useful scripts" - maybe there needs to be a place for general command line scripting stuff, as opposed to lumping all 'desktop applications' together.  To further complicate things there is the idea of things in the PHP that script libraries like PEAR and Zend Framework are installed to program files somewhere - and then web applications that are installed put them into their include_paths.  In essence you're installing a "library" - but it's going to have much different usage needs and patterns then a traditional library/.dll

Ugh - too many ways to do things.

Thanks,
Elizabeth M Smith