mastodon.gamedev.place is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server focused on game development and related topics.

Server stats:

5.2K
active users

#copy

1 post1 participant0 posts today
(1784–1836). Made in bronze by “Compagnie des Bronzes” in Brussels, 1900. 💿

(Source: Rijksmuseum)

This statue is a copy of a marble sculpture from 1828, which was made for the Duke of Devonshire. ©️

The original is located at Chatsworth House in England, while the plaster model is preserved in Brussels. In 1900, this model was used to cast the bronze version for “Rijksmuseum”. 🏛️

#amsterdam #discuswerper #discusthrower #sculpture #museum #athlete #bronze #art #matthieukessels #copy #artiseverywhere #statue
Replied in thread

@rl_dane I am thanking you for pointing me to the books of that writer who gave them away for a short period at Amazon

A question I have now before doing any research; is there a command available where I can just copy my books that are within my Kindle library, convert them to the standard ebook format so that they can have them forever, because now I don't have a copy of the books Amazon has them

Replied in thread

Ein drei Jahre altes Basis-Dockerfile, mit dem ich mit Multi-Stage-Builds rumgeeimert habe.

Das Build-Image baut eine Compile-Umgebung auf, und baut dann aus der requirements-frozen.txt die notwendigen Wheels.

Die werden dann ins Deploy-Image rüber getragen. Dort wird dann auch der Code importiert (der hier nicht groß ist – es ist kaum mehr als ein hello_world.py).

Ich habe eine requirements.txt, die die Dependencies importiert und die so das Venv baut.

Dann mache ich ein

(venv) $ pip freeze -r requirements.txt > requirements-frozen.txt
(venv) $

Dies zeichnet nicht nur die bewußt importierten Dependencies auf, sondern auch deren Dependencies, mit fixierten Versionen.

Indem ich das Image mit der requirements-frozen.txt bauen (die mit eingecheckt wird), habe ich im Image dieselben Versionen wie beim Testen.

(base) kk:~ kris$ cd PycharmProjects/dockertest/
(base) kk:dockertest kris$ cat Dockerfile
FROM python:3.10-slim as builder
LABEL maintainer="isotopp" \
description="A test image"

WORKDIR /app

ENV PYTHONDONTWRITEBYTECODE 1
ENV PYTHONUNBUFFERED 1

RUN apt-get update && \
apt-get install -y --no-install-recommends gcc git build-essential

COPY requirements-frozen.txt /tmp/requirements.txt
RUN cd /tmp && pip wheel --no-cache-dir --no-deps --wheel-dir=/tmp/wheels -r requirements.txt

# -----

FROM python:3.10-slim
WORKDIR /app
#COPY --from=builder /tmp/wheels /wheels
#RUN pip install --no-cache /wheels/*

COPY . /app
CMD [ "python3", "-u", "main.py" ]

In earlier days I was using #unison to two-way (mostly manually) sync a directory between hosts. But this is becoming a huge problem, as unison requires the very same version on both sides, and my systems are quite different these days.

What other Linux tools out there can do a reliable two-way sync of a directory?

Edit: use case is manually sync work between multiple devices, not online all the time.

#Linux#Sync#Copy

“When there was only analog #tape, making a physical copy of your tapes was the #backup (aka “safety copy”). One problem is that this is not actually an exact #copy. The backup goes through multiple stages of analog circuitry and cabling, and it ends up residing on a totally different magnetic tape – all factors guaranteeing that it won’t be exactly the same as the original.

Due to tape deck discrepancies or incorrect settings, the copy could even sound different than the original. It also took the industry many years to realize that #analog tapes (primary or backup) might not last forever, and, due to poor storage and sticky-shed syndrome, many old tapes have been pulled out of storage only to have them disintegrate and self-destruct!”

“Are You Backing Up?” — #MikeKosacek / #TapeOp / #music / #recording <tapeop.com/interviews/161/are->