96efc44b82
* Chore: Feature lock email settings in UI The email settings under account settings needed to be feature locked in a way different from teh current way for it to be enabled for accounts in a self hosted scenario. Some refactorings were also done along with this change. 1. There was a feature flag defined in code in account model called domain_emails_enabled was used to check if the inbound emails was enabled for the account. But there was already a feature flag called "inbound_emails" defined in features.yml. So changed to use this to check if inbound emails are enabled for an account. 2. Renamed and re-purposed existing `domain_emails_enabled` to `custom_email_domain_enabled` to use for feature toggling the UI for email settings. 3. To enable & disable multiple features using the featurable concern we were passing an array of values. Changed this to accept a comma separated set of values. * Chore: Feature lock email settings in UI Fixed the specs for accounts controller & removed unneccessary code from Account seetings component in UI * Chore: Convert newlines to <br>s Removed the layout used while sending replies in conversation continuity. Converted the newlines in the messages to <br/> tags for the correct HTML rendering. * Chore: Bug fix in reply email domain Renamed the function custom_email_domain_enabled to inbound_email_enabled. Fixed bug on setting reply emails's domain. |
||
|---|---|---|
| .circleci | ||
| .dependabot | ||
| .github | ||
| __mocks__ | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| deployment | ||
| docker | ||
| docs | ||
| lib | ||
| log | ||
| public | ||
| spec | ||
| swagger | ||
| tmp | ||
| vendor/assets | ||
| .all-contributorsrc | ||
| .browserslistrc | ||
| .codeclimate.yml | ||
| .dockerignore | ||
| .editorconfig | ||
| .env.example | ||
| .eslintrc.js | ||
| .gitignore | ||
| .nvmrc | ||
| .prettierrc | ||
| .rspec | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-version | ||
| .scss-lint.yml | ||
| app.json | ||
| babel.config.js | ||
| Capfile | ||
| config.ru | ||
| crowdin.yml | ||
| 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 | ||
| semantic.yml | ||
| workbox-config.js | ||
| yarn.lock | ||
Background
Chatwoot is a customer support tool for instant messaging channels which can help businesses provide exceptional customer support. The development of Chatwoot started in 2016. It failed to succeed as a business and eventually shut up 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 this time, 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.
Branching model
We use the git-flow branching model. The base branch is develop.
If you are looking for a stable version, please use the master or tags labelled as v1.x.x.
Heroku one-click deploy
Deploying chatwoot to heroku is 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
Follow our docker development guide to develop and debug the application using docker-compose.
Follow our environment variables guide to setup the environment for Docker.
Contributors ✨
Thanks goes to all these wonderful people:
Chatwoot © 2017-2020, ThoughtWoot Inc - Released under the MIT License.