I did some searching in the forums for discussion around my particular question, but didn't come up with any hits. I'll admit my search wasn't exhaustive, so forgive me if this is a "repeat"!
Here's the deal: I have both my Flare project source files and output files stored in Git repositories in Azure DevOps. My project is bound to the Git repo that contains the source files, and I have a project destination of type "Source Control" that points to the Git repo containing the output files. My HTML5 target is set up to publish the output using the destination definition. Now, each of the Git repos is set up with credentials (to keep the bad guys out), and I used/saved those credentials while in Flare to set up both my project binding and my destination definition.
Everything works swimmingly as I publish project output from my local workstation using the setup described above, but now we'd like to add one more variable to the mix...
We're about to install an instance of Flare on a server so we can automate the publishing process there. We'll be using the command line to get latest from the source file Git repo, then publish to the output file Git repo. The question is whether or not all the Git repo credentials info is somehow stored in the Flare project file (.flprj) or somewhere else (possibly in the project's associated ".git" directory?), such that all we need to do with the Flare installation on the server is point to that project, get latest of the source files and publish—without the need to re-enter the Git repo credentials each time we initiate the process.
We're not to the point of having our server and Flare installation in place yet, so I can't simply test this out to get an answer to my question; I'm hoping I can learn from others' experience here, in advance of our attempted implementation.
Does anyone have some wisdom to impart on the topic? Could it be as easy as I hope it will be? Thanks for any help you can offer!