Today I decided to ditch Flyway Desktop execution from CLI and integrate into my Sway + Wofi desktop environment. Basically, there is what you need:
Get an Flyway icon and paste it into
flyway.svg
fileCopy that SVG file into
$HOME/.local/share/icons/hicolor/scalable/apps/flyway.svg
Change the color for the icon by adding
fill="#CC0200"
to the pathCreate an
$HOME/.local/share/applications/flyway.desktop
file with the content like this:1 2 3 4 5 6 7 8 9 10 11 12
[Desktop Entry] Version=1.0 Type=Application Name=Flyway GenericName=Database migration tool Comment=Database Migrations Made Easy Categories=IDE;Development Keywords=Database;SQL;IDE;JDBC;ODBC;MySQL;PostgreSQL;Oracle;DB2;MariaDB Exec=$HOME/.local/share/flyway/flyway-desktop/flyway-desktop --enable-features=UseOzonePlatform --ozone-platform=wayland --no-sandbox %U Icon=flyway Terminal=false MimeType=application/sql
Because Flyway Desktop is Electron app, we are passing few flags to run it on Wayland system. If you still use Xorg, then just remove those flags.
Copy entire Flyway directory which you downloaded from their archive into the
$HOME/.local/share/flyway
directoryRename the
Flyway Desktop
executable1 2
mv $HOME/.local/share/flyway/flyway-desktop/Flyway\ Desktop $HOME/.local/share/flyway/flyway-desktop/flyway-desktop
This is required so that your desktop entry actually works.
That’s basially it. You might be required to logout from your session. Or just
run update-desktop-database
. This will update the cache and your desktop entry
should show up.
The catch might be with the flyway.desktop
file itself. Deppending which
application launcher you use, it migth be picky about the properties used in the
desktop file. If so… wipe everything. Start just with Exec
and Icon
fields. Icon might be an issue. If you use absolute path, then file extension is
required. If you use just icon name, then don’t include the file extension. Make
sure icon lives in the right path.