Replies: 3 comments
-
I just chime in to share my practice on this one, even if it is not golem specific, but golem compatible for sure. That way, I'll see if I am the only one doing this. I often usethis config 📦 to store configuration. I like very much the fact that I can have one file to store every configuration for different environment, and it will activate automatically depending on where my app run. When I have credential, I use one of the two soltuions
Most often I use the second way as I deloy in RStudio Connect, or using Docker and env variable can be configure in both case. And having all the configuration required for my app in one file is something I find a best practice. Interested in your thought on this way of doing - it is always a good thing to be challenged on its practice 😃 |
Beta Was this translation helpful? Give feedback.
-
Is there a suggested solution for this yet? Has anyone tried using the |
Beta Was this translation helpful? Give feedback.
-
If you want to store secret in another yaml file not followed by git in addition to Hope it helps. |
Beta Was this translation helpful? Give feedback.
-
As I continue to convert more of my apps to {golem}, I found one area that I'm not quite sure how to handle. Some of my apps deployed on an internal Shiny Server Pro had to connect to some kind of service (say API or database) and my solution was to create a
.Renviron
in the app's root directory with the credentials, and ensure that the file was not tracked by Git, yet it would be included in the app deployment. If I convert one of these apps to {golem}, is it recommended to take a similar approach? Or should I try using a customoption
instead?Beta Was this translation helpful? Give feedback.
All reactions