fdbea0dcae
## Description Triggered manually from actions page using [manual trigger](https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/). @vkamra ~We will need `WEBSITE_S3_BUCKET` and `WEBSITE_CF_DISTRIBUTION` in `Production` env for this to work.~ If you could add the s3 and cloudfront details to to GitHub secrets, I'll switch to using the secrets instead. ## Type of change <!--- Please check the type of change your PR introduces: ---> - [ ] 🌻 Feature - [ ] 🐛 Bugfix - [ ] 🗺️ Documentation - [ ] 🤖 Test - [x] 💻 CI/Deployment - [ ] 🐹 Trivial/Minor ## Issue(s) <!-- Can reference multiple issues. Use one of the following "magic words" - "closes, fixes" to auto-close the Github issue. --> * fixes https://github.com/alcionai/corso/issues/1329 ## Test Plan <!-- How will this be tested prior to merging.--> - [x] 💪 Manual - [ ] ⚡ Unit test - [ ] 💚 E2E
Corso website documentation
Requirements
Building the Corso website requires the following tools on your machine:
make- Docker
Installation
make buildimage
Live documentation development
make dev
This command starts a local development server within the Docker container and will expose a live website preview at http://localhost:5050.
Building a static website
make build
This command generates static content into the dist directory for integration with any static contents hosting service. If you are using AWS S3 + CloudFront, you can run make publish to upload to the configured S3 bucket.
Website platform development
make shell
Use this command to interactively (and temporarily!) change the contents or configuration of the live website container image (for example, when experimenting with new packages).