Whitelabeling is not complete

[potemkin_ai]

I've noticed that branding is not complete - Cloudron name is at least displayed at authorization page and 500 error pages.

Is there any chance that Cloudron will be replaced with 'Cloudron Name' from Branding, please?

[humptydumpty]

It’s also mentioned if you visit a domain/sub that has no app installed.

You are seeing this page because the DNS record of sub.domain.com is set to this server's IP but Cloudron has no app configured for this domain.

[girish]

I guess Branding is too broad a term We only meant to change the login screen text and logo. It's not meant for whitelabeling as such. There is a lot of places like emails, footers, template pages, API calls where we use 'cloudron' all over.

[andreasdueren]

@girish I know we have talked about this before, you said that a lot of these are hardcoded (Like the app offline page). But it would be nice to be able to modify these without having them overwritten on updates.

[potemkin_ai]

@nebulon , it might be not too much complicated, if branded name is exposed via some kind of API, like you expose Cloudron version (for some reason) now via /api/v1/cloudron/status.

You can then do fetch for that custom name using JS's fetch() and that's it.

btw, why would you expose platform version in the public accessible API?

[jayonrails]

I would be happy to support on this regarding the language files, with German, Englisch and Danish.

[humptydumpty]

@jayonrails said in Whitelabeling is not complete:

Englisch

[andreasdueren]

@potemkin_ai said in Whitelabeling is not complete:

btw, why would you expose platform version in the public accessible API?

True, this should at least require a token

[jagan]

Upvote for whitelabelling the branding.