https://github.com/RDIL/geminabox-railway/blob/debug/config.ru#L11

the ui is straight up lying

You tried to set ${{secret()}} on a service, it can only be set within templates.

I feel like there should be a glaring warning that tells you that then

or it should just refuse to work

instead of behaving like this

Iirc secret() just resolves to a random value. Had this issue recently too

this feels like a massive footgun and i'm surprised it's not documented anywhere

That value is mismatched as it gens a new one when you view it. Ssh in to container and echo the var to see it

Or, see the one your process is using…

Inconvenient yeah

This is good feedback. I’ve run into this and found it confusing myself. “Is this value uhh stable between restarts?”

I can create a product ticket for this

Yay!

Was also annoyed by this <:sadcat:1408269791965478932>

I think the best behavior would be it generating when you press submit and actually storing that static value

I think though what brody was saying is this value is meant for templates so the starting value isn’t consistent.

Its meant to be changed not used as keygen iirc

at least when you're not in a template

if the feature is only meant for templates it should not work outside templates

I'd consider that a bug

^

Hi, this should be fixed now!

oh that was nice and quick, thanks!

@Paulo what fix was applied? I just tried it and it seems to be the same 🤔

${{secret()}} should generate the value on save, what are you trying to do, could you record a video please?

sure one moment

whoa okay it just worked

must have been a tab from before the change was deployed