C-Liu

                        ^℠
  C六

Biz case #65, the php and python codesets at the core of the Domains CMS.
Defining use cases are the sameboat network and the AKSAMBAR products.

 
"DCMS" is used in the widest sense to refer not just to the php/python core (C六) but to content management in domain space generally outside of the DCP providing manifold services to AKPERSONS. DCMS< and DCMS> name front and back end elements relative to the Drupal 7 codebase, respectively. C六 php is expected to remain d7 based³.

D7 will reach EOL in November, 2022 and drupal.org will cease support then. Drupal has a vendors program for extended support which is inappropriate for me as CLiu isn't drupal. The drupal part of it nearly is though and therefore I will be maintaining a curated d7 core and set of contrib modules as part of the software as a service. Instructions on how to set my servers for the drupal update function will be posted here before the EOL allowing the module update mechanism to continue for the from that point diverged lines. Core and contrib modules which are unaltered will be noted. As far as the CLiu line is concerned, security issues are covered by domain space security.

Sameboat commons is the stable branch from my live sandbox and the first stop before downstream deployments. The commons app supports C六 and my product lines as a base.

Timeline

c. 4719 — Portable Groups. Fork live and commons prod, rebuilding the latter².

c. 4716 — Pursuant to SA-CORE-2018-004, C六 drupal was rebuilt from scratch.

c. 4714 — First selection of sameboat name based on concept of affinity group support.

c. 4705 — First selection of Drupal as php CMS of choice and the C六 name after C5.

  ²C-六 exceeds drupal tolerances ( best practice), engineering/curation to make it so and make it work is part of the ops concept. Live now has 464 and commons 279 non core.   ³D9 branch for devops use, other php packages generally track latest release for the operational stack.

C5 (whence "C-6")

C六书

d.o