You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a repository is built, it is assumed to be agnostic of where and how it will be run. For instance, if I want to use the same website repository for two different domains, or a domain and a sub-folder, I would need to merge a submodule into the repository and add something like a GitHub Action that automatically updates the submodule. This issue can be easily solved by adding context to CI/CD runs.
The idea is to simply export an environment variable and a filesystem (folder) with the configuration, or at least a subset of it.
Exporting the configuration repository may pose a question: Should we clone the current branch, or should we clone the current commit on the branch? Upon reflection, using the current commit should be the preferred method, as it will cause the build to fail and retry if the node is not up-to-date yet. Another method could be to decompile and generate the configuration from TNS.
The text was updated successfully, but these errors were encountered:
Currently, when a repository is built, it is assumed to be agnostic of where and how it will be run. For instance, if I want to use the same website repository for two different domains, or a domain and a sub-folder, I would need to merge a submodule into the repository and add something like a GitHub Action that automatically updates the submodule. This issue can be easily solved by adding context to CI/CD runs.
The idea is to simply export an environment variable and a filesystem (folder) with the configuration, or at least a subset of it.
Exporting the configuration repository may pose a question: Should we clone the current branch, or should we clone the current commit on the branch? Upon reflection, using the current commit should be the preferred method, as it will cause the build to fail and retry if the node is not up-to-date yet. Another method could be to decompile and generate the configuration from TNS.
The text was updated successfully, but these errors were encountered: