An existing site: the tasks on a repo that already is an EmDash site
The tasks expect the site in a site/ folder beside mise.toml. If your repo is the site, say so under [env] in mise.toml:
[env]
SITE_FOLDER = "."
site:new and site:delete then refuse: they make and remove a folder of the site’s own, and there is none.
If the site has no seed file, also set SITE_SEED = "none", and site:check skips the seed check.
Then:
mise run site:status # where the site is now, and the task that gets it further
mise run site:start # as in Getting started
Getting started has the rest.
What the tasks change in your site
- A task that type-checks the site adds
typescript@6to its devDependencies when it has notypescript, and says so:site:check, and the tasks that run it,emdash:update,live:ship,live:previewandplugin:works. Without itastro checkasks to install it, checks nothing and ends as a success (Upstream issues). - The first task that starts or builds the site writes
EMDASH_ENCRYPTION_KEYinto its.env, with EmDash’s ownemdash secrets generate, when it is not there. plugin:sandbox, and every registry plugin task on this machine, which runs it first, editsastro.config.mjs, andwrangler.jsoncon a Cloudflare site orpackage.jsonandpnpm-workspace.yamlon a Node one.plugin:newandplugin:addeditpackage.jsonandastro.config.mjs, andlive:previeweditswrangler.jsonc: Plugins, Preview.
Limits
- No test step runs with
SITE_FOLDER = ".": the test’s sites are insite/. plugin:demoneeds collections namedpostsandpages, as EmDash’s templates have.