Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] [Low priority] Define instance name in config #213

Open
fnetX opened this issue Jun 10, 2019 · 1 comment
Open

[Feature Request] [Low priority] Define instance name in config #213

fnetX opened this issue Jun 10, 2019 · 1 comment
Labels
feature request hx hoster experience

Comments

@fnetX
Copy link

fnetX commented Jun 10, 2019

Hey,
I'd like to change the title of the software to something else when running an instance of my own. People seem to get confused between Doodle, Dudel and Croodle, and having multiple Croodle servers does not exactly help here.
In addition, I got an idea to create a service where the user can kinda define the poll name itself, and I'd like to use Croodle as a base since it's much more secure than simple alternatives.

Request:

I would appreciate a php-based config option to change the instance name, e. g. to Troodle.
I see that the software is not yet designed to do so easily.

I can try and work on that, but I guess I need some input about the basics of ember to find a 'fancy' approach.

@jelhan
Copy link
Owner

jelhan commented Jun 10, 2019

This is already possible by overriding some parts of the templates in a fork. I think for your use cases it would be these lines:

{{title "Croodle"}}

<h1 class="cr-logo">{{#link-to "index" class="navbar-brand"}}Croodle{{/link-to}}</h1>

This is not considered public API of course and would be easier if controlled by configuration. But I think this is related to the more general question of theming and branding, which is not officially supported yet.

I would appreciate a php-based config option to change the instance name, e. g. to Troodle. [...]
I can try and work on that, but I guess I need some input about the basics of ember to find a 'fancy' approach.

I don't think serving a configuration via API is the way to go for theming. That would have a very bad performance impact as it would require to wait for another network request to fulfill before initial render.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request hx hoster experience
Projects
None yet
Development

No branches or pull requests

2 participants