Hi,
I would like to have an clean Startup-Installation without «Typo3.NeosDemoTypo3Org» Site-Package from beginning. Is there an different command for composer create-project typo3/neos-base-distribution DirectoryName
So done, there is still a dead simlink to demo under Web/_Resources/Static/Packages
Perhaps I forgot a step, otherwise I can also remove it by Terminal/Hand – no problem.
But maybe there is a more simple solution without download stuff than delte/remove.
Like: composer create-project typo3/neos-empty-distribution DirectoryName
If you want to remove the demosite you should adjust your compoer.json and remove the package. A composer update should to the trick. To get the symlink removed try ./flow resource:clean and/or ./flow resource:publish
Hey stolle,
cool, and once again, thanks for all your help!
I tried your recommended commands in different sequences. and have read the docs about, also tried the combination with ./flow flow:cache:flush --force and ./flow node:repair but the simlink don’t wont pastaway.
It’s OK and not really important. I just thought, there could be a simpler and more direct way as download Demo and delete afterwards, which I have not found yet.
I delete the sim simply by hand, no effort.
After a while always removing the demo package from the base distribution, I took the time to look at the package inheritance and what I needed for a “Empty Base Package” and my composer.json ended up like this
Where you can adjust the version number of the packages.
When you add your own site package to the “require” section, you can move the typo3/neos and typo3/neos-seo dependencies into that package. Then this composer file simply contain the requirement of your site package
I’m still looking for a way to remove the scripts part, perhaps move it to the TYPO3.Flow package - it’s the part taking care of the creation of the directory and creating index.php for the Flow framework to work. With that being removed, the composer file will be super slim
The entire process who works for me.
Maybe there is a more efficient way or I misunderstood something: Comments are very welcome!
###Install a clean NEOS-Distribution :
Create a Folder in Server-Directory (e.g. «new-clean-website.neos»)
####Note for Composer-Package Distribution on Github/Bitbucket
Package includes only Site-Package. NO ANCESTORS – NO PATH: Sites/Vendor.Sitename
So the composer.json from Site-Package is in Root-Folder of Github/Bitbucket-Package
With transferring the part «“typo3/neos”: “~2.2”, “typo3/neos-seo”: “~1.0”» in own Package, there throws repeatedly an Error while installation-Process 4/5 «Missing typo3/neos-nodetypes» for Sites.xml.
With this explicit listing in require (first line)–> NO Error!
The content in composer.json in SitePackage on Github/Bitbucket: