nullday

> I think in serving scenario, logs are handled by k8s. Such as a deamonset, or a sidecar container to send the logs to remote API endpoint. Is there anything...

> > BTW, how to handle the envdlib in the new design? Will these be in a new subgraph, or use the default graph directly? > > Still the default...

I think there are some questions to discuss: - Should users care about the port? if we listen on the host's interface, user A use port 8888 but user B...

All we need is code snipplet

Maybe we could had a default cwd directory and allow users to override. WDYT?

If it is just a creation of build.envd and up, I dont think we should provide a top-level subcommand for it. But I think we could do more and how...

> It also can be used in `envd init` yes, we could had a feature to support interactive set simple envd build manifest first.

Should we promote this issue's priority? @gaocegege @VoVAllen @kemingy

I think you could host a meeting to introduce this work for others could help you to maintain.

Nice Job. Maybe we need a podman socket CI to test it all.