Author Topic: Keeping track of source code (Read 3575 times)

mrpackethead · « **Reply #25 on:** January 29, 2019, 09:39:52 am »

Git on AWS code commit. ( its free and private ). every project has a repo.

bd139 · « **Reply #26 on:** January 29, 2019, 09:44:27 am »

You don't need a remote server to run git or push to. Just keep one git repo per project in the project root. Even single file projects get a repo. It's so cheap and quick to do it. Makes experiments cheap to undo as well.

mrpackethead · « **Reply #27 on:** January 29, 2019, 09:53:42 am »

remote server is handy when you are working across multiple locaitons with several machhiunes.

bd139 · « **Reply #28 on:** January 29, 2019, 10:00:53 am »

I solve that by avoiding it.


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

EEVblog Electronics Community Forum

Author Topic: Keeping track of source code (Read 3575 times)

mrpackethead

Re: Keeping track of source code

bd139

Re: Keeping track of source code

mrpackethead

Re: Keeping track of source code

bd139

Re: Keeping track of source code

Share me