Repository navigation
Release 3.1.1: Instagram works on a fresh install; printable guide rewritten - #26
Merged
Merged
Conversation
…e for 3.1.1 Instagram could not be connected on a fresh install: the Social section refuses to save credentials without SOCIAL_ENCRYPTION_KEY and nothing set it. install.sh and generate-secrets.sh now generate it with the other secrets (only when empty). The installer's closing message also named a Settings path that no longer exists. The installation guide PDF predated 1.0.0 and pointed at Admin Settings -> Domain, removed in 3.0.0. It is rewritten from an HTML source in docs/guide/, rendered by the new scripts/make-guide.sh. Release prep for 3.1.1: changelog, version pins, package versions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On Alpine (and docker:dind) lsof is BusyBox's, which ignores its arguments and exits 0. Every port read as in use, so the free-port walk never ended and the install hung with no output after 'install name'. Skip a BusyBox lsof in favour of netstat, and stop after 100 ports. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes
Instagram could not be connected on a fresh install. The Social section refuses to save Instagram credentials without
SOCIAL_ENCRYPTION_KEY, and nothing generated it.install.shandgenerate-secrets.shnow generate it with the other secrets, only when it is empty, so an existing key is never changed..env.exampledocuments it.The installer's closing "Next steps" said
Admin Settings → WhatsApp Accounts, a menu that no longer exists. It now saysSettings → WhatsApp → Accountsand addsSettings → Instagram → Connection.The installer hung forever, silently, on Alpine /
docker:dind. BusyBox'slsofignores its arguments and exits 0, so every port read as busy and the free-port walk never ended. A BusyBoxlsofis now skipped in favour ofnetstat, and the walk stops with a clear message after 100 ports.Docs
docs/ForgeGrowth-Installation-Guide.pdfis rewritten. The old one predated 1.0.0 and sent readers to Admin Settings → Domain (removed in 3.0.0) in five places. The new one adds the zip route, a chapter on connecting Instagram, and domain checks that usecurl. Its source isdocs/guide/installation-guide.html;scripts/make-guide.shrenders it with WeasyPrint in a throwaway container.docs/social-section.md: the installer now generates the key.docs/install.mdbackups section: back upSOCIAL_ENCRYPTION_KEYtoo.Release prep (same pattern as 3.1.0)
Changelog
[3.1.1], pinsv3.1.0→v3.1.1in README, install.md and SECURITY.md, package versions, anddist/forge-growth-v3.1.0.zip→forge-growth-v3.1.1.zip, built withmake-bundle.sh(all links verified).Tested
canSaveSecrets: falseand no key in.env. Re-ran this branch's installer over it:generated SOCIAL_ENCRYPTION_KEY,canSaveSecrets: true, and saving an app secret throughPUT /api/social/credentialssucceeded. The new "Next steps" text printed.--domain) end to end, in an isolateddocker:dindcontainer (which is how the hang above was found): this branch's installer with--domain crm.fgtest.internal --tls-email internal. Caddy started on 80/443 and served a certificate for the domain; HTTP returned 308 to HTTPS;/api/auth/meanswered through HTTPS;webwas bound to127.0.0.1only;TLS_MODE=caddy; sign-in was verified. Not covered: real Let's Encrypt issuance, which needs public ports 80/443.After merge
Tag this PR's merge commit
v3.1.1, wait for Publish images, thengh release create v3.1.1 dist/forge-growth-v3.1.1.zip.🤖 Generated with Claude Code