!NhAsaYbbgmzHtXTPQJ:funklause.de

Nix NodeJS

207 Members
59 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
21 Dec 2023
@lily:lily.flowersLily Fosteryeah, one sec. getting personal laptop out16:01:44
@lily:lily.flowersLily Foster
In reply to @peter-lustig:matrix.org
could you show me how I would do that in my current flake
the values don't matter during build right? so they could be empty strings for all your package cares?
16:03:49
@peter-lustig:matrix.orgpeter-lustigyeah i think so16:04:21
@peter-lustig:matrix.orgpeter-lustigworth a try16:04:28
@lily:lily.flowersLily Foster(dynamically grabbing them from the env when they are needed rather than importing from a virtual module would probably be more robust, and would also handle things like the env vars changing during the lifetime of the program better)16:04:51
@lily:lily.flowersLily Foster

you can do something like this though:

env = {
    GITHUB_CLIENT_ID = "";
    GITHUB_CLIENT_SECRET = "";
    ...
}
16:05:19
@lily:lily.flowersLily Fosteron the derivation16:05:23
@peter-lustig:matrix.orgpeter-lustig
In reply to @lily:lily.flowers
(dynamically grabbing them from the env when they are needed rather than importing from a virtual module would probably be more robust, and would also handle things like the env vars changing during the lifetime of the program better)

yeah i had it dynamic before and everything worked, but look at this:

https://kit.svelte.dev/docs/migrating-to-sveltekit-2#dynamic-environment-variables-cannot-be-used-during-prerendering

16:05:33

Show newer messages


Back to Room ListRoom Version: 6