Skip to content

Latest commit

 

History

History
91 lines (55 loc) · 3.82 KB

TODO.md

File metadata and controls

91 lines (55 loc) · 3.82 KB
  1. WIP (check origi script call dtables) - allow to call simply by a command without a wrapper script like

List of parameters -w, --webdir - public web directory document root, where to symlink the assets -p, --package - current package working directory -o, --ownAssetsDir - Own assets directory

-1 - -w - WebDir parameter not supplied, is mandatory, exiting ... root@4d5d53247275:/var/www/html/fantomx1/ToolMasterForeman# PHP_IDE_CONFIG="serverName=server_name" php vendor/fantomx1/packages-assets-support/initAssets.php -w=examples/assets -p=./ -o=./testAssets

2 ) done, error codes handling

3 ) find dir reversely from shortcut to the long name -0 => -ownPackageDir

4 ) (Note: In future can be added functionality of publishing only the specific asset part of the other library, however this library is not intended to solve intricacies of other libraries assets, since they can share just this library to solve their issues, though it might be added later)

5 ) automatically regard the current package - remove param p?, only if it in our library so not passed parameter , done

6 ) add unknown parameter supplied

7 ) separate nubered indents by dots

8 ) refactor other object plus inner loop and closures and eventually exceptions flow of condtions and exxceptions types else clauses without negative interuptions

old readme

/var/www/html/fantomx1/ToolMasterForeman# php vendor/fantomx1/packages-assets-support/initAssets.php  -w=examples/assets -p=./ -o=./testAssets
  • where the "-p -package" - references relatively the curret package it is used in (toolmasterForeman)
  • where the "-w -webdir" - comma separated references the directories where to distribute/publish assets using symlinks
  • -- where the "-o -ownPackageDir" - defines own relative assets directory if we wish to publish this way also our assets directory, this is almost exclusively used if we use own project as a library (obsolete, now automatically takes getcwd) --
  1. functionality of blocking - if it contains already a similar frontend library, not to clash

  2. include recursively other libraries too, better to list and execute commands for each such dependency explicitly at the time being for the gain/work ratio

  3. use for all the libraries same subdirectory, though the versions might clash, as they don't happen to be always in the library name, though on the other-side it's execution namespace could clash anyway in the first place

  4. if is deeper than in document root directory, those assets, or shared between via alias

  5. add prefix for deeper or an alias ,eg frontend launch script backend/web/script/index.php and assets ../assets, like backend/web/assets/ or alias imges = /tmp , so move everything to web and add alias imges

  6. // or just pass similary a multiple webdirs with or pass abolutely and multiple and check add to docs
    @TODO:
    

// if (basename(dirname($webDir, 3)) == "vendor") { // $webDir = "/../../".$webDir; // }

  1. a install i ci nie zbytocne

  2. dont throw error but order of errors not owerwritten, take second only if not earlier error //if (!$error && empty($params['p']) && !$currentPackageDir) { // if (!$error && !$currentPackageDir && empty($params['p']) ) { // $error = -2; // }

// if (!$error && !$ownPackageAssetsDir && empty($params['o']) ) { // $error = -3; // }

  1. check if still works on frontends and with backtrace bt getAssetsDir add call to dtables

  2. a rozlisenie inych vstupnych podmienok aj i takto

  3. todo check that it is already in the composer.json to be it more transparent, though in parent directory it doesn't have to eb deployed anywhere yet, update docs

  4. todo readlink xargs for the

  5. support for htaccess mod rewrite paths as controllers etc, which bypass such structure for images