Skip to content

revert: remove LibreSign SaaS-specific fragment config#32

Merged
vitormattos merged 6 commits into
mainfrom
feat/shared-site-header-bridge
Jul 6, 2026
Merged

revert: remove LibreSign SaaS-specific fragment config#32
vitormattos merged 6 commits into
mainfrom
feat/shared-site-header-bridge

Conversation

@vitormattos

@vitormattos vitormattos commented Jul 6, 2026

Copy link
Copy Markdown
Member

Summary

  • remove LibreSign/SaaS-specific fragment webhook environment variables from the base stack
  • remove LibreSign-specific example env entries from the general-purpose repository
  • remove the SaaS fragment upload nginx override from the shared wordpress-docker config

Why

wordpress-docker is a general-purpose repository and should not contain configuration that is specific to LibreSign or the SaaS composition. Those overrides now live in the saas repository local override layer.

Validation

  • local SaaS stack still responds with HTTP 200 on http://localhost
  • the shared header/footer fragment flow continues to work through the SaaS-owned override config

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
@vitormattos vitormattos changed the title fix: support local shared fragment webhook payloads revert: remove LibreSign SaaS-specific fragment config Jul 6, 2026
@vitormattos vitormattos merged commit f2db751 into main Jul 6, 2026
2 checks passed
@vitormattos vitormattos deleted the feat/shared-site-header-bridge branch July 6, 2026 16:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant