APIs like listing tasks are only available through the CLI commands (ScheduleListCommand.php)
ScheduleListCommand currently uses a hardcoded Configuration / FileSystem implementation in the generated crunzcontainer which always returns the current working directory.
When trying to invoke these methods from within an application (running in apache), the source will also resolve to getcwd.
Solution: Provide a way to specify the configuration parser when creating the application
$application = new Application('Crunz', 'v3.4.0');
APIs like listing tasks are only available through the CLI commands (ScheduleListCommand.php) ScheduleListCommand currently uses a hardcoded Configuration / FileSystem implementation in the generated crunzcontainer which always returns the current working directory. When trying to invoke these methods from within an application (running in apache), the source will also resolve to getcwd.
Solution: Provide a way to specify the configuration parser when creating the application
$application = new Application('Crunz', 'v3.4.0');