• (nodebb)

    It's a great system. They should setup another bot to commit the current date and time, the website visitor's client IP address, and the web server uptime. All of these should be separate jobs (god forbid combining them into one execution), and a CI/CD run to deploy the new code to the server.

  • Hanzito (unregistered) in reply to Mr. TA

    A good idea. While they're at it, why not create a separate branch for each user, and CI/CD that to the user's URL? That way, you can update the content all in one place. DRY, baby!

  • (nodebb)

    Much like the rest of the team, Justin found that there were bigger issues to tackle.

    If I was in Justin's situation, my "bigger issue to tackle" would be "how soon can I get an updated CV out to recruiters?" ...

  • Jaloopa (unregistered)

    I know I've seen a git-SQL adapter out there, that lets you query your Git history via SQL, which tells me we could just stop using databases and use Git from now on. It'll be great!

    Or stop using Git and track history in databases

  • (nodebb)

    Wouldn't the best option (if you had to keep these bot commits) be to have a separate branch that was rebased (or merged) against master/main. Then the bot would update THAT branch, which would then go into their web server?

  • Tinkle (unregistered)

    Wouldn't the best solution be to drop the download count?

    I do not do web development, but my thoughts are:

    Hmm, isn't a download counter a solved issue already? Why reinvent the wheel like this?

  • (nodebb)

    Hmm, isn't a download counter a solved issue already?

    There's a meme about keeping your hands warm while riding a bicycle. I think this falls into that category.

  • (nodebb)

    Stinky is right!

  • (nodebb) in reply to n9ds

    I don't know that meme and I am afraid to look it up.

  • (nodebb) in reply to TheGreatLobachevsky

    I don't know that meme and I am afraid to look it up.

    It isn't really that scary. It's just a bunch of people discussing different ways (all more or less, usually more, in the spirit of Heath Robinson or Rube Goldberg) to keep their hands warm while riding a bicycle, spiked in the end by some who just says, more or less, "why not just wear gloves?".

  • (nodebb)

    I had worked for a financial firm that kept one set of pricing data in VCS. There was a new commit daily. I don't know which is worse. :-)

    The normal download counter doesn't keep a history of dates. With this system, you can see how many downloads were done on October 3, 1981, for example.

  • (nodebb)

    If I wanted to do a download counter on my site (which is static generated, BTW), this Git method would be how it would be handled.

  • (nodebb)

    When the only tool you have is a single coke bottle, it gets used as a hammer. And a container. And a ...

  • Fizzlecist (unregistered) in reply to WTFGuy

    When you have a fully stocked toolkit, but the only thing you know how to use is the coke bottle you've just finished drinking...

  • (nodebb) in reply to Rick

    How about a database table which has a row for each download with d/t, IP, session ID or user ID, etc. etc.? You get the count, the detailed history, and no source control commits to boot!

  • (nodebb) in reply to Jaloopa

    That's called fossil.

  • Jaloopa (unregistered) in reply to n9ds

    https://thedailywtf.com/articles/the_complicator_0x27_s_gloves

Leave a comment on “A Countable”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article