What I do in my spare time...

[jmcipale 129]

So last month, after the latest discogs (dischogs?) update borked the Android app (and didnt do the website much in the way of favors either), I began a quest to create

my own music curation library. Creating the database is the easy part, as is downloading my discogs library and filtering out the important features (artist name, title,

year of release and a few other things). I have the DB populated and the install somewhat working and I can do a lot of work from the linux/OSX command-line interface

(CLI). But now the fun begins! My ultimate goal is make this a standalone application that resides on either a desktop or a home network server. My OS of choice is

Debian Linux but the install works on Linux (all flavors), Apple OS, and my Windows 10 VM. 

The fun part begins now: Coding the front-end! The idea is to have this run from a browser (pick a browser, any browser) and allow the user to upload records in

single/batch mode, make edits to an entry and display the data based on search parameters. The fun part will be the API. The tricky part, and this is where I could use

some feedback, creating something that can be accessible to the outside world. 

 

I would ultimately like to design it so that people can use this tool from their own network! This would require configuring their home network/desktop/whatever to

allow outside access over a secure connection. It wouldn't tie into discogs, other than the initial data retrieval of your recordings. This is will simply show the curation 
of music that a given user has. It WILL NOT be located on a central server somewhere (no more sluggish behavior while trying to access discogs back-end). Just a simple 

application that allows you to make changes to your 'inventory'. No silly "Is this a specific pressing? Is it made of yellow vinyl vs black?" sort of nonsense. Just a way to 
track your inventory in a quick, simple browser interface on your home network (or perhaps your ISP if you have access to a and can utilize either MariaDB, MySQL
or SQLite). The best thing is, it is open source and anyone will be able to download it make changes to improve the usability, accuracy, access speed. 

I suppose what I am looking for here is - would anyone be interested in using a tool like this, knowing you would have to be a part-time DB Admin? The good news is,

the data involved would be somewhat small (it isn't like you are managing financial records where you can see upwards of 1.5M entries in a 24 hr period - trust me, it

is a bloody pain in the ass).

 

Thoughts? Ideas? Good idea or total rubbish?


 

Edited December 6, 2025 by jmcipale

[4krow 7,446]

 This may not compute but I have a hard time reading your post with all of the broken paragraphs. 

[Sk1Bum 13,095]

I would probably use, as I now use:

 

dir z:\Music /S /O:N > z:\Music\MusicList.txt

 

Then the tedious task of editing the txt file.

 

I've not used a Linux box since I added a NAS to my LAN, so I've not attempted to export my music library to a sql, mysql or the like. 

 

I did attempt it with Access, and gave up fairly quickly. 

 

[jmcipale 129]

4krow -

 

I tried to format better than what I was seeing from the desktop. Sorry for the poor execution. 

 

Sk1Bum - 

Access was a truly bad idea from m$.