Closed pietgeursen closed 5 years ago
iainkirkpatrick
commented
7 years ago questions questions questions:
dogstack:dev: would this be a wrapper around something like budo to start with? or are you imagining something quite different?
0.3: this is referring to your thoughts around files being named a certain way within a certain directory structure just glueing themselves together ala next.js?
ahdinosaur
commented
7 years ago @iainkirkpatrick dogstack dev is the same as catstack dev, namely it wraps node-dev so your next command runs in auto-restart mode. so most commonly you'd do dogstack dev server. no reason to use budo anymore since i wrote uify-server
ahdinosaur
commented
7 years ago @iainkirkpatrick re 0.3, yes. then 0.4 is this but also applied to "plugins" in separate directories.
okay, i want to think about MVP:
0.1
bin:
dogstack lint: https://github.com/enspiral-root-systems/dogstack/issues/42dogstack test: https://github.com/enspiral-root-systems/dogstack/issues/43dogstack dev: https://github.com/enspiral-root-systems/dogstack/issues/440.2
bin:
dogstack server: https://github.com/enspiral-root-systems/dogstack/issues/41api:
dogstack.Log()dogstack.Server({ log, service, plugins })dogstack.Service({ services, plugins })dogstack.Client({ plugins })dogstack.Browser({ store, routes, renderer })dogstack.Store({ reducer, middlewares, enhancers })dogstack.Renderer({ plugins, enhancers, setup })0.3
rather than use
dogstack[method]functions as glue code, remove the glue code entirely and export the custom params necessary to glue everything together as you want, at respective filesserver.js,service.js,client.js,browser.js,store.js,renderer.js, etc.0.4
somehow enable us to split authentication to a separate repo, which we include into the example app.
will require us to describe a "dogstack plugin" as a set of topic directories, where each topic directory has files at specific file paths that determine what the file is doing. these files are then automatically composed into the app.