golem15/summercms
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(34): close the --module question for v1

Browse Source
This commit is contained in:
Jakub Zych
2026-10-29 18:46:25 +01:00
parent d024ab4bb8
commit 96a7012ece
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.planning/research/questions.md
View File

@@ -15,4 +15,4 @@
## From the plugin marketplace exploration (2026-10-29)
- **Is `--module` for git-URL installs worth supporting?** `summer plugin:install <git-url>` defaults to a submodule checkout. Installing a private repo as a Go module needs `GOPRIVATE`/`GONOSUMDB` and git `insteadOf` rules so `go` can authenticate, which is fragile across GitHub, GitLab and Gitea and across SSH and HTTPS tokens. Find out what the setup costs in practice, whether `plugin:install` can detect and explain a misconfiguration, and decide whether `--module` ships or git URLs stay submodule-only. See `.planning/notes/2026-10-29-plugin-marketplace.md`. Phase: plugin marketplace.
- ~~**Is `--module` for git-URL installs worth supporting?**~~ **Answered 2026-10-29: not in v1.** Git URLs install as submodules only (Phase 34, D-11; `summer plugin:install <git-url>` shipped in 34-04 without `--module`). Revisit only if submodule-only installs prove limiting; adding the flag later is additive. Original question: `summer plugin:install <git-url>` defaults to a submodule checkout. Installing a private repo as a Go module needs `GOPRIVATE`/`GONOSUMDB` and git `insteadOf` rules so `go` can authenticate, which is fragile across GitHub, GitLab and Gitea and across SSH and HTTPS tokens. Find out what the setup costs in practice, whether `plugin:install` can detect and explain a misconfiguration, and decide whether `--module` ships or git URLs stay submodule-only. See `.planning/notes/2026-10-29-plugin-marketplace.md`. Phase: plugin marketplace.