That is basically the neos base distribution one, and that is the correct place to start your own production deployment
composer.json. You maybe should give it an own name instead of “neos/neos-base-distribution” though.
Now what you need to do is, remove the neos/demo site package, the site-kickstarter, the ui-compiler and what is “neos/test”? You don’t need those in production. Also remove the require-dev section.
Then you add your own site package as a dependency, e.g “acme/cool-site”. You can then either provide that yourself via a git repository that you map in composer like here (https://getcomposer.org/doc/05-repositories.md#using-private-repositories)
you use the “DistributionPackages” folder inside the distribution directly. You just need to place your own site package inside (e.g.
./DistributionPackages/Acme.CoolSite with it’s own composer giving it the name “acme/cool-site” or whatever you call your package) and then commit and deploy it together with the composer.json. Composer will then find the dependency to your site package from that source folder and it will work out of the box, even with multiple packages side by side.
For more information on that aproach, take a look at https://github.com/kitsunet/composer-mono-project which is basically the same setup and explains the reasons for doing it that way.