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
{{ message }}
This repository has been archived by the owner on Nov 9, 2021. It is now read-only.
what do you think about using phar as default way to use phrozn? If we use an approach similar to composer install script could be more simple to start a project with Phrozn.
👍 I have the same vision. Phrozn should work as stand alone tool which should not be installed on system globally. We have already achieved this after moving to Composer. But having phar would be even better. I had plans to work on this issue someday, but while somebody "having plans", somebody else is working already :-) Thumbs up!
P.S. Also need to implement phar lifetime as Composer has. But this is more related with phar building itself:
...// add warning once the phar is older than 30 daysif (preg_match('{^[a-f0-9]+$}', $this->version)) {
$warningTime = time() + 30*86400;
$stub .= "define('COMPOSER_DEV_WARNING_TIME', $warningTime);\n";
}
...
Hi guys,
what do you think about using
phar
as default way to use phrozn? If we use an approach similar to composer install script could be more simple to start a project with Phrozn.Look this:
$ curl -s http://www.phrozn.info/installer/ | php $ php phrozn.phar init $ php phrozn.phar update
or with an existing project
It is simple and looks great imho...
The
phrozn-site
can host the installer (I propose a PR later...)I also attach the composer install script refactored to Phrozn purposes.
The text was updated successfully, but these errors were encountered: