Skip to content

Use nginx-strangler as console client backend#225

Merged
StephaneTrebel merged 3 commits intomainfrom
use-strangler-as-client-backend
Apr 16, 2026
Merged

Use nginx-strangler as console client backend#225
StephaneTrebel merged 3 commits intomainfrom
use-strangler-as-client-backend

Conversation

@StephaneTrebel
Copy link
Copy Markdown
Contributor

Dernière étape dans la mise en place du nginx-strangler: l'utiliser comme backend pour client au lieu de server.

(Je ne mergerai cette MR qu'une fois qu'on aura réglé les problèmes liés à Gitlab)

@StephaneTrebel StephaneTrebel added this to the MCO milestone Apr 3, 2026
@StephaneTrebel StephaneTrebel self-assigned this Apr 3, 2026
@StephaneTrebel StephaneTrebel force-pushed the use-strangler-as-client-backend branch from 3ebf27f to 9f6fbc5 Compare April 13, 2026 08:11
@StephaneTrebel StephaneTrebel force-pushed the use-strangler-as-client-backend branch from 9f6fbc5 to 36d0a3e Compare April 16, 2026 12:04
@StephaneTrebel StephaneTrebel force-pushed the use-strangler-as-client-backend branch from 36d0a3e to 76e9a9c Compare April 16, 2026 12:17
@StephaneTrebel StephaneTrebel merged commit 32d7f5e into main Apr 16, 2026
4 checks passed
@StephaneTrebel StephaneTrebel deleted the use-strangler-as-client-backend branch April 16, 2026 12:24
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.

2 participants