You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that may be troublesome with a .phar file is some enhancements I have planned, including #19 (using local MODX zips instead of always downloading from MODX.com to speed things up), will rely on writing to a central gitify folder. I was thinking of doing that inside the gitify folder itself, but if it's turned into a .phar, I'm not sure if that's still possible.
@Mark-H Best way for store modx zips - use folder with leading dot in the name.
Gitify can create .gitify folder in users /home and store data to this folder. And then use data from this folder. The same way use composer for cache packages.
To make installation easier, it'd be great to compile Gitify into a PHP Archive, to make installation on remote/production servers easier.
I've yet to do this (may attempt as an interesting exercise) but would probably use Composer's compiler as a template: https://github.com/composer/composer/blob/c573ae57810e98f60e810e5d1a920a51c12c8ebc/src/Composer/Compiler.php
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: