3 months ago
Hey,
I've been trying to create a template for a service which has some opt in features. I do not want to force the user to provide all the enviroment variables (ex. maybe they dont need to setup oauth when they first deploy); I've marked the template fields as optional but post deployment the user wont have an easy way to view which other enviroment variables they can fill.
What's the railway recommended way to approach this? I'd love to make it as seamless as possible for the user
3 Replies
3 months ago
if you have a .env.example, Railway will use that for Suggested Variables in the variables tab. Unsure if this applies to template services though, and definitely not sure if this applies to direct docker image services
Usually I just have a table of configurable variables in my template description though
3 months ago
Admittedly would be nice if Railway could keep a record of optional variables and keep it under the Variables tab, maybe something for #🤗｜feedback
3 months ago
Thanks for the input! I guess i'll add the list in the template description