getmeli / meli

Platform for deploying static sites and frontend applications easily. Automatic SSL, deploy previews, reverse proxy, and more.
Other
2.41k stars 97 forks source link

Custom Logo and Server Name #181

Open robertorubioguardia opened 3 years ago

robertorubioguardia commented 3 years ago

Hi @gempain ,

This is more like a feature request.

Considering that Meli is self-hosted, it'd be cool to have the ability to change the logo to a custom one and also change the server name from Meli to a custom name, so that email invites, notifications, etc, show a name my users can recognize and therefor trust.

This could even be a "premium"/paid feature, but I think, as portainer does, it would open Meli to be used as a base for commercial or pseudo-commercial use, therefore boosting interest and adoption.

Cheers,

gempain commented 3 years ago

@robertorubioguardia hi ! Thanks for opening an issue here.

This feature sounds interesting. I see a use in customizing the name and logo of the server, but we would like Meli's name to stay in the frame. I do think that it would be nice to have a way to customize the title to something like "My Company's Meli" and have your company logo placed somewhere alongside Meli's - this would indeed increase trust.

Currently, when you invite someone to Meli, the email contains enough information for your users to reasonably trust it IMO. Also, there is already an environment variable named MELI_MAIL_SUBJECT_PREFIX that allows you to change the prefix used in emails. Also, MELI_MAIL_FROM should let you add some trust to those emails.

One way I see this going is the following: we could drop MELI_MAIL_SUBJECT_PREFIX and replace it with something like SERVER_NAME which would be used everywhere Meli's name is used (including emails). However, as I mentioned, keeping Meli's name alongside SERVER_NAME would be something important to us.

That said, Meli is currently under the BSL license, which secures a monetization path for sustaining the project by running a SAAS version (please read this). I would be interested in learning more about your use case and how we can find a way to work together. Let's discuss this aside (sent you a PM 😉).