I noticed that only the system env variables are a...

# kobweb

[Funyinoluwa Kashimawo]

I noticed that only the system env variables are available in the jvm module.

How can I inject user env variables into the app?

[David Herman]

The Kobweb block has a "globals" map which you can set from Gradle. So as long as you can get those env variables from your Gradle script, you can do something like

kobweb {
  app {
     globals.put("version", "123")
  }
}

You can then reference those values from your code using the AppGlobals global. For the above case, you could get the version by writing AppGlobals.getValue("version").toInt()

Does that work for you?

[Funyinoluwa Kashimawo]

Thanks

[Funyinoluwa Kashimawo]

So that would mean I would have to use a secret gradle file?

[David Herman]

A secret Gradle file?

[David Herman]

Gradle can read local env values

[David Herman]

You should just be able to add this code to the build.gradle of your site project

[Funyinoluwa Kashimawo]

Yeah because the gradle file also can't access the user env value only system env value

[Funyinoluwa Kashimawo]

So the solution I am looking for is basically an env file that can either be inserted through the run command or pulled from system env when the app is deployed.

[David Herman]

You can insert values into your gradle.properties file if that works for you

[David Herman]

Does System.genenv not work?

[David Herman]

Does this post help? https://ubuntudroid.medium.com/handling-environment-variables-in-gradle-fb1b8bb6c758

[Funyinoluwa Kashimawo]

System.getenv works but does not provide the values attached to the run command.

Check the image sent earlier.

[Funyinoluwa Kashimawo]

Yeah I think the gadle.properties option might work

[David Herman]

Do any of these help? https://stackoverflow.com/questions/27172863/how-to-set-environment-vars-in-intellij-for-gradle-tasks

[Funyinoluwa Kashimawo]

Do the .properties did not really work and the app globals to didn't work because I needed the value in the jvm but the AppGlobals is only available in the js

[Funyinoluwa Kashimawo]

I'll share how I resolved it shortly

[Funyinoluwa Kashimawo]

I defined the variable in the local.properties file an made it available to the app using this gradle plugin https://github.com/gmazzo/gradle-buildconfig-plugin

[Funyinoluwa Kashimawo]

In local.properties MONGO_URI=
In project level build.gradle

val properties = Properties()
val propertiesFile = project.rootProject.file("local.properties")
if (propertiesFile.exists()) {
    properties.load(propertiesFile.inputStream())
}

val mongoUri = properties.getProperty("MONGO_URI")

buildConfig {
    buildConfigField("String", "MONGO_URI", "\"${mongoUri}\"")
}

In code

private val client = MongoClient.create(BuildConfig.MONGO_URI)

[David Herman]

Great, thanks for sharing!

[David Herman]

I'm glad another plugin could provide the necessary behavior

[David Herman]

Note that I've used findProperty in some of my own build scripts

[David Herman]

For example, I use it for signing: https://github.com/varabyte/kotter/blob/52b8a07cb28a8a17d32f09546d19b8c566e6a27b/kotter/build.gradle.kts#L80

I declare that value in a gradle.properties file for that project

[Funyinoluwa Kashimawo]

wow do you mean the findProperty can also return values from the local.properties file?

[David Herman]

I'm not sure. Worth a shot!

[Funyinoluwa Kashimawo]

Update

I did this instead of picking the values separately

val properties = Properties()
val propertiesFile = project.rootProject.file("local.properties")
if (propertiesFile.exists()) {
    properties.load(propertiesFile.inputStream())
}
buildConfig {
    properties.forEach {
        if ("${it.key}" != "sdk.dir") {
            buildConfigField("String", it.key.toString(), "\"${it.value}\"")
        }
    }
}

[David Herman]

https://github.com/gradle/gradle/issues/12283 reading this now, but it seems like they might not intentionally support local properties?

[David Herman]

Yeah official guidance is using gradle.properties instead

[Funyinoluwa Kashimawo]

Oh If it works for gradle.properties that's fine. I don't mind making that into a secret