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
I am not sure if this is fixed anywhere else, but for the initial setup, I ran in to an issue where resque is unable to clone repository due to _deploynaut_logs directory not existing. I understand this is not a fatal error, just a warning but as soon as I created that directory manually the deploynaut-php-resque was happy to clone.
ERROR [Warning]: fopen(/sites/deploynaut/www/assets/_deploynaut_logs/clonegitrepo.log): failed to open stream: No such file or directory
I have grepped through the code, but I cant see anywhere this directory being created. I had to create it manually and fix its permissions.
I was hoping this directory would get created upon /dev/build ? Therefore it might be an enhancement.
I had to run resque manually to see the above Warning.
I am not sure if this is fixed anywhere else, but for the initial setup, I ran in to an issue where resque is unable to clone repository due to _deploynaut_logs directory not existing. I understand this is not a fatal error, just a warning but as soon as I created that directory manually the deploynaut-php-resque was happy to clone.
ERROR [Warning]: fopen(/sites/deploynaut/www/assets/_deploynaut_logs/clonegitrepo.log): failed to open stream: No such file or directory
I have grepped through the code, but I cant see anywhere this directory being created. I had to create it manually and fix its permissions.
I was hoping this directory would get created upon /dev/build ? Therefore it might be an enhancement.
I had to run resque manually to see the above Warning.
sudo -u www-data ./framework/sake dev/resque/run queue=*
The text was updated successfully, but these errors were encountered: