Building

Building turns a local SDK application into a container image that the LongLink Platform can inspect, register, and deploy. The image carries LongLink metadata labels for application identity, SDK version, application version, display text, and declared environment requirements.

longlink build builds from a temporary Docker context and leaves the application folder untouched. Push the resulting image to a registry the LongLink Platform can reach before creating the application.

Use --tag to set the image version tag, --registry to prefix the image with a registry, and --push to push the image after the local Docker build completes.

Point longlink build at the environment class from pyproject.toml. The build command parses the class statically for image metadata, without importing application code or requiring real secret values.

Application Metadata

LongLink loads application metadata from pyproject.toml. Values in [tool.longlink] override standard [project] values where both are supported. The same section can also point longlink build at the user-defined environment class used for generated image metadata.

  • name identifies the application. It falls back to [project].name.
  • version identifies the application version. It falls back to [project].version.
  • title and summary provide display text for application views and registration.
  • description falls back to [project].description when omitted from [tool.longlink].
  • contact, license_info, and terms_of_service are optional metadata objects or URLs passed through to the runtime and image labels.
  • environment is a module:Class import string for the user environment class. It defaults to src.envs:Env.