Revision as of 03:33, 12 August 2022

Agenda

Updates on anything Darin's been doing
Ideas / questions from Jonathan and Godwin re: planning for a weekend coding sprint
Check in about scheduling the weekend coding sprint

godwin - API on serverside.
maybe nextjs on front and back
richtext rendered on the front end and ??? on the back
boilerplate out there now should be pretty easy to get off the ground
jonathan - is using feathers. feathersjs -there's not a good comparison to nextjs
godwin - react stable, been used for years, seems like it's sticking around - what is feathersjs? react?
jonathan - easy way to put together an API. featthers just handles API. you write usenode you use js to write it. database agnostic. mongo, psql, etc
godwin - sounds like maybe we could use both
jonathan - https://feathersjs.com/comparison
godwin would use mongo if starting now
jonathan - feathers handles sockets, too. supposed to be really easy to use. any socket library you want to use. extremely versatile. just a framework that creates api. not locked into anything.
godwin - if we use nextjs and feathers (looks from google like lots of people do that) would we have one server that does api and one that does rendering or would we want one service/stack that does service and rendering?
jonathan - thinks they should be separated
godwin - my experience starts to break down @ ___. one linux machine does everything and these days people distribute that more. is that the right way to go? is it cost-effective in money?
jonathan - we could do that in the future if the service becomes super popular. different instnace.s something easy to do, run server somewhere else. to begin, easiest just to have one nice vps. linode or ___. either/or.
godwin wants to move off digital ocean. ___ is alot cheaper for us. been a long time since godwin has looked into it. digital ocean used to be the cheap option
jonathan - something called raftnerd has specials. $50 for a year with 4G. basically the same __ you get with linode. i use linode to handle vps and stuff and it's working surprisingly well. it's ___ and stuff. no problems with their server and rack node. get their specials. $100 for 8G. That would be one kpm instance. good way to start out. sysadmin experience. happy to set up docker for everything. coobenaties?
godwin - and that's all the stuff I'm pretty lost on so if there's any of that you want to plan for/start setting up?
jonathan - will start looking into it.

@@ Line 19: / Line 19: @@
 * jonathan - feathers handles sockets, too.  supposed to be really easy to use.  any socket library you want to use.  extremely versatile.  just a framework that creates api. not locked into anything.
 * godwin - if we use nextjs and feathers (looks from google like lots of people do that) would we have one server that does api and one that does rendering or would we want one service/stack that does service and rendering?
-* jonathan -
+* jonathan - thinks they should be separated
+* godwin - my experience starts to break down @ ___.  one linux machine does everything and these days people distribute that more. is that the right way to go? is it cost-effective in money?
+* jonathan - we could do that in the future if the service becomes super popular. different instnace.s  something easy to do, run server somewhere else. to begin, easiest just to have one nice vps.  linode or ___.  either/or.
+* godwin wants to move off digital ocean.  ___ is alot cheaper for us.  been a long time since godwin has looked into it. digital ocean used to be the cheap option
+* jonathan - something called raftnerd has specials.  $50 for a year with 4G.  basically the same __ you get with linode.  i use linode to handle vps and stuff and it's working surprisingly well.  it's ___ and stuff. no problems with their server and rack node.  get their specials.  $100 for 8G.  That would be one kpm instance. good way to start out.  sysadmin experience. happy to set up docker for everything.  coobenaties?
+* godwin - and that's all the stuff I'm pretty lost on so if there's any of that you want to plan for/start setting up?
+* jonathan - will start looking into it.