Chatwoot - Simple and elegant live chat software

[andirahmat]

@sojan_official Hi. Any update on this?

[jdaviescoates]

@andirahmat I've just created an issue on GitHub to remind @sojan_official about this

https://github.com/chatwoot/chatwoot/issues/1989

[sojan_official]

Apologies for losing track on this one. We will get this prioritized !!!

@jdaviescoates Thanks for the reminder.

[jdaviescoates]

@sojan_official you're very welcome! thanks for all your great work

[girish]

@sojan_official I saw you guys joined YC. Congrats! And let us know if you need any help about the package.

[timconsidine]

@sojan_official I hope this is not a nuisance question, just checking in on the status of chatwoot for Cloudron appstore.

[Side note : I had a bash at installing self-hosted docker on a separate VPS but ran into couple issues. But didn't take notes, so can't recall clearly what. Sorry, I'm an idiot. I thought the Cloudron release might solve the issue.]

[sojan_official]

Thanks a lot for the patience . We have some work happening on this at the moment. Please feel free to take a look at https://github.com/chatwoot/cloudron-chatwoot

[timconsidine]

@sojan_official hey, no problem, very grateful for your time.

I will look at this very shortly, many thanks.

[v_shnu]

@girish Could you please take a look and provide some early feedback? What are the next steps to get this published to Cloudron app store ?

ref: https://github.com/chatwoot/cloudron-chatwoot

[timconsidine]

@sojan_official thank you again, and some feedback.

Build runs very smoothly.
Installs to cloudron via CLI but stuck on "Wait for Health Check".
App stuck in "Starting ..."
I'm trying to diagnose, but thought I would report it.
Maybe someone can see cause more quickly than I can.

[timconsidine]

@timconsidine looking at logs, I don't understand all messages, but couple things I notice below.
Could be red-herrings, hope they're not a wild goose chase.

1. host name is not the app url

box:shell reload spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
box:shell reload (stdout): sudo: unable to resolve host ssdnodes-612cb793ae148: Name or service not known

2. keybase

/gems/ruby/3.0.0/gems/railties-6.1.4/lib/rails/application.rb:603:in `validate_secret_key_base': Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit` (ArgumentError)

pid=67 tid=4kf WARN: ArgumentError: Missing `secret_key_base` for 'production' environment, set this string with `bin/rails credentials:edit`

[timconsidine]

@timconsidine I just tried installing 2 other custom apps in order to test my general setup

First one (focalboard) went through fine and is running.

2nd one (papercups) : also failed with host name issue.
But I packaged papercups myself and I don't really have any experience in this.

Investigating further ...

[v_shnu]

@timconsidine Could you please pull the latest changes and try again?

[timconsidine]

@v_shnu will do later today, thank you

[timconsidine]

@v_shnu
Builds fine
But cloudron install --image xxxx gives me :

Failed to install app: 500 message: ER_TRUNCATED_WRONG_VALUE_FOR_FIELD: Incorrect string value: '\xF0\x9F\x94\xA5\xF0\x9F...' for column 'manifestJson' at row 1

Seems to be some encoding issue but can't track it down
Looking further ...

[timconsidine]

I think it was inclusion of emojis in CloudronManifest.json
Removed them and it installs
And .... I get "app installed".
Thank you
Now going to test it out

[v_shnu]

@timconsidine Sorry about that. Forgot to push that change

[timconsidine]

@v_shnu No problem !

[timconsidine]

@v_shnu app installs nicely now
I can run it and set it up in the app webpage.
But strangely I notice that the .env file in /app/data gets reset to default values after re-starting the app.
The changes are saved when I edit the file and save.
But then restarting the app resets the .env to default values (mostly blank).
Presumably this is not correct ?

Although some settings in the app persist, so some db integration working

[timconsidine]

I think the reset of .env to defaults is because in the start.sh script there is this line

cp /app/.env.example /app/data/.env

Ideally this should be on a run once basis

so I adapted the start.sh by checking for .env existence

if [[ ! -f "/app/data/.env" ]]; then
        cp /app/.env.example /app/data/.env
fi

Let's see if that works.