Deploy will write a deploy-local-initialize marker file after creating a new database on a fresh local project, but this is only picked up by the custom NoNodes page (this file is deleted and a deploy marker file is created to trigger a metadata deployment).
If the project includes a package migration with content (and publishes the content in a post-migration, like Umbraco.TheStarterKit), this doesn't happen though (as the NoNodes page isn't shown): the deploy-local-initialize marker file is left untouched and no deployment is triggered.
Umbraco 9.3.1
Umbraco Deploy 9.2.3
On a clean project, install Umbraco.TheStarterKit and run the site: it will create the deploy-local-initialize marker file, but not trigger a deployment after starting up.
Deploy should still trigger a deployment after creating the database and an automatic package migration adding content, just like it would do on an empty site.
Actual resultThe deploy-local-initialize marker file is left untouched and no deployment is triggered.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4