2168f823a5
Previously we did not support authentication for redis anywhere. Also in the docker compose we were exposing redis port 6379 without any authentication. In the app side for the connections that app server (for storing keys as well as for socket connections made using action cable) and Sidekiq were making to redis server did not support authentication. With this commit, we support authentication for redis connections from app side and Sidekiq. This is supported in docker-compose as well. The changes include : * Added support for new env variable REDIS_PASSWORD * This redis password is now supported by action cable connections, Sidekiq connections and app side redis connections * Since Sidekiq did not have an initializer, added an initializer to pass custom config to Sidekiq (for now it's options for redis) * Changes in docker-compose to pickup a password set in .env file to protect the redis server running in docker * Added necessary documentation changes in `docker.md` and `environment-variables.md` |
||
|---|---|---|
| .circleci | ||
| .dependabot | ||
| .github | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| docker | ||
| docs | ||
| lib | ||
| log | ||
| public | ||
| spec | ||
| tmp | ||
| vendor/assets | ||
| .all-contributorsrc | ||
| .browserslistrc | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .eslintrc.js | ||
| .gitignore | ||
| .prettierrc | ||
| .rspec | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-version | ||
| .scss-lint.yml | ||
| app.json | ||
| babel.config.js | ||
| Capfile | ||
| config.ru | ||
| docker-compose.production.yaml | ||
| docker-compose.yaml | ||
| Gemfile | ||
| Gemfile.lock | ||
| jest.config.js | ||
| LICENSE | ||
| package.json | ||
| postcss.config.js | ||
| Procfile | ||
| Procfile.dev | ||
| Rakefile | ||
| README.md | ||
| workbox-config.js | ||
| yarn.lock | ||
Background
Chatwoot is a customer support tool for instant messaging channels which can help businesses to provide exceptional customer support. The development of Chatwoot started in 2016 and it failed to succeed as a business and eventually shut the shop in 2017. During 2019 #Hacktoberfest, the maintainers decided to make it opensource instead of letting the code rust in a private repo. With a pleasant surprise, Chatwoot became a trending project on Hacker News and best of all, got lots of love from the community.
Now, a failed project is back on track and the prospects are looking great. The team is back to working on the project and we are building it in the open. Thanks to the ideas and contributions from the community.
Documentation
Detailed documentation is available at www.chatwoot.com/docs.
You can find the quick setup docs here.
Heroku one-click deploy
Deploying chatwoot to heroku, it's a breeze. It's as simple as clicking this button.
Follow this link to understand setting the correct environment variables for the app to work with all the features. There might be breakages if you do not set the relevant environment variables. This applies to deploying the docker image as well.
Docker
You can use our official Docker image from https://hub.docker.com/r/chatwoot/chatwoot
docker pull chatwoot/chatwoot
Follow our environment variables guide to setup environment for Docker.
Follow our docker development guide to develop and debug the application using docker composer.
Contributors ✨
Thanks goes to all these wonderful people:
Chatwoot © 2017-2020, ThoughtWoot Inc - Released under the MIT License.