Cloudron Forum

@brianb said in Add MariaDB and Setup as Replica:

Can't I just create a mysql database in the grafana once it is setup in cloundron?

Not sure what you mean here. Are you referring to Grafana's database (https://grafana.com/docs/grafana/latest/setup-grafana/configure-grafana/#database) or Grafana's data source (https://grafana.com/docs/grafana/latest/datasources/mysql/)

On Cloudron, Grafana's database cannot be changed. It uses PostgreSQL internally.

If you are referring to data source, then yes, you can can mysql database data source. But I referred to MariaDB only because you mentioned MariaDB in your initial post (in fact, there is no mention of MySQL there).

Specifically, the DO refcode is 933831d60a1e .

This should be fixed with next release. It was a missing event handler.

@lukas Forgot to link to the docs - https://docs.cloudron.io/user-management/#openid-connect

@jdaviescoates said in Shared Authentication between Apps:

I'd still love a simple way to allow for Open Registration on my Cloudron:

https://forum.cloudron.io/post/5339

I agree that would be great also.

@girish the example command did the trick! I was not using the correct syntax but also I didn't specify the database name. Once I did that I was able to reach the Ghost mysql database from the Discourse app 🙂

@girish said in Enable enableDeveloperExperiments:

enableDeveloperExperiments

moving it outside privacy worked, thank you!

@briankb-0 said in How to Start Discourse with Plugins Disabled?:

@girish I'm sorry, I've already uninstalled and reinstalling the app

no worries, let us know if you hit it again.

@brianb said in Installing More Than One Plugin at a Time:

@jdaviescoates handy? NOPE!

I get it... they need to make $ to keep discourse development (or nodebb) funded and moving forward. But after I got Discourse installed I thought there would be a nice UI for the Plugins... nope.

It's not hard but it is tedious.

Best I've been able to do so far is to go to official Discourse github repo and do a search for "discourse-plugin" which is how they tag MOST plugins.

https://github.com/orgs/discourse/repositories?q=discourse-plugin&type=all&language=&sort=

5c0672d4-090d-4836-82a2-864ca508aa82-image.png

I also keep their plugins page pulled up to know what is available and how they prioritize them.

https://www.discourse.org/plugins#business

@brianb Do you think this should be added to the doc for users to find good plugin sources faster?
And if the answer is yes... would you like to contribute that to the doc? 😉

@briankb-0 the launcher script only works with Discourse's own packaging stuff i.e if you use https://github.com/discourse/discourse_docker . It does not work in Cloudron, we have our own packaging at git.cloudron.io/cloudron/discourse-app

Generally, you should be able to do everything using rake or bundle exec since Discourse is just a rails app. See https://docs.cloudron.io/apps/discourse for some examples.

And doing a curl does return the ghost.js file:

$ curl -L https://forum.cloudron.space/plugins/nodebb-plugin-blog-comments/lib/ghost.js (function() { "use strict"; var articlePath = window.location.protocol + '//' + window.location.host + window.location.pathname; var pluginURL = nbb.url + '/plugins/nodebb-plugin-blog-comments', savedText, nodebbDiv, contentDiv, commentsDiv, commentsCounter, commentsAuthor, commentsCategory; var stylesheet = document.createElement("link"); stylesheet.setAttribute("rel", "stylesheet"); stylesheet.setAttribute("type", "text/css"); stylesheet.setAttribute("href", pluginURL + '/css/comments.css'); ...

The version of the plugin installed is 0.8.6

@briankb-0 said in Root Domain Hosts Shopify Site Subs Are Cloundron:

What happens if I add the domain to Cloundron so I can use it to setup sub-domains for NodeBB and Ghost?

When you add a domain:

To validate credentials, the code will add a cloudrontestdns A record and remove this immediately. To configure the server to send emails: If there is an existing SPF record, it is edited to have a:my.my.domain.com . The SPF record essentially whitelists which servers can send email on behalf of the domain. This is NOT destructive, your existing SPF record is only amended. A DKIM record is added under <random>._domainkey.domain.com. This is used to sign/verify emails by mail servers. Because of the 'random' part, it won't conflict with any of your existing DKIM keys If there is no existing DMARC record, we create one with the value "v=DMARC1; p=reject; pct=100". This essentially is a strict DMARC policy not allowing anyone outside the SPF record to send emails on behalf of the domain.

Other than that, it is what @BrutalBirdie said. The bare/root domain is untouched. Cloudron only adds entries when you install apps. Also, if you had a root domain DNS entry already, it will warn you that it's in use, if you try to install an app on the root domain (it does this check for any subdomain).