engrmarkk / altschool-python

Python (Flask) lessons from AltSchool Africa

Explore the docs »

Report Bug · Request Feature

---

Table of Contents

1. About This Project
• Built With
2. Usage
3. License
4. Contact
5. Acknowledgements

back to top

---

Hello and Welcome! 👋🏾

---

About This Project

This is a repository containing all notes and files created while learning Backend Development with Python (Flask) at AltSchool Africa.

Built With:

back to top

---

Usage

If you like this structure and want to use it for your own notes or just go through for tips and practice, follow these steps:

1. Fork the original repo on GitHub
2. In your terminal, cd into the folder you use for AltSchool or Programming on your computer:
   eg: cd ~/AltSchool
3. Clone the repo from your personal GitHub into the folder:
   git clone https://github.com/YourGitHubUsername/altschool-python
4. Feel free to rename the cloned folder. This is entirely optional:
   mv altschool-python Python
5. CD into the cloned folder:
   cd altschool-python (or cd Python if renamed)
6. Add an upstream, which links to the original GitHub repo:
   git remote add upstream https://github.com/Ze-Austin/altschool-python
7. Create and move into a new branch (preferably using your name or GitHub username for this repo):
   git checkout -b YourName
8. Open the folder in your IDE to make your own notes and play with code files. Try it. Break it. Fix it. Repeat. To open the current folder in VSCode from the terminal:
   code .
   • If this doesn't work, google "add code to PATH"
9. When you're done for the session:
   • Stage your changes on git by adding them:
     git add . or git add file.name
   • Then commit the staged changes:
     git commit -m 'message here'
   • Alternatively, you can add and commit at once:
     git commit -am 'message here'
10. Push the changes to your branch:
    git push origin branchname
11. This is when you'll usually create a pull request on GitHub, but please don't. There's no point in merging everyone's personal notes
12. Update your workflow with my weekly updates by following these steps in order:
    • Move into main:
      git checkout main
    • Update main with changes from my GitHub repo (upstream):
      git pull upstream main
    • Push my changes to your forked GitHub repo (origin), for online storage:
      git push origin main
    • Move into your named branch:
      git checkout branchname
    • Update your named branch with changes from main:
      git merge main
    • Make any changes you want to, then return to Steps 9 & 10.

Note: Every time you want to work on this repo, ensure that you've checked out into your branch to freely make/edit your notes without affecting others:
git checkout branchname

Caveat: I use a MacBook, so the notes and files about installation and features might differ from what would apply to your computer. Trust LMS, Live Classes and Google for a better-tailored experience.

Timeline: I usually update this repo some hours after the latest class, and then announce on Slack. Caleb's (and any other Python tutor's) folder will be updated when we get the files on Slack.

Bonus: There's a Git Cheat Sheet file in here. It helps with reminders and explanations of Git commands in the Terminal. Further explanation can be found online.

Please don't send pull requests

back to top

---

License

Distributed under the MIT License. See LICENSE for more information.

back to top

---

Contact

Dr Austin Wopara - @Ze_Austin - [e-mail]

Project Link: AltSchool Python

back to top

---

Acknowledgements

This project was made possible by:

• AltSchool Africa School of Engineering
• Caleb Emelike's Python Classes at AltSchool
• Kehinde Ogunyale's Python Lectures at AltSchool
• GitHub Student Pack
• Othneil's README Template
• Ileriayo's Markdown Badges
• Stefan's GitHub Light vs Dark Demo
• Stack Overflow

back to top

---

Thanks for dropping by. Have fun! 💜

---