Neos Con 2023: Migrating a Project to Neos 9

Transcript

1. Migrating a Project to Neos 9
2. 1 2 3 4 5
3. Update to Neos 8.2 or 8.3 ...and PHP 8.1 or 8.2 1
4. { "name": "neos/docs-neos-io-distribution", "config": { "platform": { "php": "8.1", "ext-vips": "1.0.9" }, }, "require": { "php": "^8.1", "neos/neos": "~8.2.0", "neos/neos-ui": "~8.2.0" } } required recommended makes composer run more deterministic
5. { "name": "neos/docs-neos-io-distribution", "config": { "platform": { "php": "8.2", "ext-vips": "1.0.9" }, }, "require": { "php": "^8.2", "neos/neos": "~8.2.0", "neos/neos-ui": "~8.2.0" } } I like 8.2 :)
6. deprecation / strict errors will still be fi xed in Neos/Flow PHP 8.2 workaround php.ini
7. test the update 1a
8. require Neos 9.0 (dev) 2
9. { "name": "neos/docs-neos-io-distribution", "config": { "platform": { "php": "8.2" } }, "require": { "php": "^8.2", "neos/neos-development-collection": "9.0.x-dev", "neos/flow-development-collection": "8.3.x-dev", "neos/neos-ui": "9.0.x-dev", "neos/neos-ui-compiled": "9.0.x-dev", "neos/eventstore": "@dev", "neos/eventstore-doctrineadapter": "@dev" } } no stable releases yet no 9.x Flow branch yet no package splits active yet
10. shel/neos-terminal is missing neos 9 compatibility fl owpack/media-ui is missing neos 9 compatibility
11. Option 2: Remove the package and add it to the ToDo list. Option 3: Fork the package, raise the version, and pull request. Option 1: Check if the package has already a Neos 9 compatible version.
13. hmmm. we need assets (CSS/JS).
14. Option 2: Remove the package and add it to the ToDo list. Option 3: Fork the package, raise the version, and pull request. Option 1: Check if the package has already a Neos 9 compatible version.
16. { "require": { "carbon/includeassets": "dev-master as 5.5.0" }, "repositories": { "distribution": { "type": "path", "url": "./DistributionPackages/*" }, "Carbon.IncludeAssets": { "type": "vcs", "url": "https://github.com/skurfuerst/Carbon.IncludeAssets" } } } reference the forked repo before, we had version 5.5.0 installed; and we want to replace this version with our fork
17. YAY :)
18. ./ fl ow help 3
19. :(
20. neos/rector 3a
23. return static function (RectorConfig $rectorConfig): void { $rectorConfig->sets([ NeosRectorSets::CONTENTREPOSITORY_9_0 ]); $rectorConfig->paths([ // TODO: Start adding your paths here, like so: __DIR__ . '/DistributionPackages/', __DIR__ . '/Packages/Plugins/Jonnitto.PrettyEmbedHelper', __DIR__ . '/Packages/Carbon/Carbon.IncludeAssets', __DIR__ . '/Packages/Carbon/Carbon.Link', ]); }; I needed to auto-migrate some more packages
24. set up the content repository 4 ./ fl ow cr:setup
25. import legacy data 5 ./ fl ow cr:migrateLegacyData
28. run & test 6 ./ fl ow server:run
32. Slack: #project-cr-rewrite github.com/neos/neos-development-collection/ => new issue marked with 9.0 github.com/neos/rector
33. APIs
34. API Basics en de ContentGraph ContentSubgraph ContentSubgraph Node NodeAggregate
35. ContentRepository + Registry
36. NodeInterface -> Node
37. Node
38. Node Traversal
39. Fusion
40. Fusion
41. Fusion
42. Fusion
43. Dimension Con fi guration Neos: ContentRepositoryRegistry: contentRepositories: default: contentDimensions: language: label: Languages icon: icon-language values: en: label: English de: label: German no more "presets"
44. Site Con fi guration Neos: Neos: sites: '*': contentDimensions: resolver: factoryClassName: Neos\Neos\FrontendRouting\DimensionResolution\Resolver\ UriPathResolverFactory options: segments: - dimensionIdentifier: language # dimensionValue => uriPathSegment (empty uriPathSegment allowed) dimensionValueMapping: en: '' de: 'de'
45. Summary