Customisable frontend

[mszkb]

• Please describe the feature you would like to have.
  I'd like to change the logo and colours for the frontend in my self hosted environment.
  The problem so far is, that everything is combined in one single binary. Maybe separate frontend and backend.

• What alternatives have you considered?
  Let us disable the frontend in the binary file with some kind of a flag. So we can fork the code of the frontend and make our adjustments. Provide the backend URL as an environment variable or with a reverse proxy in the docker-compose file.

• Any additional context
  Great tool, I love to use it.

[realaravinth]

I was considering doing something similar. I read stuff on an old tablet and while I enjoy the fancy frontend on my phones and desktop computers, the JavaScript really hurts performance on my tablet.

All requests to the API are scoped to /api/so I guess you can get away with configuring a reverse proxy like Nginx to achieve what you have described.

---

To the contributors, thanks for the great tool

[sungwoncho]

Thanks for your suggestion @mszkb. Adding a build flag to disable embedding the frontend in the binary is a definitely a solution. However, there exists an even more low-key solution: you can make necessary changes and build the binary from the source make version=master build-server.

Just curious, what is the use case and the benefit of being able to customize logo and colors?

[mszkb]

@sungwoncho thanks for the advice. I look into it.

The use case: I love to customize. Replacing the logo with one of mine, makes all my self hosted services (like owncloud, mediawiki and so on) feel like one piece.

[github-actions]

This issue is stale because it has been open for 60 days with no activity.

[sungwoncho]

Now that the web client has been removed, I would like to hear whether this feature would be still useful.