github/pyrodactyl
1
1
Fork 0
mirror of https://github.com/pyrohost/pyrodactyl.git synced 2026-04-05 19:51:59 +02:00
Code Issues 44 Packages Projects Releases Wiki Activity

Downloading/Uploading SQL files from Client Panel #9

New Issue
Open
opened 2026-04-05 19:45:16 +02:00 by MrUnknownDE · 0 comments
MrUnknownDE commented 2026-04-05 19:45:16 +02:00
Owner
Copy Link

Originally created by @Lupancham on 10/29/2025

Is there an existing feature request for this?

  • I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

I believe it would be a nice feature to allow clients to download and upload SQL files to databases, which lets them easily transfer databases from old hosts or make local copies for editing.

Yes, I might be aware that users should be expected to use SQL clients to do this process, but I believe this may be a good QoL feature for those who may not be well-versed in using a SQL client or know much about it.

Describe the solution you'd like.

I would like to see this feature implemented within the Server's Databases tab of the Client Panel to allow easy access to SQL files.

Clients will be able to download SQL files by hitting a Download Database button, which can be accessed by clicking the Details button. SQL files can be uploaded and written to databases by clicking the Details button while in the database tab of their server, from which they can click Upload Database File that lets them select a SQL file and type the database name into a text box to confirm that they wish to upload the database. (Uploading Databases should optionally request to download the old database file)

Additional context to this request.

No response

*Originally created by @Lupancham on 10/29/2025* ### Is there an existing feature request for this? - [x] I have searched the existing issues before opening this feature request. ### Describe the feature you would like to see. I believe it would be a nice feature to allow clients to download and upload SQL files to databases, which lets them easily transfer databases from old hosts or make local copies for editing. Yes, I might be aware that users should be expected to use SQL clients to do this process, but I believe this may be a good QoL feature for those who may not be well-versed in using a SQL client or know much about it. ### Describe the solution you'd like. I would like to see this feature implemented within the Server's Databases tab of the Client Panel to allow easy access to SQL files. Clients will be able to download SQL files by hitting a ``Download Database`` button, which can be accessed by clicking the ``Details`` button. SQL files can be uploaded and written to databases by clicking the ``Details`` button while in the database tab of their server, from which they can click ``Upload Database File`` that lets them select a SQL file and type the database name into a text box to confirm that they wish to upload the database. (Uploading Databases should optionally request to download the old database file) ### Additional context to this request. _No response_
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Feature Request
bug
bug
bug
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
dependencies
enhancement
enhancement
enhancement
enhancement
good first issue
good first issue
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
javascript
php
php
php
php
php
php
php
php
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrUnknownDE
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pyrodactyl#9
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?