Change old /archive/* links to /daily/*
This commit is contained in:
parent
661669f2a5
commit
538141466c
406 changed files with 457 additions and 457 deletions
|
@ -3,7 +3,7 @@ title: >
|
|||
Separating releases from deployments with feature flags
|
||||
pubDate: 2022-12-07
|
||||
permalink: >-
|
||||
archive/2022/12/07/separating-releases-from-deployments-with-feature-flags
|
||||
daily/2022/12/07/separating-releases-from-deployments-with-feature-flags
|
||||
---
|
||||
|
||||
In a typical feature release process, a feature is released when you merge the code and push it to production.
|
||||
|
@ -20,4 +20,4 @@ If my feature is incomplete, if it's feature flagged, I can commit and deploy it
|
|||
|
||||
If you wanted, you could enable a feature flag for a subset or a certain subsection of your users - allowing them to test it before making it available to everyone.
|
||||
|
||||
Another way I use feature flags is within a [multi-site Drupal application]({{site.url}}/archive/2022/11/13/how-i-manage-multiple-drupal-websites-using-the-same-codebase) to enable a different feature set per site and allow me to keep one version of the code for all sites to keep this easy to manage and maintain.
|
||||
Another way I use feature flags is within a [multi-site Drupal application]({{site.url}}/daily/2022/11/13/how-i-manage-multiple-drupal-websites-using-the-same-codebase) to enable a different feature set per site and allow me to keep one version of the code for all sites to keep this easy to manage and maintain.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue