Mayursinh Sarvaiya
5c6a0356c0
* fix(docs): typos which were reflacted from vale linter's command * feat: Implement Vale linter (#2031) Initialize .vale.ini file Add 'lint:docs' script to package.json, to lint all md files except the ones which are located in node_modules Generate 'vocab.txt' by using command 'yarn run lint:docs' | grep -o ''[a-z A-Z]*'' | grep -o '[a-z A-Z]*' | sort | uniq > .github/styles/vocab.txt Add steps to github workflow 'master' to check docs quality * chore: Separate workflow for quality checking * chore: Added 'shx' dev dependency to support grep command in cross platform * feat: Add script to operate same quality check process on different platform * ignore: remove lint:docs from lint-stages which was added for experiment purpose * fix: check-all-files on push event & check-changed-files on pull_request event * chore(CI): triggle workflow only when there is any updates in .md file(s) on pull request * fix: use spawnSync to solve 'The command line is too long.' error * fix: github workflow syntax * fix: prettier error * chore: add vale command directly to lint-staged * chore: use shebang for easy access * fix: windows script issue & remove shebang * chore: Add shebang flag * chore: better error message related to vale * chore: mention vale linter in documentation * fix: spelling errors & add keywords to vocab.txt
778 B
778 B
Deploying Backstage
Heroku
Deploying to heroku is relatively easy following these steps.
First, make sure you have the heroku CLI installed and log into it as well as login into Heroku's container registry.
$ heroku login
$ heroku container:login
You might also need to set your Heroku app's stack to container
$ heroku stack:set container -a <your-app>
We can now build/push the Docker image to Heroku's container registry and release it to the web worker.
$ heroku container:push web -a <your-app>
$ heroku container:release web -a <your-app>
With that, you should have Backstage up and running!