Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidebar shouldn't list instructions for both daemon and wings #211

Closed
iamkubi opened this issue Apr 30, 2020 · 5 comments
Closed

Sidebar shouldn't list instructions for both daemon and wings #211

iamkubi opened this issue Apr 30, 2020 · 5 comments

Comments

@iamkubi
Copy link
Contributor

iamkubi commented Apr 30, 2020

image

If you follow the instructions from top to bottom you will install both 0.6 and 0.7 daemon. I think these two sections should be combined in a single dropdown rather than separate items.

People are doing this, e.g.:

KanameToday at 1:43 PM
Daemon work but wings dont want start
i've Daemon 0.6
and wings 1.0
@parkervcp
Copy link
Member

Wings is a beta. It's specifically tagged as such. I don't see this as an issue.

@parkervcp
Copy link
Member

You install the the current version of the panel (0.7) and the current daemon (0.6).

Wings will eventually replace the old nodejs daemon.

@iamkubi
Copy link
Contributor Author

iamkubi commented Apr 30, 2020

Your arguments are not consistent. Why hide the Panel 1.0 docs behind a dropdown but not the Wings 1.0?

@matthewpi
Copy link
Member

matthewpi commented May 1, 2020

Because the Panel is a direct upgrade/replacement while Wings is a completely new system.

But I do agree that Wings should be placed as a dropdown under the Daemon as it is basically a newer daemon written in another language, not to mention that the old daemon is referenced as wings in multiple places. This would prevent people getting confused when they are installing Pterodactyl as it is not clear that you cannot run wings with the current stable panel and when following the docs from the beginning it does not specify that you need to install the daemon to create and run servers, leading people to potentially install none of them, one of them, or both of them.

@DaneEveritt
Copy link
Member

I think we could solve this by just making it very clear on the wings install page that it is beta software, and likely not what the user is looking for.

I'm happy with the current documentation structure, but it might just need some language adjustments. I'm pretty tired of constantly changing things and making it more confusing for me to reason about and maintain just because people are too dense to slow down and read the directions.

However, if we're showing everything like this and there is not a clear warning on the wings page then it should be added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants