PlexIntroEditor VS sqlitebrowser

That has turned into Plex Intro Editor, an app that allows you to add, edit, and delete intro markers for episodes in your library. You can view stats (X episodes have no markers, Y have 1, etc), add a marker to an episode that Plex couldn't detect, shift all markers for a season forward 2 seconds, add an extra marker if a show has multiple intros, and pretty much anything else you might want to do with an intro marker.

It also linked to an intro editor I made that makes it easier to add/edit/delete markers, though there is a fair bit of initial setup required to get it running.

It also includes a link to an in-progress PlexIntroEditor project I've been working on, which adds a nicer UI layer that allows you to manually edit markers: https://i.imgur.com/oYzKv0h.png. It definitely hasn't been heavily tested, but should be fine for just editing existing markers.

If you're really brave, I created this program that makes it a bit easier to modify (or even add/remove) markers, but it's not heavily tested, is not polished (i.e. very likely has bugs) because my real job got in the way, and while editing existing markers shouldn't cause issues, adding/deleting them is completely unsupported by Plex so has the potential to break if Plex changes how intro markers are stored.

If you're really brave, and willing to run a stranger's first ever Node project, I've been working on a tool for myself that makes editing/adding/deleting intro markers a bit easier, though as the project mentions, is far from polished/bug free, and is very much a work in progress.

We have a spread of different GitHub Actions based workflows that do stuff whenever a PR is proposed or merged:

https://github.com/sqlitebrowser/sqlitebrowser/tree/master/....

Most of those are oriented around building packages for various OS's (Linux, macOS, Windows) so people can try the latest code.

While there are some tests, they're more like extremely basic sanity tests and don't rely on Docker.

Those tests rely on whichever version of SQLite was downloaded and compiled into the GUI (as per above code snippet).

---

That being said, that's for the client side GUI application. There's a server side of things too (https://github.com/sqlitebrowser/dbhub.io -> dbhub.io) that does use docker for it's automated tests:

https://github.com/sqlitebrowser/dbhub.io/tree/master/.githu...

Those are integration tests though (eg "make sure we didn't bust communication with our cli", "make sure our go library still works 100% with the server"), and a reasonably decent set of End to End (E2E) tests of the web interface using Cypress.

---

Does that help? :)

Do you know about SQLite DB Browser ? It's a multi platform application that would perfectly fit your use case :).

https://sqlitebrowser.org/

Someone gave you a sqlite database. You probably started to think to install a program like sqlitebrowser, but only to view and read the data. Don't bother, you can use this extension instead.

Try https://sqlitebrowser.org/ it’s great for local use and training purposes

You can see how the db file looks for the app using https://sqlitebrowser.org/

If you want to fiddle with SQLite and don't need all the power herein, I recommend DB Browser for SQLite.

https://sqlitebrowser.org/

Hello y'all. This is my first post here. I'm learning SQL with the Northwind database. When I run a "big" query, like "SELECT * FROM Customers" the application crashes. I noticed this only happens when I run a general query, for example, if I run something more specific (and, by the hand "smaller") it doesn't happen. So, I thought it could be related to the size of the query. But I'm a total beginner so idk. It doesn't happen every time I try to use it, but still, this is frustrating. If there's no solution, what other SQL application can I use to keep learning? I found something on GitHub but this is for an older macOS version.