Does Blueprint work with Pterodactyl in development mode?
We're running Pterodactyl in a docker container and based our setup off of https://github.com/pterodactyl/development/. But we're having one heck of a time getting Blueprint running with it... I've gotten as far as actually getting it installed BUT I'm receiving the "You need to finish installing Blueprint to start using extensions." message. Is it even possible to use Blueprint when running Pterodactyl in development mode?
8 Replies
Oh I left out that this is virtually a brand-new setup so we're already running the latest version of both Pterodactyl and Blueprint
Looks like the development repo's compose file uses a different image; I'll look into it.
Looks like they don't have any kind of versioning with the dev image; it will always be :latest. That simplifies things at least.
The dev image isn't based on alpine; this won't be a matter of just swapping the image out.
That’s fair. Thanks for looking into it! Any insight would be hugely appreciated 🙏
I can skip most of the alpine-specific logic, as nodejs and yarn are already installed in the image, and for the sake of the Blueprint install, I'll just assume they're a new enough version. Looks like several keys in that image are expired though, so that's what I'm on now.
@tfh The node image in that development image is v14.20.1
I don't think the repo you linked is actively maintained anymore.
At this point I'm scrapping the project, but I did install the tools necessary for development into the blueprint image at https://github.com/BlueprintFramework/docker; it was necessary, since Blueprint modifies the panel repeatedly. If you need something else in there, let me know.
Dang, yeah. It's rough. I did manage to get it working and could share the relevant docker-compose.yml, Dockerfile and entrypoint script if you were curious. But otherwise, would it make sense to instead swap out our current pterodactyl container for this one of yours? And am I right that it would be a direct replacement of the pterodactyl docker container — in other words, I don't need both, right?
Yes, it would be a direct replacement. If you're starting from an existing compose file you're already modified, see https://discord.com/channels/1063548024825057451/1094949482535321690/1244743256575578164.
This is great, thank you very much!
No problem