No description
An external broker is more stable, this is something I did not know as a beginner. Especially because the embedded broker has a memory leak. It would have saved me a bunch of time and WAF trust issues if I would have had this piece of knowledge. Issue on memory leak: https://github.com/home-assistant/home-assistant/issues/11594 |
||
|---|---|---|
| .github | ||
| .themes/classic | ||
| _deploy@69146ecaf4 | ||
| credits_generator | ||
| plugins | ||
| sass | ||
| source | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .powrc | ||
| .project | ||
| .ruby-version | ||
| .slugignore | ||
| .travis.yml | ||
| _config.yml | ||
| CLA.md | ||
| CODE_OF_CONDUCT.md | ||
| config.rb | ||
| config.ru | ||
| Gemfile | ||
| Gemfile.lock | ||
| LICENSE.md | ||
| Rakefile | ||
| README.markdown | ||
Home Assistant website
This is the source for the Home-Assistant.io website.
Setup
Setting up to contribute to documentation and the process for submitting pull requests is explained here.
Site preview
In order to make the preview available on http://127.0.0.1:4000, use the command as follows:
bundle exec rake preview
Speeding up site generation
Every release we post long changelogs to the website. This slows down generation of the website significantly! We include some tools to temporarily exclude the blog posts that you're not working on out of the way.
bundle exec rake isolate[filename-of-blogpost]
When you're done working on the site, run the following command to move the posts back again:
bundle exec rake integrate