mataroa VS golang-samples

I love Mataroa: https://mataroa.blog

I jumped from WordPress to Mataroa and I'm also using Jekyll, Hugo, Zola, and Obsidian to blog.

There are a lot of great things about Mataroa that I love. I've blogged about Mataroa: https://pivic.blog/blog/mataroa/

Same for me, too.

I honestly love https://mataroa.blog it ended my paralysis for searching a blog platform, and every page is bog standard HTML. It accepts Markdown, plus it has its own anonymous analytics, so it's nice.

git clone https://github.com/mataroa-blog/mataroa.git

https://blog.bayindirh.io

It's a semi-regular, assorted blog about my adventures and experiences in life. Generally semi-focused on minimalism, computers and life in general.

It's powered by https://mataroa.blog/, which is very minimal and a joy to use.

I'm using Mataroa[0] as my blogging platform and it comes with its own analytics. It's very simple, and gives me the following:

- Read counts per post, for the last 30 days.

- How many RSS pulls, for the last 30 days.

- How many site visits, for the last 30 days.

Nothing more, nothing less. I'm pretty happy with them, and have no intention to change it.

[0]: https://mataroa.blog

Already in use.

Until this is fixed, anyone would be much better off going for Bear Blog [2] or Mataroa [3].

[1]: https://nicheless.blog/post/learn-one-thing-well

[2]: https://bearblog.dev/

[3]: https://mataroa.blog/

https://smol.pub and https://mataroa.blog are also nice examples. I host my blog in Mataroa, and love the experience so far.

You can find an example of the function code for analyzing the data store on Google Cloud’s Github.

Choose a platform like App Engine. It's auto-scaling. Supports bigtable. And opentelemetry. Manageable from anywhere via Cloud Shell. You can run multiple instances and partition load between them. Even includes a free tier ;)

https://github.com/GoogleCloudPlatform/golang-samples

# Source: https://github.com/GoogleCloudPlatform/golang-samples/blob/master/run/helloworld/Dockerfile FROM golang:1.16-buster as builder # Create and change to the app directory. WORKDIR /app # Retrieve application dependencies. # This allows the container build to reuse cached dependencies. # Expecting to copy go.mod and if present go.sum. COPY go.* ./ RUN go mod download # Copy local code to the container image. COPY . ./ # Build the binary. RUN go build -mod=readonly -v -o server # Use the official Debian slim image for a lean production container. # https://hub.docker.com/_/debian # https://docs.docker.com/develop/develop-images/multistage-build/#use-multi-stage-builds FROM debian:buster-slim RUN set -x && apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y \ ca-certificates && \ rm -rf /var/lib/apt/lists/* # Copy the binary to the production image from the builder stage. COPY --from=builder /app/server /app/server # Run the web service on container startup. CMD ["/app/server"]