Fly · Set-up and going live · about 45 minutes
Your logbook with Git
The picture: The logbook on board, with a copy in the harbour
What it's about
Every ship has a logbook: who did what, when, and why? Git is that logbook for your project. Every entry records a state you can go back to. A copy is kept in the harbour, at Albatros on code.aufwind.sh. Even if your computer falls in the water, nothing is lost.
What you'll learn
- what an entry in the logbook is (commit) and what a good note for it looks like
- how the copy gets to the harbour (push)
- why you only enter your own changes
How you go about it
- Have a look around the harbour: your logbook is already there, with the template in it.
- Fetch the logbook onto your computer.
- Change something, enter it, send it to the harbour. Twice.
- Check whether the entries have also arrived on your server, in the folder
~/projekt.
Done when
- your logbook has at least two entries on
main: with Light in the harbour, with Pilot also in~/projekton your server.
How Albatros can tell it worked
- ~/projekt is a Git logbook with at least 2 entries.