Christoph folkengine

2.0.1 Charging Profile

struct ChargingProfile {
    int32_t id;
    int32_t stackLevel;
    ChargingProfilePurposeEnum chargingProfilePurpose;
    ChargingProfileKindEnum chargingProfileKind;

    std::vector<ChargingSchedule> chargingSchedule; // 1..3

™

$> clone https://github.com/US-JOET/everest-demo 
$> cd everest-demo 
$> git checkout branch couryrr/updating-dockerfile-for-testing
$> cd manager
$> docker build --platform linux/amd64 -t ghcr.io/everest/everest-demo/manager:0.0.12 .
$> docker-compose -f docker-compose.automated-tests.yml up

Music Coding

Open linux env

To start with I am using Multipass.

Install Host Packages

https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#build-host-packages

$> sudo apt install gawk wget git diffstat unzip texinfo gcc build-essential chrpath socat cpio python3 python3-pip python3-pexpect xz-utils debianutils iputils-ping python3-git python3-jinja2 python3-sphinx libegl1-mesa libsdl1.2-dev python3-subunit mesa-common-dev zstd liblz4-tool file locales libacl1

Minecraft Resources

Energy Reading List

Communities

Resources

My Personal White Whale:

One of my big goals as a developer of late has been what I call the water principle… (“Be water.” - Bruce Lee. (Yes, the irony of quoting Bruce Lee isn’t lost on me)) Developing should be as simple as possible. When I start a new project, my setup should be as close to a single pushbutton as possible. It should flow like water. For this, I have created my Dev Playbooks. Simple, GitHub templates that I can leverage for the languages I am working in. I go boop, and I have a repo ready to go with all the things I like to have when I am coding something. Things like CI/CD, testing dependencies, etc.

How to use PlantUML with Markdown

PlantUML is a really awesome way to create diagrams by writing code instead of drawing and dragging visual elements. Markdown is a really nice documentation tool.

Here's how I combine the two, to create docs with embedded diagrams.

Step 0: Setup

Get the command-line PlantUML from the download page or your relevant package manager.

	Start testing: Feb 20 19:30 UTC
	----------------------------------------------------------
	1/5 Testing: database_tests
	1/5 Test: database_tests
	Command: "/workspaces/libocpp/build/tests/database_tests"
	Directory: /workspaces/libocpp/build/tests
	"database_tests" start time: Feb 20 19:30 UTC
	Output:
	----------------------------------------------------------
	Running main() from /workspaces/libocpp/build/_deps/gtest-src/googletest/src/gtest_main.cc