Difference between revisions of "C-Liu"

From Cibernética Americana
(38 intermediate revisions by the same user not shown)
Line 1: Line 1:
<table width=100%><tr>
+
 
<td width="20%">[[:en:Concrete 5|<html><span style="background-color: maroon; color: white;">C5 (whence "C-6")</span></html>]]</td>
+
<html><div  style="background-color: antiquewhite; color: navy; "></html><br/>
<td width="20%">[[Documentation|<b>C六书</b>]]</td>
 
<td width="20%">[https://drupal.org/u/kyberuserid <html><large><b>d.o</b></large></html>]</td>
 
<td width="20%">[[drupalapps|<html><span style="background-color: black;">druportfolio</span></html>]]</td>
 
<td width="20%">[[C5|<b>To PHP CMS Page</b>]]</td>
 
</tr></table>
 
<html><div  style="background-color: midnightblue; color: antiquewhite; "></html><br/>
 
 
&nbsp;
 
&nbsp;
 
<font size=6>C六</font>
 
<font size=6>C六</font>
  
<html><img style="position: relative; top: -50px;" align=right width=175 src=/img/front_1.jpg>
+
<html><script> if (screen.width >= 1024) document.write(
<blockquote><p>
+
"<img style='position: relative; top: -30px;left: -50px;' align=right width=175 src=/img/front_1.jpg>");</script>
The drupalfolio link has some other/earlier/jobbing use. I pretty much started with d6 so never used earlier,see discussion page, history for evolution.
+
<blockquote>
While I don't anticipate decommitting drupal,<br> I've moved on to the (haskell based) generalization in DCMS, django/python for systems web stuff, and take WordPress as a simpler peer to drupal, and with mediawiki, forming the our cover of the space of PHP CMS. </p>
+
<div style="text-align: justify;width: 80%;"><br><center><b><i>C六 is just my integration of Drupal and django.<br>The sameboat verticals and SaaS are its proving ground.</i></b></center><br><br>&nbsp;<br>
<div style="width: 80%;"><br><center><b><i>C六 is just my curated set of d7 and d8 modules using a single pg db packaged with the app module
+
C六 is a DCMS component and not a product as such, so it doesn't have documentation, nor are its sources available anywhere except the instances or the reference repo here.<p>
and d.o drupal distribution helpers. <br>The sameboat products and integrate with my domain space and focus on specific end service/feature sets.</i></b></center><br>
+
<p>Pursuant to the security issue with drupal 7.59/8.5.3, the <a style="color: brown;" href=https://sameboat.live>sameboat app</a> (essentially C六 applied to different lines of biz) was rebuilt from scratch and from that point maintains a clean line of descent, with only forward deployments from the clean environment, issues such as SA-CORE-2018-004 are wiped by deployments to the wild, as they arise.
<p> Originally intended as a locus for various stuff and for a line of biz supporting d7/d8 migration/integration as well as CMS generalization. A golden procrastination situation was found to have arrived by about Spring '18 by which time d8 was finally starting to look solid, although d7 necessarily remains the production choice. So at this point the mark is strictly used for my curation of d7/d8 modules, principally in the sameboat venture and the distribution which I will only be offering here and thru Shopify, not on d.o.</p>
 
<p>Pursuant to the security issue with drupal 7.59/8.5.3, the <a href=https://sameboat.live>sameboat app</a> (essentially C六 applied to different lines of biz) was rebuilt from scratch and from that point maintains a clean line of descent from that rebuild, with only forward deployments from the clean environment, to avoid such issues in the future. Issues such as SA-CORE-2018-004 are wiped by deployments to the wild, as they arise.
 
 
</p>
 
</p>
The sameboat domain composed of </html>[https://sameboat.live sameboat.live] which is d7 and [https://cliu.sameboat.live cliu.sameboat.live]<html> which is d8 has operational versions of every such service/feature set in its reference public form.<br>&nbsp;<br><br>&nbsp;<br>
+
The sameboat domain (publicly routed as </html><span class="plainlinks">[https://sameboat.live sameboat.live] (d7) and [https://cliu.sameboat.live cliu.sameboat.live]</span><html> (d8) is the model production instance. Currently only the verticals use django, which when present always includes drf against the drupal database.<br>&nbsp;<br><br>&nbsp;<br>
 +
<center>Links below background my drupal use, GMRV was first django iirc.</center><br><br>
 
</div></blockquote></div>
 
</div></blockquote></div>
 
</html>
 
</html>
 +
<table width=100%><tr>
 +
<td width="20%">[[:en:Concrete 5|<html><span style="background-color: maroon; color: white;">C5 (whence "C-6")</span></html>]]</td>
 +
<td width="20%">[[Documentation|<b>C六书</b>]]</td>
 +
<td width="20%">[https://drupal.org/u/kyberuserid <span style="color: pink;"><b>d.o</b></span>]</td>
 +
<td width="20%">[[drupalapps|<html><span style="background-color: black;">druportfolio</span></html>]]</td>
 +
<td width="20%">[[C5|<b>To PHP CMS Page</b>]]</td>
 +
</tr></table>

Revision as of 00:30, 20 December 2018


  C六


C六 is just my integration of Drupal and django.
The sameboat verticals and SaaS are its proving ground.


 
C六 is a DCMS component and not a product as such, so it doesn't have documentation, nor are its sources available anywhere except the instances or the reference repo here.

Pursuant to the security issue with drupal 7.59/8.5.3, the sameboat app (essentially C六 applied to different lines of biz) was rebuilt from scratch and from that point maintains a clean line of descent, with only forward deployments from the clean environment, issues such as SA-CORE-2018-004 are wiped by deployments to the wild, as they arise.

The sameboat domain (publicly routed as sameboat.live (d7) and cliu.sameboat.live (d8) is the model production instance. Currently only the verticals use django, which when present always includes drf against the drupal database.
 

 
Links below background my drupal use, GMRV was first django iirc.


C5 (whence "C-6") C六书 d.o druportfolio To PHP CMS Page