Cloudron Forum

I just wanted to share what a great addition the Outline app has been to the Cloudron catalog. It’s been a fantastic tool, and the Cloudron packaging has been seamless. Thanks for making this available!

While these two relevant issues (https://github.com/calcom/cal.com/issues/3026 and https://github.com/calcom/cal.com/issues/6780) remain open, it looks like a PR was merged and released in 2.9.5 a few weeks ago that addressed both of these: "feat: Make database optional when building" (https://github.com/calcom/cal.com/pull/8561)

I saw a mention of BotPress integrated with Chatwoot in their documentation on AgentBots at https://www.chatwoot.com/docs/product/others/agent-bots/#implementation-examples

I haven’t tried this out, so it’s not an endorsement, but I did want to highlight that in addition to its standalone capabilities, BotPress may integrate with and complement Chatwoot.

@nebulon We recently set up Chatwoot, and it's been great so far!

The work to support the IMAP Email Channel that was discussed in this thread has since been finished and released. I was able to configure an Email Channel with IMAP and SMTP details using a Google account, so presumably this could work with Cloudron email now, too. This allowed me to set up a dedicated email address for Chatwoot-based support.

The one piece that I wasn't able to get configured fully was the "conversation continuity" discussed above. I'm still seeing the "Forward to Email" address provided by Chatwoot as xxxxxxxx@false. It's not clear to me if some configuration with Cloudron Email (for the inbound email service) might address this, but it seems worth revisiting now that the IMAP integration is in place.

@girish said in Using the n8n CLI:

I put this in the docs as well - https://docs.cloudron.io/apps/n8n/#cli

In the docs, it could be helpful to linking "n8n CLI" to the documentation link: https://docs.n8n.io/reference/cli-commands/

I wasn't ultimately able to get this to work, but uninstalling and reinstalling the Cal.com app from the Cloudron App Store gave me access to the admin onboarding flow, which did let me set up Google Calendar correctly.

@nebulon Thank you! Great to hear. Happy to say that our custom skin loads properly.

Wanted to note that the optionalSso change here allowed me to fix my Google Login issue, too! https://forum.cloudron.io/post/77654

I wanted to flag that the latest Cloudron build is the first beta release candidate for Chatwoot v4. (Chatwoot posted a migration guide to accompany the upgrade, but looks like pgvector may already be installed and available.)

I spotted this before our Cloudron app auto-updated so I was able to turn off auto-updates for this app, but I wanted to recommend marking this beta of a major version such that it doesn't get updated by Cloudron automatically.

n8n ships with a n8n CLI (found on Cloudron at /app/code/node_modules/.bin/n8n.) When I try to use it to export a workflow, I run into this...

/app/code/node_modules/.bin/n8n export:workflow --backup --output=/tmp/n8n/

Error exporting workflows. See log messages for details.
EROFS: read-only file system, mkdir '/root/.n8n'

Is there a different way to invoke the command that works on Cloudron?

Problem solved! With these two in my env file, I'm no longer seeing the error messages:
NEXT_PUBLIC_WEBAPP_URL=https://cal.example.com
ALLOWED_HOSTNAMES='"example.com","cal.example.com"'
(I suspect that the first hostname is sufficient on its own. Haven't yet tried removing the second one.)

We ran into this issue recently, too. As a temporary workaround, we updated the code snippet from <domain>/embed/embed.js to https://cal.com/embed/embed.js. The upstream issue is at https://github.com/calcom/cal.com/issues/14990. It looks to me like this regression is being fixed in the calcom/docker repo with https://github.com/calcom/docker/pull/364. Hopefully this gets incorporated in the next upstream release.

@nebulon Confirming that the latest version of cal.com has embed.js rendering and working again!

I wanted to express appreciation to the Cloudron team for great tooling to support reliable updates. The Etherpad app has changed quite a bit since the previous package, and a great set of platform-level features has made managing potentially breaking version updates very manageable:

• allowing user to specify exactly when auto-updates should run
• only auto-updating if the new version is marked as “stable”, with unstable updates available but not automatic
• allowing user to disable auto updates for specific app(s)
• cloning an app to test changes in a sandbox
• backups automatically created before each version update
• one-click to roll back to any past version

Together, these make it low-stress to manage big updates. Great work on the platform!

Currently using the hosted version. It is excellent! Would definirely prefer to self-host on cloudron if that was an option.

I wanted to post an update on this based on this response to my post on the Outline repo...

The authentication_providers database record for Cloudron OIDC and for Google Login need the same providerId value (i.e., email domain), but only one can have it set.

I confirmed that if a fresh Outline installation specifies that account management should be left up to the application does work properly with Google Login (assuming GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET are set in env.sh file.)

Ideally, Cloudron login and Google Login options would co-exist, but this isn't strictly necessary in our case.

I just updated Chatwoot after updating Cloudron to 7.5. The one issue that I'm seeing is that image uploading seems to be broken. I'm seeing this same error when attempting to do any image uploading action: update an agent's profile image, set a channel avatar, etc. Here's the top of the error message:

Jul 07 16:02:21 I, [2023-07-07T23:02:21.543998 #13] INFO -- : [...] Completed 500 Internal Server Error in 24ms (ActiveRecord: 0.5ms | Allocations: 2246)
Jul 07 16:02:21 F, [2023-07-07T23:02:21.546159 #13] FATAL -- : [...]
Jul 07 16:02:21 [...] LoadError (Could not open library 'vips.so.42': vips.so.42: cannot open shared object file: No such file or directory.
Jul 07 16:02:21 Could not open library 'libvips.so.42': libvips.so.42: cannot open shared object file: No such file or directory):

This discussion looks relevant:
https://stackoverflow.com/questions/70849182/could-not-open-library-vips-42-could-not-open-library-libvips-42-dylib

I'm looking to convert markdown to HTML in a n8n workflow. There are no built-in n8n nodes that do this, so it requires an external node module. marked seems like a good candidate for this.

Based on @girish's comment on Using handlebars.js, it sounds like this would need to be hardcoded into the Dockerfile. Would it be possible to include marked (or something equivalent) in an app update?

Thank you!

I tried following the self-hosters instructions to add Google Calendar to the app, but have run into an issue (error message: "Google client_id missing") that I think might be specific to the Cloudron setup. Ultimately, it looks like we need to add these two new environment variables:

GOOGLE_API_CREDENTIALS={"web":{"client_id" ... }}
GOOGLE_LOGIN_ENABLED=true

and then re-seed the app store:

cd packages/prisma
yarn seed-app-store

I'm seeing lots of errors when running this that appear to be related to apps that I'm not trying to install, but I did see one error message that perhaps needs to be addressed here: error: Environment variable not found: DATABASE_URL.

I saw that the cal.com documentation mentions .env (here) and .env.appStore (here), so I tried putting the new variables there too (in addition to the current env file in Cloudron), but still no luck.

I'm curious to hear if anyone else has been able to successfully connect Google Calendar.

@nebulon I wasn't able to get it to work with changes to the env file, but was able to get everything working through a different path: by first uninstalling and reinstalling from the Cloudron App Store. This time, I entered the credentials directly through the web prompts during the admin user onboarding flow. Looking forward to testing it all out this week!