# |
Dec 14th 2019, 19:25 |
luizcmarin |
need help solving these two items just |
# |
Dec 14th 2019, 19:24 |
luizcmarin |
I learned that I should not change the content of 'vendor'. So how to solve it? |
# |
Dec 14th 2019, 19:13 |
luizcmarin |
The first error are deprecated messages. I don't want to disable them. I want to solve them. |
# |
Dec 14th 2019, 19:13 |
luizcmarin |
pardon. |
# |
Dec 14th 2019, 19:13 |
luizcmarin |
o primeiro erro são de mensagens deprecated. Não quero desabilita-las. Quero resolve-las. |
# |
Dec 14th 2019, 19:10 |
luizcmarin |
@admad @sean.kelly I appreciate your help. I understood how to solve this kind of problem. But there are two I can't. See this picture: |
# |
Dec 14th 2019, 18:08 |
luizcmarin |
thanks you |
# |
Dec 14th 2019, 17:10 |
sean.kelly |
Hi @luizcmarin: change `public function middleware($middlewareQueue)` to `public function middleware(MiddlewareQueue $middlewareQueue`. ;) |
# |
Dec 14th 2019, 14:27 |
admad |
https://github.com/cakephp/app/blob/4.x/src/Application.php#L66 |
# |
Dec 14th 2019, 14:25 |
luizcmarin |
@admad I tried to understand what to do .... but.... |
# |
Dec 14th 2019, 14:22 |
admad |
add the typehints as expected |
# |
Dec 14th 2019, 14:21 |
admad |
error message already contains the solution to the problem |
# |
Dec 14th 2019, 14:20 |
luizcmarin |
and now? |
# |
Dec 14th 2019, 14:19 |
luizcmarin |
*/ public function middleware($middlewareQueue) { $middlewareQueue // Catch any exceptions in the lower layers, // and make an error page/response ->add(new ErrorHandlerMiddleware(null, Configure::read('Error'))) |
# |
Dec 14th 2019, 14:19 |
luizcmarin |
in my file: |
# |
Dec 14th 2019, 14:19 |
luizcmarin |
Fatal error: Declaration of App\Application::middleware($middlewareQueue) must be compatible with Cake\Http\BaseApplication::middleware(Cake\Http\MiddlewareQueue $middleware): Cake\Http\MiddlewareQueue in C:\marin\www\ola\src\Application.php on line 63 |
# |
Dec 14th 2019, 14:19 |
luizcmarin |
hi, |
# |
Dec 14th 2019, 14:16 |
admad |
why should it be integrated into core? the skeleton app already has support for it |
# |
Dec 14th 2019, 13:29 |
dsar |
When php-dotenv will be integrated in the core? |
# |
Dec 14th 2019, 11:07 |
dsar |
Automation is usually blind :) of course with some exceptions |
# |
Dec 14th 2019, 10:49 |
noel |
@dsar I'm talking about continuous integration (CI). This generally means automated deployments via something like Jenkins to an environment. I don't really know what you mean by "blindly". |
# |
Dec 14th 2019, 10:42 |
challgren |
The initial machine setup shouldn't be blindly setup but after that it should |
# |
Dec 14th 2019, 10:41 |
dsar |
What do you mean by automate deployments? In my opinion the deployment is not something that is convenient to (blindly) automate |
# |
Dec 14th 2019, 10:37 |
challgren |
For our app, we use env vars so our app_local mainly includes env(‘var’) in it and we just commit it. |
# |
Dec 14th 2019, 10:36 |
noel |
So... one can't fully automate deployments then? |
# |
Dec 14th 2019, 10:35 |
challgren |
Like `app_local.php` you’d create it manually and upload it. app_custom.php would be in git |
# |
Dec 14th 2019, 10:34 |
noel |
Ok... so then how do I deploy the local config for a given env? E.g. 'app_staging.php`? |
# |
Dec 14th 2019, 10:34 |
challgren |
https://github.com/cakephp/app/blob/master/src/Console/Installer.php |
# |
Dec 14th 2019, 10:33 |
challgren |
https://github.com/cakephp/app/blob/master/composer.json#L38 |
# |
Dec 14th 2019, 10:33 |
noel |
oh |
# |
Dec 14th 2019, 10:33 |
challgren |
when you run composer install its copied from app.default.php |
# |
Dec 14th 2019, 10:32 |
noel |
@challgren thx – I read it but I'm not really understanding how to deploy `app.php` – it's not part of the shell script. So how would it be created for a given deployment? |
# |
Dec 14th 2019, 10:29 |
noel |
I'm trying to achieve that when deploying an app I don't have to manually write an app.php file for that environment each time. |
# |
Dec 14th 2019, 10:28 |
dsar |
What are you trying to achieve? |
# |
Dec 14th 2019, 10:25 |
challgren |
https://sandbox.dereuromark.de/pages/best-practices is a good doc about Config |
# |
Dec 14th 2019, 10:25 |
challgren |
Not really because if you have machine specific stuff such as API logins you dont want that in git |
# |
Dec 14th 2019, 10:23 |
noel |
I'm not understanding `/config/app.php` is in `.gitignore` when the documentation says: "The application skeleton features a config/app.php file which should contain configuration that doesn’t vary across the various environments your application is deployed in." Surely that means one wants `app.php` to be deployed to all environments and therefor it should be in the git repo? |
# |
Dec 14th 2019, 10:22 |
noel |
@dsar I wanted some custom setting actually, namespace was just an example. |
# |
Dec 14th 2019, 10:22 |
noel |
Ok found the answer. ```use Cake\Core\Configure; Configure::read('App.myConfigSetting')``` |
# |
Dec 14th 2019, 10:21 |
dsar |
You shouldn't access that variable in views since it defines internal stuff, what are you trying to achieve? |
# |
Dec 14th 2019, 10:08 |
noel |
App.php defines some stuff like: ```'App' => [ 'namespace' => 'App',``` How can I access these in a view / template? |