This script, `list-blueprint-schemas`, is a blunt and fragile object, but it can get the work done. Every time
it is run, it will get a list of all version tags from Git, compare them to all the available schemas available
by version, and print out a copy of `./website/docs/customize/blueprints/v1/structure.md` where it has replaced
the existing `Available Older Blueprint Schemas` collapse block with the most up-to-date version.
I will have to talk to @beryju and @tanberry to find out what they want done with this; would it be fine to just
run this at build time *before* the site is compiled, replacing the structure.md file with this dynamic block,
or can we generate it separately and [include it as a markdown
extension](https://stackoverflow.com/questions/65741307/how-to-include-import-markdown-file-content-in-docusaurus-v2)?
* added note to readme
* fixed env file
* tweaks
* moved env file
* add more troubleshooting
* ran make website
---------
Co-authored-by: Tana M Berry <tana@goauthentik.com>
* add csv file for migration to new structure
* this time in csv format jeez
* edits to readme
* freaking mess
* tweaks
* tweaks
* trying
* tweak
* env file ot force only reading docs dir
* update readme
* tweak
* remove old, too big file
* tweak readme
* make website again
* more tweaks
---------
Signed-off-by: Tana M Berry <tanamarieberry@yahoo.com>
Co-authored-by: Tana M Berry <tana@goauthentik.com>
* add docsmg tool
* moved to the correct scripts directory
* removed test files
* added install script and readme draft to docsmg
* fix install script
* fixed issues
* Revert "fixed issues"
This reverts commit a51192025f.
* Revert "Revert "fixed issues""
This reverts commit ab68918fea.
* added dotenv and updated readme
* fixed install script
* update readme to ensure that new installers of rust have envs loaded
* changed docsmg from using .env to docsmg.env
