You find a good tutorial with all the basics at the Weaveworks
it introduces
#!/bin/bash | |
# Find the primary IPv4-connected interface | |
ipv4_interface=$(ip -4 route | grep default | awk '{print $5}') | |
if [ -n "$ipv4_interface" ]; then | |
ipv4_address=$(ip -4 addr show "$ipv4_interface" | grep -oP '(?<=inet\s)\d+(\.\d+){3}') | |
ipv4_mac=$(cat /sys/class/net/"$ipv4_interface"/address) | |
echo "IPv4 Interface: $ipv4_interface" | |
echo "IPv4 Address: $ipv4_address" | |
echo "IPv4 MAC Address: $ipv4_mac" |
sdg-goal-1: #E5233D | |
rgb(229,35,61) | |
sdg-goal-2: #DDA73A | |
rgb(221,167,58) | |
sdg-goal-3: #4CA146 | |
rgb(76,161,70) | |
sdg-goal-4: #C5192D |
"""Code for handling color names and RGB codes. | |
This module is part of Swampy, and used in Think Python and | |
Think Complexity, by Allen Downey. | |
http://greenteapress.com | |
Copyright 2013 Allen B. Downey. | |
Distributed under the GNU General Public License at gnu.org/licenses/gpl.html. | |
""" |
You find a good tutorial with all the basics at the Weaveworks
it introduces
All newer Raspberry Pi models, like the 3/3+ series, the 4 and also the 400 all have a 64-bit CPU, but the Raspberry Pi OS still works with 32-bit by default for compatibility reasons.
To take full advantage of the capabilities of a 64-bit CPU, you should also run a 64-bit operating system on it. This can speed up some calculations considerably.
A 64-bit operating system can also run 32-bit programs without any problems, so you usually don't have any disadvantages due to software that doesn't run anymore or similar.
Bounded Context defines the scope of a domain model, i.e., it encompasses the business logic for a particular domain.
The inner core is assumed to remain consistent as long as the business use case does not change.
All outer layers are always assumed to change over time, i.e., they are only binding for the current point in time, e.g., when the technology used has reached its final stage of maturity and/or is overtaken by new innovations.
The interfaces/connectors define the interaction between the relevant (data, technology, business, etc.) layers of the domain model.
FROM golang:1.6.2 | |
COPY . /go | |
RUN go get github.com/nats-io/nats | |
RUN go build api-server.go | |
EXPOSE 8080 | |
ENTRYPOINT ["/go/api-server"] |