Nomulus CloudRun Deployment & Service Mapping Clarification

[amsyvah]

I have been working on deploying Nomulus to CloudRun and have made some fixes to mockUserService to get it running. I've successfully deployed jetty, core, and proxy. My database is on the cloud with Flyway migration, currently empty. I've also set up a VPN with a serverless VPN access connector, as initial attempts to connect the database to the deployed image were unsuccessful. I'm still verifying the connection with the current settings.

I need some clarity regarding the build and deployment process, specifically with how the Nomulus subdirectories map to the services. I've received conflicting guidance: one suggests building from core, jetty, proxy, default, and console-webapp, while another recommends building services backend, bsa, default, pubapi, and tools.

Could you clarify the intended mapping? For example, does core map to a service named backend, and jetty to pubapi? Any guidance on this would be greatly appreciated, as I'm new to this codebase.

Additionally, I'd like to understand the recommended environments for the current Nomulus GitHub code library. Would a sandbox environment suffice, or do specific configurations need to be set up?

I've had some deployments pull up front pages (one titled "Domain Registry," another "Google Registry") on /console and /registrar paths, which further adds to the complexity.

Any pointers on this thread or via email would be immensely helpful in navigating this elaborate setup.

Thank you.