docs: example monorepo

examples/nosnap_monorepo/beet-common.yml

@@ -0,0 +1,13 @@
+author: Chad Beeter
+
+# We can't use "data_pack.load" because the "src" path would be
+# resolved relative to the "beet-common.yml" file instead of the
+# root of each individual subproject. Config options provided
+# through "meta" aren't resolved when the config is loaded but by
+# plugins directly, which is what we want in this particular case.
+pipeline:
+  - beet.contrib.load
+
+meta:
+  load:
+    data_pack: "src"

examples/nosnap_monorepo/beet-release.yml

@@ -0,0 +1,18 @@
+broadcast: "projects/*"
+extend: "beet.yml"
+
+# A broadcast config is resolved at the root of each
+# individual subproject so we need to go up to output
+# all packs in the same location.
+output: "../../out"
+
+data_pack:
+  zipped: true
+
+# Disabling the "meta.autosave.link" option makes it so
+# that if we have a "beet link" set up for development
+# we won't pollute the "datapacks" directory with the
+# release zips.
+meta:
+  autosave:
+    link: false

examples/nosnap_monorepo/beet.yml

@@ -0,0 +1,2 @@
+broadcast: "projects/*"
+extend: "beet.yml"

examples/nosnap_monorepo/projects/bar/beet.yml

@@ -0,0 +1,3 @@
+version: 1.2.3
+
+extend: "../../beet-common.yml"

examples/nosnap_monorepo/projects/bar/src/data/demo/functions/bar.mcfunction

@@ -0,0 +1 @@
+say bar

examples/nosnap_monorepo/projects/foo/beet.yml

@@ -0,0 +1,3 @@
+version: 42.0.1
+
+extend: "../../beet-common.yml"

examples/nosnap_monorepo/projects/foo/src/data/demo/functions/foo.mcfunction

@@ -0,0 +1 @@
+say foo