Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

KUNST-72: The big upgrade #68

Merged
merged 49 commits into from
Aug 10, 2023
Merged

KUNST-72: The big upgrade #68

merged 49 commits into from
Aug 10, 2023

Conversation

rimi-itk
Copy link
Contributor

@rimi-itk rimi-itk commented Aug 1, 2023

https://jira.itkdev.dk/browse/KUNST-72

Upgrades to

  • PHP 8.1
  • Symfony 6.3

Assets, i.e. Webpack and the like, are not yet upgraded.

The commit history is a mess and we should rebase into a single commit if this is ever approved (or squash when merging).

@rimi-itk rimi-itk marked this pull request as ready for review August 2, 2023 14:06
@rimi-itk rimi-itk requested review from tuj and jekuaitk August 2, 2023 14:09
.env Outdated
DATABASE_URL=mysql://db:db@mariadb:3306/db
# Override to use mariadb as backend
DATABASE_SERVER_VERSION='mariadb-10.3.13'
###< doctrine/doctrine-bundle ###

APP_SECRET=NotSoSecretReplace
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

APP_SECRET defined two times in the file

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in f734d86.


# Build assets using our development setup
docker compose run --rm node yarn install
docker compose run --rm node yarn build
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and remove the node_modules folder

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed in 84c6466.

public function up(Schema $schema): void
{
// The migration_versions table exists only if upgrading, i.e. not making a fresh install.
$this->addSql('DROP TABLE IF EXISTS migration_versions');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this needed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've updated the comment above the line with more details and a reference to https://github.com/doctrine/DoctrineMigrationsBundle/blob/3.2.x/UPGRADE.md#from-2x-to-300 (cf. 5a80bb3).

How de we usually handle this situation? Do we add configuration to keep the migration_versions table name?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"and existing database" => "an existing database"

@rimi-itk rimi-itk requested a review from tuj August 3, 2023 11:00
@rimi-itk rimi-itk changed the title KUNST-72: The all in one go upgrade KUNST-72: The big upgrade Aug 4, 2023
@rimi-itk rimi-itk merged commit d03ff70 into develop Aug 10, 2023
6 checks passed
@rimi-itk rimi-itk deleted the feature/KUNST-72-update branch August 10, 2023 13:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants