i did a bunch of cli tweaks including that querystring thing. also renamed -g --github as -D --deploy since it's a generic utility
i started thinking that maybe antwar.config.js should be split into two: antwar.config.js and antwar.site.js. former would be just what we have at site field right now while latter would be site specific meta available for each page on rendering stage
this would reduce nesting and make our code a little simpler. in addition it would be easier to just copy a nice antwar.config.js across projects without having to tweak it
you would just define a custom antwar.site.js per site then
also port setting seems too generic. maybe we should have something more specific per target (ie. serve + deployment blocks)
i won't do any changes as i'll wait for your feedback. gotta look into some of the core issues next
eldh 2 hours ago
sounds all good to me. I realized I don’t have anything other than site in the three antwar.config.js files I have here... and yes, being able to define both serve and dev ports would be very good.