Tag: syndicated

  • A New Word: Altschemerz

    altschmerz – n. a sense of weariness with the same old problems that you’ve always had, the same boring issues and anxieties you’ve been gnawing on for decades, which makes you want to spit them out and dig up some fresher pain you might have buried in your mental backyard.

    Many of us deal with problems over and over in our lives. Sometimes we just don’t have the energy or power to change them. Sometime we don’t know what to do with them.

    Over time, this can wear you down. For me, I have all sorts of problems, fortunately overshadowed by the amazing things I experience.

    As an example, I struggle with anxiety when starting some projects. Not all, but there are some that I don’t complete well enough, or need repeated repairing, and I get challenged to find a new approach or even re-repair something. Sometimes these are things I’ve delayed fixing, sometimes they’re maintenance that creeps up again, sometimes a thing broke. I get anxious and feel challenged, I worry I don’t do well, I don’t want to start and get stuck or stop.

    Rebuilding trailer hubs is one of those things. I can’t decide if maybe the trailer is bent too much, but these keep happening and I wish they didn’t.

    I certainly have other problems, but relatively few. I deal with altschmerz well some days, and not well others.

    From the Dictionary of Obscure Sorrows

  • Updating Teslamate to the Latest Version

    I noticed Teslamate wasn’t updated. In fact, I hadn’t had any data captured in nearly a month and I’ve been too busy to notice. I was concerned something had happened, but I wasn’t sure what.

    This is part of a series that covers my experience with a Tesla Model Y.

    Troubleshooting

    I saw a few notes online that said to restart things, which I did. When I went to the home page of my installation, everything looked fine, but not data for the last 20 something days. On the settings page, I saw a message that I needed to include an encryption key as an environment variable, nothing else.

    One post said that I should delete the entry in the tokens table in the database to force a new login. So, I did that. I connected to the container with:

    docker compose exec database psql teslamate teslamate

    Then I ran a delete statement.

    2023-12-19 15_39_30-cmd

    When I went back to the home page, I did see a login page. Fortunately, I had the Tesla Tokens app on my phone and it generated new API keys for me. If you don’t have this, you need it.

    I still had the encryption key message and I didn’t have any data, so I decided to upgrade.

    Adding an Encryption Key

    In my Docker Compose file, I decided to add the encryption key. In the old file, I didn’t have the encryption key, so I copied the environment variable from the docs and added this in my file.

    ENCRYPTION_KEY=somekeyvalueImadeup

    No, that isn’t my password, but you can see the file below.

    2023-12-19 15_41_44-docker-compose.yml - PublicDocuments - Visual Studio Code

    Once this was done, I checked the update page and it said to be sure you were on docker compose v2. I wasn’t sure where I was, but I know I hadn’t updated Docker Desktop in awhile, so I went to that app, downloaded the update and applied it.

    Now I was ready.

    Upgrading Teslamate

    This is really easy. This is on the docs page. First, stop your containers with this:

    docker-compose down

    Next, run this

    docker compose pull

    As you can see, it started the update and had to pull down new images.

    2023-12-19 15_45_41-cmd

    Once this was done, I ran docker compose up and things were running. I got to the teslamate page, where it wanted me to log in again. Fortunately, I’d saved my API tokens. I entered them and I was in:

    2023-12-19 15_46_43-Overview - TeslaMate - Dashboards - Grafana — Mozilla Firefox

    Before this, the “Tina” in the upper left dropdown was nul and none of the temp values were populated.

    Hopefully I’ll have this working for some time, but I’ll set a reminder to upgrade things a couple times a year.

  • Friday Flyway Tips–The Version Control Blade

    The Flyway Desktop Version Control tab is gone and a new blade has appeared in its place. This post looks at the changes and what that means for a developer.

    I’ve been working with Flyway Desktop for work more and more as we transition from older SSMS plugins to the standalone tool. This series looks at some tips I’ve gotten along the way.

    The Version Control Tab

    It’s gone. Here’s an old screenshot of what this looked like. It was one of four tabs across the top of a project. Note that this just had the title, with no information.

    2023-12-13 18_01_48-Flyway Desktop

    That’s unlike most other tools that provide VCS features, in that there usually is some status. On the tab, you can see the files to be committed, and push/pull/etc., but you have to select the tab.

    2023-12-13 18_02_45-Flyway Desktop

    We wanted to do better.

    A Version Control Blade and Status Bar

    We realized that version control isn’t really part of the workflow of Flyway Desktop; it’s a separate function. We also had lots of requests to help developers know there are changes in the repo to commit, push, etc.

    We’ve been testing this for some time as a feature flag, which was annoying because I’d see the tab and the blade, but it released recently. I’m not sure which version got this, but it is in 7.0.3.

    You can see it below, on the right side. Note that we have an arrow at the top to expand this. We also have a branch icon, a refresh, which tells you the last time something push/pull/fetch’d, and then there are down arrow (remote commits not pulled), a circle with a line (uncommitted changes), and an up arrow (commits to push).

    2024-01-05 16_39_26-Flyway Desktop

    If I select the object listed, and click Save, I’ll see this after the operation completes I have an uncommitted change. Notice the “1” in the middle of the blade.

    2024-01-05 16_41_53-Flyway Desktop

    I can expand the blade, but I can just click the one (or icon) and I see the blade expand. From here, I can add a commit message and commit this change (if I select it).

    2024-01-05 16_42_01-Flyway Desktop

    I’ll make another change, generating a migration script. Now my expansion shows 3 changes, the schema file, the migration script and the undo script.

    2024-01-05 16_44_44-Flyway Desktop

    I’ll commit these three as one item. My blade closes after this and I see a committed change to push.

    2024-01-05 16_45_40-advocates - Redgate - Slack

    I’ll generate another migration script. In this case, I now see multiple changes. I see my two new migration scripts added, and I still have a commit to push.

    2024-01-05 16_48_43-Flyway Desktop

    If I expand the blade, I can see the details. For example, on the push tab, I can see the commit and files included. For a small screen, or small window, I get a tooltip if I hover and can see the full file name and path.

    Screenshot 2024-01-05 165157

    If I make a change in the remote, likewise, I’ll also see a commit to pull.

    2024-01-05 16_53_57-Flyway Desktop

    I’ll push and pull (and commit) and then I’ll see a clean list nothing in my VCS blade.

    Summary

    This isn’t a big change, and I’d argue this makes FWD much easier to use and more comfortable for many people. Developers are less likely to have their local repo out of synch with a remote.

    Try Flyway Desktop out today. If you haven’t worked with Flyway Desktop, download it today. There is a free version that organizes migrations and paid versions with many more features.

    Video Walkthrough

    I made a quick video showing this as well. You can watch it below, or check out all the Flyway videos I’ve added:

  • A New Word: Candling

    candling – v. intr. the habit of taking stock of your life on the occasion of your birthday, letting it serve as a kind of internal referendum on all your goals and qualities and relationships and accomplishments so far – which makes you want to dress a little nicer that day, as if you’re standing before a parole board that convenes once a year to adjudicate your release from childhood.

    Such an interesting and contradictory definition, at least to me. I like the first part, taking stock, but it’s not as though I’m being judged by others. Of course, this is a dictionary of obscure sorrows.

    Maybe even the “dress nicer” part makes sense to me, as that’s sorrow for me. I like to dress like a bum, or wear wild shirts, and just be comfortable. One of my bucket list items used to be to not wear ties anymore. However, as I age, and I see funerals, I accept it’s important to others I do so at times.

    Enough sorry.

    I used to do this, even in my 20s. I didn’t love attention or celebrations of me, especially on my birthday. They’ve always made me a little uncomfortable, which sounds funny coming from someone that does enjoy presenting and teaching people from a stage. However when I do that, I think it’s about others, and what I can do to help them.

    Many birthdays I went off by myself, at least for part of a day. Biking or on a kayak/sailboard on the water earlier in life, hiking or skiing later, to take stock of where I was and what I wanted to do in life. What direction? I didn’t do a life quest, but I did try to think about the direction in which I wanted to move.

    After getting married, I often used my birthday as a marker to decide if I was happy with my career and if I’d want to do something else. That’s helped me to decide when to continue on with a position and when to move.

    I still do a bit of that, but my candling has become a more regular thing, often when I hear of someone having success in some way, or making a change, or sadly, when someone has passed. And I know often do so with my wife, discussing where I am and what life would be like if I changed something.

    From the Dictionary of Obscure Sorrows