[new feat] add --serve-html-path param in server target

[Liyulingyue]

My work is as follows:

• add --serve-html-path option. After starting the service, you can enter "127.0.0.1:8081" in the browser to access the following interface.

[leejet]

I think it would be better to keep this as a separate repository, like many other UIs powered by sd.cpp.

[Green-Sky]

I think it would be better to keep this as a separate repository, like many other UIs powered by sd.cpp.

I second that.

It would also help if server had something like a --serve-html-path <path> option.

[Liyulingyue]

I think it would be better to keep this as a separate repository, like many other UIs powered by sd.cpp.

How about adding the width, height, and steps parameters? If these changes look good, I’d be happy to open a separate PR for them.

And I completely understand the strategy of separating frontend and backend services! That said, I’d like to suggest a simple HTML page (just basic API calling) to:

• Help new users test the server without writing frontend code
• Let developers quickly verify model behavior during debugging

It’d require minimal maintenance, just like FastAPI’s auto-docs or llama.cpp’s debug page.

[leejet]

How about adding the width, height, and steps parameters?

At present, all of these parameters can be specified either in the prompt via <sd_cpp_extra_args>(.*?)</sd_cpp_extra_args> or through the default image generation parameters.

[leejet]

It would also help if server had something like a --serve-html-path option.

I agree with this approach.

[Liyulingyue]

At present, all of these parameters can be specified either in the prompt via or through the default image generation parameters.<sd_cpp_extra_args>(.*?)</sd_cpp_extra_args>

Oh! Sorry for the redundant work.

[Liyulingyue]

I agree with this approach.

The code has been revised based on the comments. Currently, the front-end can be specified via a --serve-html-path option. Please review it.