5de4a7e75b
If we trigger a deploy, then we want the deploy to actually run. I am assuming that this was in place when there was a single GitHub Actions workflow that would trigger this all the time, even when nothing changed in `docs/**`. Since https://github.com/dagger/dagger/pull/1498, we no longer have this problem. After merging https://github.com/dagger/dagger/pull/1591, I was caught by this behaviour which to me seemed surprising. This change should make docs deploy via Netlify behave in a more predictable way. Signed-off-by: Gerhard Lazu <gerhard@lazu.co.uk> |
||
|---|---|---|
| .. | ||
| cypress | ||
| plugins/docusaurus-plugin-hotjar | ||
| src | ||
| static | ||
| .gitignore | ||
| .prettierrc | ||
| babel.config.js | ||
| cypress.json | ||
| docsearch.config.json | ||
| docusaurus.config.js | ||
| netlify.toml | ||
| package.json | ||
| README.md | ||
| sidebars.js | ||
| yarn.lock | ||
Website
This website is built using Docusaurus 2, a modern static website generator.
Installation
yarn install
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
GIT_USER=<Your GitHub username> USE_SSH=true yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.