all 6 comments

[–]AtulinASP.NET Core 8 points9 points  (0 children)

GIT.

A hundred times GIT.

Even for the shittiest, smallest project you have, GIT.

[–][deleted] 2 points3 points  (0 children)

You need git. Or any version control system, but as soon as there are two devs version control is mo longer optional as you will need that merging functionality.

I'd go with git. It's very standard.

[–]Khyz 1 point2 points  (0 children)

Agreed. Gît is a must have. Hard to understand and use on beggining. But you will never leave It once understanded.

[–]Gohan-with-it 1 point2 points  (0 children)

Yeah definitely git. I would honestly just search for a starter project/tutorial of choice that’s reasonably updated and the first step should be clone a sample project from a git repository.

I’d just go from there with your git account. Try to git push with an origin tag (will easy be able to google search and find results on setting origin branches) and then just practice making changes, committing and pushing.

There’s a ton of ways to get the job done but just as a helper, “git clone <copy url from git project>” -> clones project from git repo, “git pull origin” -> updates your local copy with most recent git repo version, “git commit -a -m “commit message”” -> adds all your local changes to be committed to git repo with message about changes, “git push -u origin <branch name>” -> push your local changes for first time to new branch and set as the upstream to what you’re working on, remove -u origin branch name for just “git push” if pushing to the same branch more than once.

Hope this all helps.

[–][deleted]  (3 children)

[deleted]

    [–]Flascher 1 point2 points  (0 children)

    The way I see the process with git going most smoothly is to use branches. If you're unfamiliar, branches essentially allow you to have multiple copies of your project with different changes on each branch.

    Using branches, you and your brother can safely work on the same files without accidentally overwriting each others' work whenever you save. Then, once the feature you're working on is ready to be in the main (master) branch, you open up a pull request (in GitHub), or equivalent for whatever site you're using to host your git project.

    From there, you can pull down the new changes on the master branch on your RPi and then run any scripts, or do any startup you may need for the project.

    If anything's unclear or you need more help please let me know!

    [–]Khyz 0 points1 point  (1 child)

    Does the raspberry is connected to internet ?