I launched 20 Forge apps. Here's some feedback

Forge
8

Thanks mate!

Yeah so the way I did Forge mono repo was a manifest for each app: manifest_APP1.yml, manifest_APP2.yml etc and then this batch script:

 for %%f in (manifest_*.yml) do (
   rename "%cd%\%%f" "manifest.yml"
   forge deploy -e production
   rename "%cd%\manifest.yml" "%%f"
 )

Then routed the particular app to an exported render() function:

  function:
    - key: macro
      handler: macro._BUTTONS
    - key: config
      handler: config._BUTTONS

But forge deploy seems to lint (and throw permission errors) on the entire code base instead of following the rabbit hole of exported/imported components.

Dynamic manifest files would be useful. eg the way I pulled off a mono repo deployment on Connect (which is hilariously annoying my slow competitors) was by generating the atlassian-connect.json via an API endpoint running in a Cloudflare Worker.

1 Like