You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the Raspberry Pi 3 and older we'd need to create an 32-bit arm version of
4
+
processing.
5
+
6
+
Github Actions do not support creating 32 bit runners so we need to host one
7
+
ourselves.
8
+
9
+
## Instructions
10
+
11
+
### Gathering your Tools
12
+
13
+
You will need:
14
+
15
+
- A Raspberry Pi
16
+
- A micro SD card
17
+
- An SD card reader
18
+
- A computer
19
+
20
+
### Flashing the SD Card
21
+
1. Install and open [**Raspberry Pi Imager**](https://www.raspberrypi.com/software/) on your computer
22
+
2. In **Raspberry Pi Imager**:
23
+
- Select your Raspberry Pi model
24
+
- Select "Raspberry PI OS lite (32bit)" as the OS (you may need to look into the sub-menus)
25
+
- Select your SD card
26
+
- Click NEXT
27
+
3. Edit the OS settings:
28
+
- Set a hostname (e.g. `processing.local`)
29
+
- Set a username and password
30
+
- Go to the SERVICES tab and enable SSH with password authentication
31
+
- Click SAVE and Apply the OS customisation settings
32
+
33
+
### Configuring the Raspberry Pi
34
+
1. Take the written SD card and put it into the Raspberry PI
35
+
2. Power it up and wait for it to boot
36
+
3. SSH into the Raspberry Pi using the hostname, username, and password you set earlier
37
+
4. Follow Github's [instructions on how to set up a self-hosted runner](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners). _Note: In the `./config.sh` setup step, you will be prompted to enter a name and other settings. Use default settings by pressing ENTER for each prompt._
38
+
5. Verify that the new runner appears in the list of runners on GitHub.
39
+
6. Quit the the runner in the terminal (we will set it up to run automatically on boot).
40
+
7. Use Github [instructions to setup the runner as a services](https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/configuring-the-self-hosted-runner-application-as-a-service) so it runs on boot.
Copy file name to clipboardExpand all lines: CODE-OF-CONDUCT.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -6,15 +6,15 @@ Processing is a flexible software sketchbook and a language for learning how to
6
6
7
7
We make room for people to get involved in the project at any point they wish. This means that we:
8
8
9
-
* Welcome contributors at any stage of their programming journey, from newcomers to professionals;
9
+
* Welcome contributors at any stage of their journey, from newcomers to professionals;
10
10
* Do not assume knowledge or imply there are things that somebody should know;
11
11
* Understand that people are the experts of their own experiences, and bring a variety of valid perspectives to the development of open source projects;
12
12
* Know that contribution is not just limited to code, and can also include working on documentation, filing issues and bug reports, and other important forms of input;
13
13
* Work to offer help and guidance when we are able to do so.
14
14
15
15
## Our Standards
16
16
17
-
All developers who contribute to the Processing project agree to abide by the following code of conduct.
17
+
All contributors to the Processing project agree to abide by the following code of conduct.
0 commit comments