feature/DJSv14

[BioCla]

Please describe the changes this PR makes and why it should be merged:
Implements DJSv14.
Contains Major changes, will be going up as a separate version
Read:
#1225
#1223

The code has been almost completely refactored, keeping the same basic structure but reorganizing the Libraries, adding functionality and modularity.
The bot has also been (optionally) containerized, using docker compose contexts, allowing the bot to be developed on any platform.

Tasks:

• Docker context
• Logging System
• DJSv14 Implemented
• Modular commands system
• Music Manager switch (Cosmicord, Erela)
• Updated packages to latest compatible versions
• Credits
• DBMS
• Music commands
• Music client funnel
• Dashboard
• github workflow and templates

v5.1 Beta

Implemented features:

• Playing tracks from playlists saved on DB
• DJ Roles
• dedicated music channels with controller
• increased compatibility with multiple music engines
• A working dashboard
  and some more...

v5.2 Beta

• Figma designs
• Better queues
• Command refactoring
• Fixing bugs and implementing checks
• And more...

v5.3 Full release

• Play, modify queue and control players from the dashboard

Future updates:

v6.0:

• Complete TS rewrite
• Will use Bun
• Automatic version updater (keeps the bot up to date with stable releases)
• CI/CD (if possible)
• Custom wrapper (maybe)???
• Better modular docker configuration

if anyone has suggestions reply to this or create a thread/discussion

PR Status

Status and versioning classification:

• I know how to update typings and have done so, or typings don't need updating
• This PR changes the library's interface (methods or parameters added)
• This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
• Code changes have been tested against the Discord API, or there are no code changes

The update is ready to be merged whenever

[DarrenOfficial]

I think we should create a new branch for this, then push to master v5 once completed.

[LewdHuTao]

So how do you want to add Spotify, Apple Music and Deezer plugins?

I have a few options:

1. Use LavaSrc (tested in my bot that using shoukaku and kazagumo, i can confirm its pretty good)
2. Use kazagumo and shoukaku to add spotify and deezer plugins (stone deezer)
3. Implements own plugins manager which pretty complicated

[Neko-Life]

Good idea. Perfect opportunity for ts rewrite

[BioCla]

@Neko-Life

Good idea. Perfect opportunity for ts rewrite

unfortunately I had already started with JS.
probably gonna have to ask someone to help with that later on. I've been trying to keep track of all the typings in the meanwhile but I have noticed how much easier it would be if we actually had a TS bot instead. Once this base version is done I'll see to start implementing a proper TS version for the bot

[BioCla]

Note: this will go up as 5.1

[BioCla]

Scylla was added in 26a57fb but will be switched out for a PostgreSQL DB with Prisma ORM

[BioCla]

Scylla was added in 26a57fb but will be switched out for a PostgreSQL DB with Prisma ORM

Prisma supports different DB architectures, mostly SQL, but also MongoDB.
Postgresql will be the provided db by default but documentation will be provided for configuration of your own DB

[C-EO]

Will this still be hostable on Replit or shall we have to do on-site hosting?

[BioCla]

Will this still be hostable on Replit or shall we have to do on-site hosting?

I haven't tested it on any deployment ready services and i don't recommend replit anyway.

The bot runs on anything that supports docker or that is docker configurable so you're free to test it however you like. If you're interested in just the bot (without DB and playlist command) then you can extract the djs-bot folder and use that directly, as it is completely modular and separable from the docker compose structure.

[BioCla]

Will this still be hostable on Replit or shall we have to do on-site hosting?

I haven't tested it on any deployment ready services and i don't recommend replit anyway.

The bot runs on anything that supports docker or that is docker configurable so you're free to test it however you like. If you're interested in just the bot (without DB and playlist command) then you can extract the djs-bot folder and use that directly, as it is completely modular and separable from the docker compose structure.

I know this might be a half solution but you could try the method described in this forum post:

https://replit.com/talk/ask/How-to-install-Docker/39255

[C-EO]

@BioCla The new Replit uses NixOS. That means that Docker can't be used because they phased it out. Before, Replit used to be a gigantic Docker container with many Docker instances running. Since it now uses Nix, I can't use the Docker option. I do not want the DB functionality, that's why I'm asking whether this new version of the bot supports Replit?

[BioCla]

@BioCla The new Replit uses NixOS. That means that Docker can't be used because they phased it out. Before, Replit used to be a gigantic Docker container with many Docker instances running. Since it now uses Nix, I can't use the Docker option. I do not want the DB functionality, that's why I'm asking whether this new version of the bot supports Replit?

If you're interested in just the bot (without DB and playlist command) then you can extract the djs-bot folder and use that directly, as it is completely modular and separable from the docker compose structure.

yes... If you want to set it up yourself

[BioCla]

v5.1 now has the dashboard as well, matching v5.0.
v5.1 now enters it's official beta period.

Upcoming features:
Playing from playlists saved on DB
DJ Roles
dedicated music channels with controller (maybe)???
and more...

if anyone has suggestions reply to this or create a thread/discussion

[sprucecellodev125]

@BioCla The new Replit uses NixOS. That means that Docker can't be used because they phased it out. Before, Replit used to be a gigantic Docker container with many Docker instances running. Since it now uses Nix, I can't use the Docker option. I do not want the DB functionality, that's why I'm asking whether this new version of the bot supports Replit?

nonono, It's running Ubuntu (ewww), and yes it have Nix as package manager instead. However if you put pkgs.docker in replit.nix deps, it installs Docker but doesn't make Docker working properly. Since Replit doesn't give you root access, I think you should configure rootless docker (pain)

[ghost]

Hey mate and maintainers :)

I might be misunderstanding something, but according to this readme, it seems I can't configure my own Lavalink server, only the one preconfigured in the docker-compose.yml example.

It would be awesome, if you could make it a Docker ENV, so you could choose your own, since I have mine hosted behind a reverse proxy, and I would like it to keep it that way, instead of using the "default" docker.lavalink.

[BioCla]

@vp-en

Hey mate and maintainers :)

I might be misunderstanding something, but according to this readme, it seems I can't configure my own Lavalink server, only the one preconfigured in the docker-compose.yml example.

It would be awesome, if you could make it a Docker ENV, so you could choose your own, since I have mine hosted behind a reverse proxy, and I would like it to keep it that way, instead of using the "default" docker.lavalink.

as stated in the main README.md:

If you don't want a particular service to start up on make up you can simply comment the block for the service you want to remove from the docker-compose.yml file

This implies that you can indeed remove the lavalink service if it doesn't suit your needs but you would still need to modify the appropriate node configuration in the config.js file under the djs-bot directory

[ghost]

Ah cool, so there'll still be a config.js file with the option(s), then it's all good. Thanks mate <3

[C-EO]

@BioCla One of the reasons I liked v5 is because it had buttons. It would be pointless to create a v5.1 without buttons

The player needs the buttons for they simplified the work in addition to the pause, play, stop, and volume commands

[BioCla]

@C-EO

@BioCla One of the reasons I liked v5 is because it had buttons. It would be pointless to create a v5.1 without buttons

The player needs the buttons for they simplified the work in addition to the pause, play, stop, and volume commands

I'll take that as a suggestion. I was already planning on reimplementing them under a different dress:
Instead of having it be on the player message itself it would be in a dedicated channel (kinda like hydra).

I'll try to reimplement it as you suggested as well

[C-EO]

@BioCla I know right now I might sound like pushing too much, but the lyrics command doesn't return the lyrics for a song that is longer 4096 chars.

Ideally it should return them but say "Truncated...."

[BioCla]

@C-EO

@BioCla I know right now I might sound like pushing too much, but the lyrics command doesn't return the lyrics for a song that is longer 4096 chars.

Ideally it should return them but say "Truncated...."

Thanks for letting me know, I'll fix it as soon as possible. It used to already be as you said but it seems it got reimplemented somewhere along the restructuring of the command

[C-EO]

Thanks

[BioCla]

New version available at: https://github.com/wtfnotavailable/Discord-MusicBot