Tech meeting 2022.08.11 - Revision history

Angel: Category:Meetings_and_minutes

2024-11-22T05:10:55Z

← Older revision		Revision as of 05:10, 22 November 2024
Line 5:		Line 5:


			[[Category:Meetings_and_minutes]]

	* godwin - API on serverside.		* godwin - API on serverside.

DarinWick at 04:08, 12 August 2022

2022-08-12T04:08:52Z

Angel at 03:56, 12 August 2022

2022-08-12T03:56:26Z

← Older revision		Revision as of 03:56, 12 August 2022
Line 45:		Line 45:
	* jonathan - open to learning new things, too. eg about react.		* jonathan - open to learning new things, too. eg about react.
	* godwin - same here, needs to sharpen up on react, it's the dominant thing now		* godwin - same here, needs to sharpen up on react, it's the dominant thing now
			* darin - will do his best to be useful where he can. godwin and jonathan know what they're doing. Darin is intern.
			* angel - next meeting? in 2 weeks.
			* godwin - august 25 - 8PST/11EST

Angel at 03:54, 12 August 2022

2022-08-12T03:54:05Z

← Older revision		Revision as of 03:54, 12 August 2022
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.		* 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?		* 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?
			*godwin will start working backwards from the front end and godwin and jonathan can meet in the middle. godwin has very limited time. hosting and serverside needs to be set up first, to build off of.
			* jonathan - we could still use a new server.
			* godwin - doesn't want to go through the process to spin up another server again
			* jonathan - smptp servers and things can get complex. but docker makes it easy!
	* jonathan - thinks they should be separated		* 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?		* 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?

Angel at 03:49, 12 August 2022

2022-08-12T03:49:21Z

← Older revision		Revision as of 03:49, 12 August 2022
Line 31:		Line 31:
	* jonathan - used to use amazons3. now uses backlaze.		* jonathan - used to use amazons3. now uses backlaze.
	* jonathan is using restick. their backup services for docker. does really nice backup service for docker. from sysadmin standpoint is really the way to go		* jonathan is using restick. their backup services for docker. does really nice backup service for docker. from sysadmin standpoint is really the way to go
	* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.		'''* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.'''
	* jonathan - we should have a group password service too. various ways of doing that. eg passable.		* jonathan - we should have a group password service too. various ways of doing that. eg passable.
	* both - like docker. usable, been around a while		* both - like docker. usable, been around a while
	* jonathan started out with distributions. docker is amazing when it came out.		* jonathan started out with distributions. docker is amazing when it came out.
	* angel wants bug and feature request tracker		* angel wants bug and feature request tracker
			* angel wants the api to integrate with OCF
			* godwin - each week we'll do a stepping stone to getting some of these foundational things set up!
			* godwin - doesn't expect to have opinions about a lot of this stuff. godwin and jonathan are a good team, won't get stuck on "we should use this/ we should use this"
			* jonathan - open to learning new things, too. eg about react.
			* godwin - same here, needs to sharpen up on react, it's the dominant thing now

Angel at 03:43, 12 August 2022

2022-08-12T03:43:30Z

← Older revision		Revision as of 03:43, 12 August 2022
Line 35:		Line 35:
	* both - like docker. usable, been around a while		* both - like docker. usable, been around a while
	* jonathan started out with distributions. docker is amazing when it came out.		* jonathan started out with distributions. docker is amazing when it came out.
			* angel wants bug and feature request tracker

Angel at 03:42, 12 August 2022

2022-08-12T03:42:36Z

← Older revision		Revision as of 03:42, 12 August 2022
Line 33:		Line 33:
	* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.		* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.
	* jonathan - we should have a group password service too. various ways of doing that. eg passable.		* jonathan - we should have a group password service too. various ways of doing that. eg passable.
			* both - like docker. usable, been around a while
			* jonathan started out with distributions. docker is amazing when it came out.

Angel at 03:41, 12 August 2022

2022-08-12T03:41:15Z

← Older revision		Revision as of 03:41, 12 August 2022
Line 23:		Line 23:
	* 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.		* 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		* 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?		* 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 kvm 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?		* 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.		* jonathan - will start looking into it.
			* godwin - can you look into costs?
			* jonathan - so what i'm thinking of is @ https://my.racknerd.com/index.php?rp=/store/special-promos go to the bottom and look at 8G kvm. that's still available
			* godwin - that's not so bad! paying about $30/month right now, so that's much better.
			* jonathan - used to use amazons3. now uses backlaze.
			* jonathan is using restick. their backup services for docker. does really nice backup service for docker. from sysadmin standpoint is really the way to go
			* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.
			* jonathan - we should have a group password service too. various ways of doing that. eg passable.

Angel at 03:33, 12 August 2022

2022-08-12T03:33:34Z

← Older revision		Revision as of 03:33, 12 August 2022
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.		* 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?		* 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.

Angel at 03:28, 12 August 2022

2022-08-12T03:28:19Z

← Older revision		Revision as of 03:28, 12 August 2022
Line 17:		Line 17:
	* jonathan - https://feathersjs.com/comparison		* jonathan - https://feathersjs.com/comparison
	* godwin would use mongo if starting now		* 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 -

← Older revision		Revision as of 04:08, 12 August 2022
Line 9:		Line 9:
	* godwin - API on serverside.		* godwin - API on serverside.
	* maybe nextjs on front and back		* maybe nextjs on front and back
	* richtext rendered on the front end and ??? on the back		** richtext rendered on the front end and ??? on the back
	* boilerplate out there now should be pretty easy to get off the ground		** 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		* 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?		* 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		** 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		** godwin - sounds like maybe we could use both
	* jonathan - https://feathersjs.com/comparison		** jonathan - https://feathersjs.com/comparison
	* godwin would use mongo if starting now		* 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.		* 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?		* 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?
	*godwin will start working backwards from the front end and godwin and jonathan can meet in the middle. godwin has very limited time. hosting and serverside needs to be set up first, to build off of.		* godwin will start working backwards from the front end and godwin and jonathan can meet in the middle. godwin has very limited time. hosting and serverside needs to be set up first, to build off of.
	* jonathan - we could still use a new server.		* jonathan - yes, and we could still use a new server, even just fr the existing bikebike.org code
	* godwin - doesn't want to go through the process to spin up another server again		* godwin - doesn't want to go through the process to spin up another server again
	* jonathan - smptp servers and things can get complex. but docker makes it easy!		* jonathan - smptp servers and things can get complex. but docker makes it easy!
	* jonathan - thinks ~~they should be~~ separated		* jonathan - thinks it's a good idea to keep frontend and backend 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?		* godwin - my experience starts to break down @ this point - I'm used to LAMP servers where one linux machine does everything. 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.		* jonathan - we could do that in the future if the service becomes super popular. different instnaces something easy to do, run server somewhere else. to begin, easiest just to have one nice vps. linode or racknerd. 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		* godwin wants to move off digital ocean. linode is a lot 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 kvm instance. good way to start out. sysadmin experience. happy to set up docker for everything. ~~coobenaties~~?		* jonathan - something called racknerd has specials. $50 for a year with 4Gb. basically the same service you get with linode. i use linode to handle dns and stuff and it's working surprisingly well. no problems with their server and racknerd. get their specials. $100 for 8G. That would be one kvm instance. good way to start out. sysadmin experience. happy to set up docker for everything. kubernetes?
	* 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?		* 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.		* jonathan - will start looking into it.
Line 33:		Line 33:
	* jonathan - so what i'm thinking of is @ https://my.racknerd.com/index.php?rp=/store/special-promos go to the bottom and look at 8G kvm. that's still available		* jonathan - so what i'm thinking of is @ https://my.racknerd.com/index.php?rp=/store/special-promos go to the bottom and look at 8G kvm. that's still available
	* godwin - that's not so bad! paying about $30/month right now, so that's much better.		* godwin - that's not so bad! paying about $30/month right now, so that's much better.
	* jonathan - used to use ~~amazons3~~. now uses ~~backlaze~~.		* jonathan - used to use amazon s3. now uses backblaze.
	* jonathan is using ~~restick~~. their backup services for docker. does really nice backup service for docker. from sysadmin standpoint is really the way to go		* jonathan is using restic. their backup services for docker. does really nice backup service for docker. from sysadmin standpoint is really the way to go
	'''* godwin - gives jonathan homework. can you do a writeup? with a plan for the system. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.'''		'''* godwin - gives jonathan homework. can you do a writeup? with a plan for the backend system, starting with the basic services like hosting. we'll still need to talk about the languages we're using, but let's land on services we start paying for and setting up.'''
	* jonathan - we should have a group password service too. various ways of doing that. eg ~~passable~~.		* jonathan - we should have a group password service too. various ways of doing that. eg passbolt.
	* both - like docker. usable, been around a while		* both - like docker. usable, been around a while
	* jonathan started out with distributions. docker is amazing when it came out.		* jonathan started out with distributions. docker is amazing when it came out.
Line 42:		Line 42:
	* angel wants the api to integrate with OCF		* angel wants the api to integrate with OCF
	* godwin - each week we'll do a stepping stone to getting some of these foundational things set up!		* godwin - each week we'll do a stepping stone to getting some of these foundational things set up!
	* godwin - doesn't expect to have opinions about a lot of this stuff. godwin and jonathan are a good team, won't get stuck on "we should use this/ we should use ~~this~~"		* godwin - doesn't expect to have opinions about a lot of this stuff. godwin and jonathan are a good team, won't get stuck on "we should use this/ we should use that"
	* jonathan - open to learning new things, too. eg about react.		* jonathan - open to learning new things, too. eg about react.
	* godwin - same here, needs to sharpen up on react, it's the dominant thing now		* godwin - same here, needs to sharpen up on react, it's the dominant thing now
	* darin - will do his best to be useful where he can. godwin and jonathan know what they're doing. Darin ~~is intern~~.		* darin - will do his best to be useful where he can. godwin and jonathan know what they're doing. Darin and Angel together are some combination of Project Manager and Intern.
	* angel - next meeting? in 2 weeks.		* angel - next meeting? in 2 weeks.
	* godwin - august 25 - 8PST/11EST		* godwin - august 25 - 8PST/11EST