Herbert Maschke

The only things that comes into my mind for an 1.0 production release would be: - tests (at least basic ones) - security audit (messages could always be sensible) -...

Its a year later, but i think i have a very simple workaround (or even solution?): https://github.com/robersonfaria/laravel-database-schedule/pull/57

Hey, thanks for trying yum! Did you use the 0.8 release or git master? is there a profile for the administrator in the 'profile' table ? If not, try to...

Try to add the 'role' submodule to your modules section and import the role submodule: Yii::import('applications.modules.role.models.*');

Actually there are no plans for supporting postgresql. I think for someone interested in using yum in postgres it would not be so difficult since ActiveRecord is used in most...

Postgresql support isn't actually hard to implement. Thanks to yii, In theory, we are independent of the unterlying database system. Only thing that needs to be rewritten is the installer...

Yes, thats ok! thanks a lot for your efforts.

A similar discussion is going on here: https://github.com/LunarVim/LunarVim/pull/2542 unfortunately my lua skills are not high enough to do it :( thanks a lot for that lines, @rebuilt thats what i...

I can confirm that problem and here is a *temporary workaround*: 1: empty runner sql table: ``` mariadb -u semaphore -p use semaphore; delete from runner; ``` 2: remove `runner.cfg`...

I like that idea but i want to point out that the *default* behavior should be to cancel the complete deployment process. If one likes to implement a fallback, he...