Chore: Support Github Codespaces

[sojan-official]

This PR builds on top of the previous work which we did for GitHub codespace. Now that publically accessible ports are available in codespaces, You can get a complete chatwoot development environment up and running in a few minutes.

Changes

• Bump up the Ruby version of the Chatwoot app ( since the base image published for codespace is on 2.7.3)
• Github action to publish the base image to container registry
• Move the steps in the old Dockerfile to the base image, so the codespaces now boot up super fast.

Notes

• The base image used currently published under my personal Github. Let's change that to chatwoot in a subsequent PR after we get this one merged.

Instructions to test

Creating Codespace

• Head over to your codespaces section in GitHub and create a codespace for chatwoot:chore/codespace
• GitHub will open up the codespace in VSCode once the build finishes

Booting for the First Time

• In the ports tab in the visual studio, add 3000, 8025 and make them public

• Edit the .env file and update the following values

  • update frontend URL environment variable with the public URL for port 3000 ( copy from vs code ports tab)
  • update values for Postgres, Mailhog and Redis hosts to localhost ( to be automated in future)

• In terminal run bundle exec rake db:reset

• run yarn

Development Workflow

• start rails server by running overmind start -f Procfile.dev
• load the public URL for port 3000, and your chatwoot instance will available to test the changes

Notes

• You can access the emails using the public URL for Mailhog (port 8025)
• When using a ruby debugger, use overmind connect backend or overmind connect worker
• if you see webpack manifest error, wait a minute for the asset complication to finish

---

chatwoot-codespace.mp4

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.