.ENV file not being respected
Hi,
I am making a new thread as one I found about my issue is old. I am in a similar place to the user here: https://discord.com/channels/1063548024825057451/1241792177919492187/1241798585868226610
However the artisan clear didn't make a difference. (My install is using Nebula theme instead of the one they listed.)
13 Replies
It occurs with any ENV value you wish to define, if the value is defined before the blueprint installation or is configured using
php artisan or editing the database directly it works as expected.
Deployed Versions
Ubuntu 24.04
Pterodactyl 1.11.7
Blueprint beta-2024-07
Nebula 1.8.3hello dan
Hello
seems like an @Emma-needed issue
hii
Oh just adding onto this I think I identified the issue, you need to force migrate php artisan where a blueprint addon may have not done something properly during it's install and surprise surprise all of the issues go away. My .ENV file becomes respected again, an issue I had where emails were being sent with my old panels domain are updated
and wings is no longer being reverted back as a backup adapter it uses s3 again
I'm glad you ended up getting it working. Blueprint should migrate the database but it's behind a input option (default option is yes).
Oh wait there is one bug in latest where it doesn't migrate the database after finishing extension installation/removal.
Only reason I noticed was in the panel logs I had a singular error relating to an addon that needed a table entry....
maybe this is what I experienced
Probably yes, one small oversight.
On another note this was one of the only oversights in latest, so I'm pretty happy about the release overall.
So far I haven't had any other issues so it seems pretty bug free for being marked as a beta
I think the other one was a bug with bash autocompletion (-install and -remove) not working outside of the Pterodactyl directory.
(It did work on zsh though)
If Blueprint stays this stable we might actually move onto a stable release.
oooh i'll keep an eye out, I don't like putting beta projects into the wiki but will probbaly link to the project once first stable build goes live.
Alrighty, sounds great!
Quick note on this, currently Blueprint is stable reliability-wise but beta feature-wise. In my opinion it would be pretty safe to put Blueprint on the wiki at this point since generally we haven't had any bug reports in the past weeks. We're thinking of adding some other features before shipping the first stable build, but generally everything should be functional enough right now.