LMU PEM2 20 21 - Revision history

Mayersven at 13:20, 12 June 2024

2024-06-12T13:20:38Z

← Older revision		Revision as of 15:20, 12 June 2024
Line 25:		Line 25:
	* Using Jenkins for creating a CI/CD pipeline: https://pimylifeup.com/jenkins-raspberry-pi/		* Using Jenkins for creating a CI/CD pipeline: https://pimylifeup.com/jenkins-raspberry-pi/

	[[Category:~~Course~~]]		[[Category:Courses]]

Mayersven at 13:19, 12 June 2024

2024-06-12T13:19:41Z

← Older revision		Revision as of 15:19, 12 June 2024
Line 24:		Line 24:
	* Git basics in under 10 minutes: https://www.freecodecamp.org/news/learn-the-basics-of-git-in-under-10-minutes-da548267cc91/		* Git basics in under 10 minutes: https://www.freecodecamp.org/news/learn-the-basics-of-git-in-under-10-minutes-da548267cc91/
	* Using Jenkins for creating a CI/CD pipeline: https://pimylifeup.com/jenkins-raspberry-pi/		* Using Jenkins for creating a CI/CD pipeline: https://pimylifeup.com/jenkins-raspberry-pi/

			[[Category:Course]]

Skwhadmin: /* Tasks & Schedule */

2021-02-12T15:59:40Z

Tasks & Schedule

← Older revision		Revision as of 17:59, 12 February 2021
Line 9:		Line 9:
	=== Schedule ===		=== Schedule ===
	* 29.01. and 12.02.: PEM2 session (Update on milestones, Q&A)		* 29.01. and 12.02.: PEM2 session (Update on milestones, Q&A)
			* 26.02.: PEM2 session (Q&A and updates on projects)
	* 12.03. 4pm: Final presentations		* 12.03. 4pm: Final presentations

Skwhadmin: /* Tasks & Schedule */

2021-01-22T16:10:19Z

Tasks & Schedule

← Older revision		Revision as of 18:10, 22 January 2021
Line 9:		Line 9:
	=== Schedule ===		=== Schedule ===
	* 29.01. and 12.02.: PEM2 session (Update on milestones, Q&A)		* 29.01. and 12.02.: PEM2 session (Update on milestones, Q&A)
	* 12.03 ~~(tentative)~~: Final presentations		* 12.03. 4pm: Final presentations

	= Projects =		= Projects =

Skwhadmin: /* Tasks */

2021-01-22T15:58:38Z

Tasks

← Older revision		Revision as of 17:58, 22 January 2021
Line 1:		Line 1:
	This is the course [https://www.um.informatik.uni-muenchen.de/studium_lehre/ws2021/pem2/index.html PEM2] at LMU in Winter Term 2020/21.		This is the course [https://www.um.informatik.uni-muenchen.de/studium_lehre/ws2021/pem2/index.html PEM2] at LMU in Winter Term 2020/21.

	= Tasks =		= Tasks & Schedule =

	=== Current ~~Task until 18.12.20~~ ===		=== Current Tasks ===
	* ~~Set up a web server~~ on ~~the Pi Zero that can be accessed from a computer/device in the same local network, i.e. calling a webpage.~~		* Work on your milestones
	** Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the ~~last minute or when it was last pressed. Think about how~~ to ~~realize data persistence.~~		* Use the Wiki to update this process
	** The user should be able to control actuators via the webpage, e.g. turning an LED on and off
	** Remember: You already collected and curated references for creating a webserver earlier (see Resources below)

	* ~~Explore options for sharing project source files within the team, e~~.g. ~~versioning or continuous integration~~		=== Schedule ===
	** You can use the LRZ gitlab: https://gitlab.~~lrz~~.~~de/~~		* 29.01. and 12.02.: PEM2 session (Update on milestones, Q&A)
	** Alternatively, ~~you could use a private or public GitHub repository (ask the other team members what they prefer~~)		* 12.03 (tentative): Final presentations
	** One approach: Push code from your computer to the repository and pull the changes from the repository onto the Pi Zero
	** Alternatively setup a Continuous Integration / Continuous Deployment pipeline. ~~This requires~~ (~~way~~) ~~more effort in the initial configuration but does not (ideally) require any manual intervention anymore afterwards when you push changes into your repo.~~

	= Projects =		= Projects =

Sebastian feger at 17:38, 11 December 2020

2020-12-11T17:38:09Z

← Older revision		Revision as of 19:38, 11 December 2020
Line 11:		Line 11:
	* Explore options for sharing project source files within the team, e.g. versioning or continuous integration		* Explore options for sharing project source files within the team, e.g. versioning or continuous integration
	** You can use the LRZ gitlab: https://gitlab.lrz.de/		** You can use the LRZ gitlab: https://gitlab.lrz.de/
	** Alternatively, you could use a private or public GitHub repository		** Alternatively, you could use a private or public GitHub repository (ask the other team members what they prefer)
	** One approach: Push code from your computer to the repository and pull the changes from the repository onto the Pi Zero		** One approach: Push code from your computer to the repository and pull the changes from the repository onto the Pi Zero
	** Alternatively setup a Continuous Integration / Continuous Deployment pipeline. This requires (way) more effort in the initial configuration but does not (ideally) require any manual intervention anymore afterwards when you push changes into your repo.		** Alternatively setup a Continuous Integration / Continuous Deployment pipeline. This requires (way) more effort in the initial configuration but does not (ideally) require any manual intervention anymore afterwards when you push changes into your repo.

Sebastian feger at 17:37, 11 December 2020

2020-12-11T17:37:33Z

← Older revision		Revision as of 19:37, 11 December 2020
Line 7:		Line 7:
	** Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.		** Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.
	** The user should be able to control actuators via the webpage, e.g. turning an LED on and off		** The user should be able to control actuators via the webpage, e.g. turning an LED on and off
			** Remember: You already collected and curated references for creating a webserver earlier (see Resources below)

	* ~~Consider~~ options for sharing project source files within the team, e.g. versioning or continuous integration		* Explore options for sharing project source files within the team, e.g. versioning or continuous integration
	** You can use the LRZ gitlab: https://gitlab.lrz.de/		** You can use the LRZ gitlab: https://gitlab.lrz.de/
	** ...		** Alternatively, you could use a private or public GitHub repository
			** One approach: Push code from your computer to the repository and pull the changes from the repository onto the Pi Zero
			** Alternatively setup a Continuous Integration / Continuous Deployment pipeline. This requires (way) more effort in the initial configuration but does not (ideally) require any manual intervention anymore afterwards when you push changes into your repo.

	= Projects =		= Projects =
Line 22:		Line 25:
	* https://www.sketching-with-hardware.org/wiki/Raspberry_Pi		* https://www.sketching-with-hardware.org/wiki/Raspberry_Pi
	* Remote variable sharing: https://www.sketching-with-hardware.org/wiki/Tutorial_Network		* Remote variable sharing: https://www.sketching-with-hardware.org/wiki/Tutorial_Network
			* Git basics in under 10 minutes: https://www.freecodecamp.org/news/learn-the-basics-of-git-in-under-10-minutes-da548267cc91/
			* Using Jenkins for creating a CI/CD pipeline: https://pimylifeup.com/jenkins-raspberry-pi/

Skwhadmin: /* Current Task until 18.12.20 */

2020-12-11T16:04:33Z

Current Task until 18.12.20

← Older revision		Revision as of 18:04, 11 December 2020
Line 5:		Line 5:
	=== Current Task until 18.12.20 ===		=== Current Task until 18.12.20 ===
	* Set up a web server on the Pi Zero that can be accessed from a computer/device in the same local network, i.e. calling a webpage.		* Set up a web server on the Pi Zero that can be accessed from a computer/device in the same local network, i.e. calling a webpage.
	** 1. Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.		** Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.
	** 2. The user should be able to control actuators via the webpage, e.g. turning an LED on and off		** The user should be able to control actuators via the webpage, e.g. turning an LED on and off

	* Consider options for sharing project source files within the team, e.g. versioning or continuous integration		* Consider options for sharing project source files within the team, e.g. versioning or continuous integration

Skwhadmin: /* Current Task until 18.12.20 */

2020-12-11T16:04:24Z

Current Task until 18.12.20

← Older revision		Revision as of 18:04, 11 December 2020
Line 4:		Line 4:

	=== Current Task until 18.12.20 ===		=== Current Task until 18.12.20 ===
	* Set up a web server on the Pi Zero that can be accessed from a computer/device in the same local network, i.e. calling a webpage. ~~https://www.sketching-with-hardware.org/wiki/Raspberry_Pi~~		* Set up a web server on the Pi Zero that can be accessed from a computer/device in the same local network, i.e. calling a webpage.
	** 1. Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.		** 1. Your web server should be able to read out GPIO states, e.g. you can read out how often a button was pressed in the last minute or when it was last pressed. Think about how to realize data persistence.
	** 2. The user should be able to control actuators via the webpage, e.g. turning an LED on and off		** 2. The user should be able to control actuators via the webpage, e.g. turning an LED on and off

Skwhadmin at 16:03, 11 December 2020

2020-12-11T16:03:57Z

← Older revision		Revision as of 18:03, 11 December 2020
Line 18:		Line 18:

	<br/><b>[[Project: CR, HW]]</b>		<br/><b>[[Project: CR, HW]]</b>

			= Ressources =
			* https://www.sketching-with-hardware.org/wiki/Raspberry_Pi
			* Remote variable sharing: https://www.sketching-with-hardware.org/wiki/Tutorial_Network