Slate/Nebula install
I have a permissions group plugin for ptero and i went to build the panel it gives me a error cus i am on node 20. i ran
export NODE_OPTIONS=--openssl-legacy-provider and it ran succsesfully now when i go to my admin page it give me a server error the dev of the permissions plugin told me to contact support for the nebula/slate theme
any help would be appreceated
37 Replies
Please @ me if you respond because i will not get any notifications if its a reg text
Blueprint does not support standalone modifications. The permissions plugin developer has to port it to Blueprint if they'd want to make it work with other extensions.
oh ok
now im getting this
Could you try running
blueprint -upgrade remote blueprintframework/fallback and then running blueprint -i nebula;blueprint -i slate?it worked
awesome!
I managed to get standalone modifications working after installing blueprint no issues
No issues you are currently facing, that is.
after a little bit of fiddling yes
Yeah until you update Blueprint that is.
I uodate everything all at once
Panek first, blueprint then my other extensions
Panel*
Yeah but those standalone mods will break between updates.
I just pray stuff works lol
Accurate Blueprint beta release description.
Lmfao
W
Nah cuz all I had to do was just install all themes and stuff first and then the plugins
and this is exactly how you screw up 50% of all blueprint client extension apis
the only non-blueprint addon i use is jelco's reverse proxy because its just deadass needed, and it works just fine with blueprint, just have to install it after installing blueprint or shit dies
send me the link
pls
i use permissions
and it works perf
if you know how to mess with code everything is fine
Reverse Proxy for Pterodactyl
Create NGINX reverse proxies using the Pterodactyl UI
can you link it
kek
we need a reverse proxy addon for blueprint like crazy
fr
indeed
fr
everytime i update the panel its a pain in the ass to do
botiful
NPM for the backend? No... a GUI is for making doing things manually easier. If you're automating it, the panel will be your GUI. You want a backend like normal Nginx or Traefik, something without a GUI.
doesnt really change anything if it has a backend or not
like it just makes it easier for me to manage it and or use it for personal stuff
and people would be able to use the extension more easily than without a gui (for the backend)
Seems like making it more complex than it needs to be is my main point; I didn't mean to imply that it wouldn't be possible.
how is it more complex than having a no gui backend
the person just have to put a docker-compose.yml
and docker-compose up -d
It's more complex because then you have two GUIs instead of one. Your project is building a GUI in the panel for this. Why double up?
however having two guis isnt a problem if one isnt going to be used at all by the users
the point of the extension is automatising proxying
npm doesn't have this possibility without the api
At the end of the day, there's nothing inherently wrong with adding extra stuff if it feels nicer to you. It's down to personal preference, so just forget I said anything.
everyone has their opininons on things
anyhow have a great night im going to sleep
You too