A small suggestion. You are running first command context-less (i.e. in root / htdocs etc. directory) while you must run second command context-full (in project’s folder). So actually you must run three commands in a sequence:
composer create-project --prefer-dist yiisoft/yii2-app-basic basic
composer update --ignore-platform-req=php
Any particular area you want the most help? This will be a blocker for us in the near future when 8.1 moves to support-only mode at the end of this year, so we can certainly spend some development time on contributing fixes for those issues if we have a clear picture of the process. Where’s your biggest pain point that you want to have taken care of?
Thanks Stefano =) There will definitely be more posts when I start moving things to Yii 3. The release of the database package this past weekend was a huge step forward and I can’t wait to be able to start truly using it. It was too soon the last time I dug into it and a lot has changed since then.
It is just time. With Yii3 going, I’m not able to focus on Yii2 every day personally. As for 8.2 support, try running tests. There are issues visible. When tests pass, we’ll see if there are any additional things to fix.
Trying to help run the tests and such, but I run into issues trying to run the mssql tests due to licensing and pull restrictions on those images.
Error response from daemon: pull access denied for microsoft/mssql-server-linux, repository does not exist or may require ‘docker login’: denied: requested access to the resource is denied.
All the other tests in the test-local.sh are passing or skipped, and I’m unsure whether the skipped ones are deliberate (Zend Data Cache not installed, XCache not installed, Wincache not installed, etc.) or if there’s a different base php image I should use for testing instead of the configured one for 8.2?
I’d really like to help but I feel like I’m spending ridiculous amounts of time just trying to figure out where the concerns are. Am I just missing something completely obvious?
Like I said above, many of us would like to test things but the expense of setting up things and do actual test is quiet high. If one of core dev would step in make it easy for testing and giving feedback, I for one would have done that long ago
Checked and it seems that in DBSession class there is call to $this->db->createCommand()->upsert($this->sessionTable, $this->fields)->execute(); which in Postgres calls INSERT instead of of updating it. and since there is already in the db the error arises!