or preferably to 0 0 0 0 any ip address

Question

jawnsy · Answer

Use the host setting when running `prefect server start` or the PREFECT SERVER API HOST environment variable See this code <https github com PrefectHQ prefect blob 6c7233bbe55fbe554956bbc70fbfa31de12c1543 src prefect cli server py L111 L122>

Jan · Answer

ah thank you will try

Jan · Answer

Perhaps add that to the docs

Jan · Answer

And if I missed it please link me to the docs

Jan · Answer

Brilliant That worked with 0 0 0 0

Jan · Answer

Thank you very much < jawnsy>

Jan · Answer

I can now see if this fits our needs

Jan · Answer

CORRECTION It works to launch the dashboard with 0 0 0 0

Jan · Answer

trying with external ip

Jan · Answer

okay So

Jan · Answer

looks like code does not differentiate between UI and API urls

Jan · Answer

So the expectation is the api and the ux run on the same host

jawnsy · Answer

There are two variables one that determines the URL that the UI uses to find the API PREFECT UI API URL and one that the server uses to determine where to bind the PREFECT SERVER API HOST variable There are some defaults between the two This is how we set things up in Kubernetes we use host to have the API listen on all interfaces Then we use the env var to tell the client where to find the API endpoint this is the external URL e g that your users should hit from their browser I think you can host the UI and API on separate hosts if you want but I m not sure why you d want to do that The UI is purely client side code single page app

Jan · Answer

Ahhhhhh

Jan · Answer

I see

Jan · Answer

Reconfiguring

Jan · Answer

< jawnsy> Brilliant That seems to have worked

Jan · Answer

To address why backend and frontend on different servers we usually do this to put firewalls and authentication in between with the ux portions being in the DMZ externally facing and only particular hosts with particular credentials from that DMZ can inquire of the backend

Jan · Answer

Up and running now thanks

Jan · Answer

I imagine this is an intentional choice <https discourse prefect io t why does prefect 2 0 doesnt include auth and rbac features as part of the open source package 741> but no RBAC or Authentication in the non cloud version is increasingly a turn off for adoption across infrastructure tools Please pass on to your product managers if that isn t you Market has woken up to excessive charges just for basic security in a world where security is increasingly important and expected out of the box Cloud offerings need to differentiate on other value to be considered worth the adoption YMMV but the future is pretty clearly no tolerance for cloud requirements to get basic security for OSS solutions If the cloud solutions offer value above the basics security there is attention to migration Frankly in today s world if you aren t OSS ing your security you re likely to end up less trusted out of the gate lt soapbox gt Looking forward to playing with it but can t give to my users until I secure it in some way

Jan · Answer

Also I m this guy <https www linkedin com janman>

Jan · Answer

Have to say after searching through the options Prefect rose to the top and thus am investing in exploring it

Jan · Answer

But the security thing is an Achilles heel

jawnsy · Answer

Regarding authentication I ve passed along your feedback to our Head of Product gt To address why backend and frontend on different servers we usually do this to put firewalls and authentication in between with the ux portions being in the DMZ externally facing and only particular hosts with particular credentials from that DMZ can inquire of the backend Both the frontend and backend need to be accessible to users When we serve the frontend we provide static content JavaScript HTML CSS and users browsers load content dynamically from the API endpoint Whether or not the UI access is authenticated doesn t really matter because there s no sensitive content there all requests go from the users browsers to the API endpoint via CORS requests Have you evaluated our Prefect Cloud service It s free for small teams up to 3 users and 1 workspace and has capabilities that are not available in our OSS You can also schedule a call with one of our engineers here other contact options including email are here

Jan · Answer

Thank you for passing on my feedback slightly smiling face

Jan · Answer

Will consider the cloud perspective but not until we have kicked the wheels and determined we can secure it on premises We do whitebox security testing as part of that process