search

pterodactyl / panel

Pterodactyl® is a free, open-source game server management panel built with PHP, React, and Go. Designed with security in mind, Pterodactyl runs all game servers in isolated Docker containers while exposing a beautiful and intuitive UI to end users.
https://pterodactyl.io
Other
6.8k stars 1.73k forks source link

Git version control for config files of servers #4252

Open SlenkyDev opened 2 years ago

SlenkyDev commented 2 years ago

Is there an existing feature request for this?

Describe the feature you would like to see.

An option to use Git version control with Pterodactyl servers to push/pull config files ext. via a built-in Git version control GUI

Describe the solution you'd like.

A "Git" tab under Pterodactyl servers which would allow you to push/pull commits from a Git server.

Additional context to this request.

No response

parkervcp commented 2 years ago

This can be handled in an egg with variables. You would need to write your own tooling to auto-update on changes.

SlenkyDev commented 2 years ago

This can be handled in an egg with variables. You would need to write your own tooling to auto-update on changes.

Sure, but what if I want to push a change I make in the panel? Wisp already has this and it's great, so why not put it directly into Ptero too?

wordandahalf commented 2 years ago

This can be handled in an egg with variables. You would need to write your own tooling to auto-update on changes.

Sure, but what if I want to push a change I make in the panel? Wisp already has this and it's great ...

That Wisp has a feature similar to what you're requesting is immaterial. How is making commits directly from the panel particularly convenient anyhow? When I'm modifying a server's configurations, I'd much rather be using the editor and Git client I'm accustomed to. With a simple custom egg setup, I can make a commit locally, push it, restart the server, and it immediately pulls my changes. It's about as seamless as one could want.

... so why not put it directly into Ptero too?

Make a PR implementing it, and I'm sure it would be considered for addition. The obvious answer to this question is that developers, especially of open source projects, don't have the time to implement every feature requested unless there is a compelling reason to add it.

DaneEveritt commented 2 years ago

Please don't slap people with "just make a PR for it", especially not when the project already has a PR block for anything that isn't a bugfix. :)