To my sense it's opposite - on a small project use online 3rd party services - no hassle, no worries. Code will be there even after many years.
On a large project (where SLA doesn't satisfy some of the needs/performance) - use in-house git server.
P.S. I am not against RPi's, owning few of them myself.
I guess that make sense, no hassle, just use it for small scale. I think I was lead by the fact - it can be done, I’m gonna try and do it :)
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To my sense it's opposite - on a small project use online 3rd party services - no hassle, no worries. Code will be there even after many years.
On a large project (where SLA doesn't satisfy some of the needs/performance) - use in-house git server.
P.S. I am not against RPi's, owning few of them myself.
I guess that make sense, no hassle, just use it for small scale. I think I was lead by the fact - it can be done, I’m gonna try and do it :)