$> 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
- Open linux env
To start with I am using Multipass.
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
- Gretchen Bakke
- Saul Griffith
- 2022 - [Electrify: An Optimist's Playbook for Our Clean Energy Future](https://www.amazon.com/Electrify-Optimists-Playbook-E
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 |
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.
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.
Get the command-line PlantUML from the download page or your relevant package manager.
The history of Silicon Valley, from railroads to microchips, is an “extraordinary” story of disruption and destruction, told for the first time in this comprehensive, jaw-dropping narrative (Greg Grandin, Pulitzer Prize-winning author of The End of the Myth).
Palo Alto’s weather is temperate, its people are educated and enterprising, its corporations are spiritually and materially ambitious and demonstrably world-changing. Palo Alto is also a haunted toxic waste dump built on stolen Indian burial grounds, and an integral part of the capitalist world system.
In PALO ALTO, the first comprehensive, global history of Silicon Valley, Malcolm Harris examines how and why Northern California evolved in the particular, consequential way it did, tracing the ideologies, technologies, and policies that have been engineered there over the course of 150 years of Anglo settler colonialism, from IQ tests to the "tragedy of th
😀 😃 😄 😁 😆 😅 🤣 😂 🥹 🙂 🙃 😉 😊 😇 🥰 😍 🤩 😘 😗