Now before We explore the expert option
there is something I wanna talk about and highlight
and that is our config file with the environment variables.
We are using that file
for our development and production environment variables.
Now this file is part of our GitHub repository.
Here it is.
And it needs to be so that Versal
is able to read that file after deployment.
The problem with that could be, though,
that this file can be read
by anyone who has access to your repository.
Now, here it's a private repository,
but if you are working in a team
that could still mean that our team members can view it
and this might or might not be a problem.
I just want to make you aware of that.
You should make sure
that you only include this conflict file
in your GitHub repository
if you can rule out that unauthorized personnel
or unauthorized people are able to view that file.
If you can't rule out that that's the case,
you should not include this conflict file here,
and instead, for production,
you should set environment variables
through that environment variables feature Versal offers.
And all hosting providers offer
a built-in environment variables support.
So you wanna use that instead of using the conflict file
for environment variables,
if that file could be read
by people that should not have access
to the data in the file.
Here, for this use case it's okay.
It's my private repository, but still we wanna rule out
that we run into problems here
and hence you should be aware
of this potential security issue.