|
1 |
| -# template-livecode |
2 |
| -Template for livecode repositories (e.g., SWC) |
| 1 | +# Livecode repository |
| 2 | + |
| 3 | +## For learners |
| 4 | + |
| 5 | +This repository keeps track of the code being written by the instructor. |
| 6 | +Use it to catch up or as a reference when running into errors. |
| 7 | + |
| 8 | +The folder structure is a good starting point when creating a project yourself. |
| 9 | + |
| 10 | +## For instructors |
| 11 | + |
| 12 | +Use [gitautopush](https://pypi.org/project/gitautopush/) to automatically push your livecode to this repository. |
| 13 | + |
| 14 | +### Prerequisites |
| 15 | + |
| 16 | +- Python and pip installed |
| 17 | +- Git installed |
| 18 | +- GitHub account added to the repository as a Contributor |
| 19 | + |
| 20 | +### Installation and usage |
| 21 | + |
| 22 | +- in a first terminal window `git clone` this repository to create a tracked working directory |
| 23 | +- if you already cloned this repository a while ago, `git pull` to avoid conflicts |
| 24 | +- in a second terminal window, install gitautopush with `pip install gitautopush` |
| 25 | +- in this second terminal window, start observing the folder with the command: `gitautopush --sleep <INT> /path/to/my/repo/folder`. `<INT>` is the amount of time (in seconds) between attempts to synchronise the code in the local repository with the remote |
| 26 | +- save the files in the working directory often and regularly (or automatically) |
| 27 | +- double check in the second terminal window if gitautopush automatically pushes your changes to the repository: in case of failure, the errors `git` throws should be inside the message of gitautopush |
| 28 | +- once you finish your lesson, close gitautopush in the second terminal window with <kbd>Ctrl</kbd>+<kbd>C</kbd> or close the terminal window altogether |
| 29 | + |
| 30 | +### Troubleshooting |
| 31 | + |
| 32 | +- ValueError: A `git status` command didn't work, are you sure this is a git repository? |
| 33 | + - It might be occuring when there are already some changes to be staged once you launch `gitautopush`. First, run `gitautopush`, then start creating files or making changes to the existing ones. |
| 34 | + - Another thing to try is to first commit and push one file manually to the repository, once you have done that and no changes are staged run `gitautopush` |
| 35 | + |
| 36 | + |
0 commit comments