Deployment as standalone app on linux server

[lpj145]

After all, big thank you guys for you efforts on this, really, this is very very fascinating.

Description
I'd like to deploy my app as standalone https server on linux in some place of the earth, something like small business do: deploy a linux server configured with cloudflare and server yours product solutions.

To Reproduce

So bad so true, I can't see any place that I can configure my app, by the way, searching in the loco source code I saw that line whats turn things out a little bad.

Expected Behavior

Server standalone application with ssl

Additional Context

I can handle this, can I provide the pr?

[kaplanelad]

@lpj145 moving this thread to discussion.

What do you mean by configuring your app?

if I understand correctly, you have a server that runs your binary app. When the process is running, the app listens on your given port.
if you want to expose your server externally with SSL you can use nginx or you have a vendor cloud like AWS that can do it for you

[jondot]

I would strongly recommend having ngnix on that Linux server, to handle SSL termination (we have deploy generator for ngnix). Would that work for you?

[kaplanelad]

You can start your loco server; when it's up, it exposes you to a port on the Linux machine (like you saw in the link).
Afterward, navigate to your Linux IP/DNS. For example, if your server is assigned the IP address x.x.x and you execute the Loco process on port 3000, you can access your application by visiting x.x.x:3000 (without SSL).

In case you want SSL you need configure it in your Linux server

[lpj145]

Guys I respect your point of view, I know how valuable the nginx could be, but, trust me, I only want to have nothing on top of my service, by the way and if I want too not have nothing more than my final binary on the pod image? it increases the chance to up some pods with ssl in handful double ssl handshake between my load balance or reverse proxy and my pod. In this link we can see how axum could implement tls here and here the axum uses hyper under the hood.

[kaplanelad]

@lpj145, now your case is more clear for me :)

We are not supporting this right now, and we can add it.
You can open us an issue. you can also open us if you want

[jondot]

Just to add my 2cent, we always try to simplify, adding SSL termination and handling code will add complexity (loading certificates, specialized binding, cert pinning, and other edge cases) to the boot hot path and to documentation, which is why at this stage we prefer not to support built-in SSL termination.