You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Combined with basic auth, allows a more secure experience.
Additional notes
Implementation is probably relatively easy, both javalin and jetty provide examples.
The current recommended way to get HTTPS with Tachidesk is running with a reverse proxy server.
Input by @ntbm "I really prefer configuring my reverse proxy and managing the certificates outside of an application. So usecase are people who want to host it on a server, but are not really familiar with hosting?"
Input by @Derevar on discord: "My prefered way is app in a docker and that behind my nginx reverse proxy." They also agree with @ntbm.
My current conclusion: Our users don't seem to need this feature really, also managing certificates with an app outside Tachidesk is indeed better.
The text was updated successfully, but these errors were encountered:
What feature should be added to Tachidesk?
Run the server in HTTPS mode.
Why/Project's Benefit/Existing Problem
Combined with basic auth, allows a more secure experience.
Additional notes
@ntbm
"I really prefer configuring my reverse proxy and managing the certificates outside of an application. So usecase are people who want to host it on a server, but are not really familiar with hosting?"@Derevar
on discord: "My prefered way is app in a docker and that behind my nginx reverse proxy." They also agree with@ntbm
.The text was updated successfully, but these errors were encountered: