Tag: Flyway

I saw a post that Flyway Desktop has a dark mode and I had to try it out.

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.

Dark Mode

In general, I’m not a big dark mode person. I tend to use browsers in light mode, like this:

I regularly work in VSCode, which is light for me.

And of course, SSMS is light. I know lots of people have wanted a dark mode, and you can configure that, but it’s a mess. To me, I just like light mode.

However, someone posted a note internally a Redgate thanking engineers for dark mode.

Wha??? I had to try it.

It looks interesting.

I don’t know if I’ll use it, but it’s easy to enable, and I can switch anytime. In the top bar, there are a number of icons. There’s a moon for one, which you see above and below, because I’m in dark mode.

If I click the left-most one above, I see this:

Now I have a sun, and a light mode.

This works on all tabs, on the VCS blade, and it gives you the option to work with either a white or dark background.

That’s pretty cool. I don’t care so much, but I know lots of people do, so they now get the option.

Try Flyway Enterprise 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:

Flyway Desktop changed the navigation and a few people were surprised. I was as well, so I decided to do a short tip on the changes.

This is part of a series of posts on Flyway.

The Old Flyway Desktop

If you’ve been following these tips, or worked with the Flyway Enterprise system, you’ve encountered Flyway Desktop, and you might have seen something that looked like this, with the navigation across the top of the screen. We see four “tabs”, called Schema model,
Generate Migrations, Migrations, and Version Control:

As part of a design refresh, we moved the version control tab to the right side as a bar, which shrinks it, but also gives information while a developer is working. I covered this in a previous tip. You can see that design below.

We weren’t done and I was surprised how quickly we made another change.

Flyway Desktop v7

This was actually in v7.0.5, which released Jan 11. We moved all the tabs to the side, though this time the first three moved to the left. As you can see below, I have the migrations tab selected and the nav is on the side panel.

The same three tabs are there, but now on the left, and what’s more, I can shrink this panel to a bar, which gives me more room in which to see code and work with my changes. The VCS tab is still on the right, with icons to let me know when I have changes to push, pull, or fetch.

Summary

This might not seem like much, but it’s a nice visual change and it gives us the ability to add more features in tabs, without running out of room or squeezing things at the top. Over time, a few more pieces of functionality will appear here as we continue to expand the capabilities of the tool.

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:

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.

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.

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).

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.

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).

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.

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

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.

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.

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

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: