awk
postgres
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awk
-
Awk: Power and Promise of a 40 yr old language (2021)
Yep, functions! I used to write a fair amount of Awk code back in the late '80s and early '90s. I treated Awk as a "real" programming language and tried to make the code nice and readable. This of course involved a lot of use of functions.
I only have a couple of surviving examples of the code from back then, but here they are for the curious:
https://github.com/geary/awk
LJPII.AWK is probably the best example. It made a nicely formatted printout of source code on my HP LaserJet II printer. I wish I had one of the printouts it generated, but they are long gone.
Hmm... I wonder if my Brother printer supports the old LaserJet II control codes? Or maybe there is an emulator online?
The code was written for Thompson Awk (TAWK), so some bits would need to be adapted to modern Awks.
-
Understanding Awk
I used to love Awk! I still do, even if I don't use it much any more.
Awk has a reputation for being hard to read (as noted in stevebmark's comment), but when I was using it actively, I tried to treat it as a serious programming language and write readable programs in it.
Several years ago I tracked down a couple of my old Awk programs from around 1990 and posted them here:
https://github.com/geary/awk
SHANEY.AWK is an implementation of the infamous Mark V. Shaney:
https://www.clear.rice.edu/comp200/09fall/textriff/sci_am_pa...
This was probably the first program that made me really impressed with Awk. People were writing rather complicated Shaney implementations in C, and I thought, "this could be really simple in Awk." And it was!
LJPII.AWK is the Awk program I'm most proud of. This was in the days when we had tiny screens and no multiple monitors and you always printed out your code to read it. In my circles we also fond of inserting "separator lines" between functions, in various formats such as this one:
// - - - - - - - - - - - - - - - - - -
postgres
- How to Escape a Container
-
Problem with Postgres container configuration?
EDIT: Somehow i managed to fix it right now (I struggled with this problem yesterday for hours). This github issue have helped: https://github.com/docker-library/postgres/issues/537 If anyone runs into this problem, those are crucial instructions that helped me: docker system prune docker-compose up --force-recreate --build --remove-orphans --always-recreate-deps --renew-anon-volumes
- PostgreSQL 16 Beta 1 Released!
-
PyPI new user and new project registrations temporarily suspended
Tragedy of the commons - only need a few actors to ruin it all for us. Almost all distributors face this problem, from Docker Hub to PyPI. This also reminded me of official Postgres Docker image running a cryptominer in the background [1]
[1] - https://github.com/docker-library/postgres/issues/770
- [Docker] Point d’entrée Docker-initdb.d Postgres
-
Nix Turns 20. What the Hell Is It?
If you open the dockerfile of the desired container, you can determine exactly how and what was built. If not satisfied, you can always build your own container with the right postgresql build flags.
-
archive_command not being executed?
Ok according to The Dockerfile, postgres is running in /var/lib/postgresql/data so you will need enter the container and look at the log files in /var/lib/postgresql/data/pg_log/
-
How do I create a docker image for postgres with nix?
I got started on trying to make a basic postgres image but I can't seem to figure out how to include a shell script in the same folder as my nix file (fetched from https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh and to be modified once I get it working) into the docker image as an entrypoint
- Postgres on docker works without a shell perfectly but fails when run via shell
-
What exactly is VOLUME used for inside the dockerfile?
See example here : https://github.com/docker-library/postgres/issues/601