javascript - Keystone.js: use one model in multiple sites -


i need create multiple sites using keystone.js (sites network). have reference collection, should used on every site relationship models in other network's sites. it's universal tags list used across network's site. hope understand mean. sorry bad english.

without understanding use case see 2 potential architectures explore:

  1. single keystone instance:

    see if can design data use inheritance , try putting sites in 1 keystone instance. ie have parent "post" model , per site "foopost", "barpost" inherits post. way use stock keystone/mongoose relationship mechanisms , built-in crud bootstraps. drawback here architecture make admin ui , data model more complicated think potential solution "partitioning" single keystone instance separate sites. might work better few "sites" on 1 instance more make data model , admin ux complicated use.

    pros: can use keystone stock crud/relationships

    cons: more complicated admin ux, you'll have manually partition front end out keep data separate, more complicated data structure using lot of inheritance

  2. separate keystone instances:

    a lightweight way share non-relational data between separate keystone instances (like common tag list) bootstrap api wrapper "tag" model each site , add api crud calls each keystone instance api . maintain model data across sites calling crud api via mongoose hooks. there plenty of examples out there boostrap keystone crud api , make api crud call within model's post save, post delete, or post update.

    to model relationships more complicated. create "link" model on each site nothing more url field , _id. set 1 many relationship in models on each site trying share relationships , wrap link model in crud api. way "link" models , render out clickable links on admin pages. have code pretty fair amount of hook , api calls think potentially feasible architecture system can allow transactional data sync tolerance (ie wouldnt try type of architecture requires super tight transactional integrity ok social media).

    pros: separation of concerns, cleaner data model, partitioned admin screens (maybe con use cases)

    cons: need sync data model schema (you can submodule common keystone models github repo , share between sites fix problem ive done before), more api , schema hook code, each site has separate admin ux, more sysadmin work run , sync separate instances


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more