search

beamable / BeamableProduct

The beamable product suite including com.beamable, com.beamable.server, microservice base image, portal, the installer, and build scripts
Other
4 stars 0 forks source link

Docs - create workflow docs for development #3372

Open cdhanna opened 2 months ago

cdhanna commented 2 months ago

We need to explain how to develop locally for the Unity SDK, and the CLI, and SAMs.

Move all build scripts to a root location, (/scripts)

  1. how does set-packages.sh work?
  2. how does CLI/SDK communication work? (Global install, vs, src install, vs nuget install)
  3. how does the install.sh script work for the CLI
  4. how does the build.sh script work for the templates
  5. How is dotnet installed in the SDK?
  6. How does the CLI code get generated? (how to regen, specifically?)
  7. How does the Auto-gen OAPI code get generated?
  8. How does the CLI know about Microservices (csproj files are king) (and why did we not use a hard coded json file?)
  9. How does the Unity SDK get access to the nuget packages (beamable.common)
  10. How do we version the CLI and SDK together? (similar to above)