-
Notifications
You must be signed in to change notification settings - Fork 0
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
Conversation
b60b50b
to
26306f2
Compare
26306f2
to
1664486
Compare
ddc488e
to
e18c3d6
Compare
e18c3d6
to
bec2f4c
Compare
.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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this needed?
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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"
5a80bb3
to
b2d17ca
Compare
feature/KUNST 72 update assets
https://jira.itkdev.dk/browse/KUNST-72
Upgrades to
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).