Raphael Piccolo
Raphael Piccolo
| Or it could omit the dependency completely, which is not a bad idea, since it will pick it up again once the min-age has passed => i like it....
> Do you wish to include betas, and pre-releases, or only stable versions? I dont really care as long as the package is old enough to be considered for update...
I found a way for the autoupdate. Would be good to have it in the readme no ? npm install -g forever have an autostart on reboot @reboot cd /home/flood/site...
note that if call spinners.succeed("spinner-1"); before or instead of remove it works.
this is not related to this lib. if you replace ``` process.stdout.write('^C received\n'); ``` with ``` console.log('^C received\n'); ``` the message appears.
usually CI logs are not ncurse capable. therefore i guess spinners just adds lines to the log instead of rewriting current lines.
I tried it. and it's not a drop in replacement for docker compose config. (although it may solve some bugs like ports format) In this example i can see that...
FWIW docker seems to believe that the real solution is to source .env in the real env https://github.com/docker/compose/issues/9306#issuecomment-1212522308 when you do this can get rid completely of "docker compose config"...
- yes a new watcher makes sens. - yes my dockerfile and compose files update inplaces and i commit them to trigger deploys. for exemple if i have this at...
why would you put ** before garbage.php ? i get better results without this