Common C libraries and data structures

Posted on by

Today I discovered: Common C libraries and data structures. (C99) over on github. So awesome.

I really like the project layout too. Each module in a directory with an example, a bunch of tests, and some documentation to go along with the code. I feel like this is how it should be done. I think today I grew as a programmer because I read this code.

The psychology of digital marketing

Posted on by

I stumbled upon this great video today: The psychology of digital marketing. Rory Sutherland, Ogilvy.

“The thing you’ve got to remember about research is, if people are annoyed about something or upset about something, they’re sincere about being upset, but their reasons for being upset are bullshit. Okay? They just reach off the shelf and go and find a plausible post-rationalisation for their emotional state.”

Docker Essentials

Posted on by

Today I am hoping to learn a little about Docker, and I have found this series of four articles I intend to read:

I will also need to do some reading on Docker and MySQL.

Also Leo says: btw about docker, I’d prefer not to create new images for docker hub, I’d rather have the images get built directly on the server where it’s running. All from a single docker compose file, so probably just with docker compose build paths. Yes, ok so:

  • I want a docker-compose.yml file in a folder, which would automatically build/start the relevant services
  • leave room for an .env file with options like port and other relevant stuff (https://docs.docker.com/compose/environment-variables/)
  • make the wiki image get built using a Dockerfile, probably located in one of the subfolders (https://medium.com/@zhao.li/how-to-understand-building-images-with-docker-compose-24cbdbc0641f)
  • docker containers are supposed to be immutable (they arent, but should be treated as if they are). So make sure the docker-compose file lists all the relevant volume mounts (using relative paths on the host, so that they end up in the same folder as the docker compose file) to things like the database and other persistent data

though I guess the more general requirements would be:

  • It should all be contained in a single folder (again, with a docker-compose.yml at the root of it most likely)
  • I should be able to move the folder around wherever I want while the compose stack is down
  • The containers shouldn’t contain any persistent data. I should be able to start, stop, delete, re-build any containers in the stack (probably only one container, but maybe you’ll include more) without any data being lost.