ogma-core: Add dockerfile to cFS template. Refs #353.#354
Merged
ivanperez-keera merged 12 commits intonasa:developfrom Feb 11, 2026
Merged
ogma-core: Add dockerfile to cFS template. Refs #353.#354ivanperez-keera merged 12 commits intonasa:developfrom
ogma-core: Add dockerfile to cFS template. Refs #353.#354ivanperez-keera merged 12 commits intonasa:developfrom
Conversation
4e9e365 to
3f88fa2
Compare
Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. To make room for the Dockerfile, we need the cFS application files to be generated in a subdirectory, so that the Dockerfile is not mixed with the contents of the generated monitoring application. This commit moves the files in the existing template to a subdirectory that holds only the monitoring application.
…#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit moved all files in the existing template to a subdirectory, so that the Dockerfile to be added is not mixed with the existing template. This commit adjusts the cFS backend so that it looks for the template in the directory `cfs`, which is where files are now located after the renaming.
…#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit moved all files in the existing template to a subdirectory, so that the Dockerfile to be added is not mixed with the existing template. This commit modifies the Cabal file so that the files in the cFS template are installed from their new locations.
3f88fa2 to
91bd8a0
Compare
Member
Author
|
Change Manager: Several of the changes fell in the |
Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit moved all files in the existing template to a subdirectory, so that the Dockerfile to be added is not mixed with the existing template. This commit adjusts the CI job that tests the cFS backend to account for the change in path for the generated files relative to the top-level target dir.
…. Refs nasa#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit moved all files in the existing template to a subdirectory, so that the Dockerfile to be added is not mixed with the existing template. This commit updates the cFS tutorial account for the new expected path for the generated monitoring application.
…Refs nasa#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit moved all files in the existing template to a subdirectory, so that the Dockerfile to be added is not mixed with the existing template. This commit updates the README to list the files produced by the cFS backend using their new location.
91bd8a0 to
76c9d37
Compare
Member
Author
|
Implementor: Fix implemented, review requested. |
Member
Author
|
Change Manager: The |
Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. This commit adds a Dockerfile to the cFS template.
…. Refs nasa#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit added a Dockerfile at the top level in the cFS template. This commit modifies the Cabal file to add the new cFS Dockerfile to the list of data files installed with the cFS template when `ogma-core` is installed.
…. Refs nasa#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit added a Dockerfile to the top-level of the cFS template. This commit updates the cFS tutorial to include the Dockerfile in the list of files generated by the cFS backend.
…Refs nasa#353. Ogma doesn't currently generate a Dockerfile with the cFS applications. That makes it harder for users to know how to use the generated applications. A prior commit added a Dockerfile to the top-level of the cFS template. This commit updates the README to include the Dockerfile in the list of files generated by the cFS backend by default, and to explain how the file can be used to compile the generated cFS application in a standard distribution of cFS.
76c9d37 to
c7ecd94
Compare
Member
Author
|
Implementor: Fix implemented, review requested. |
Member
Author
|
Change Manager: Verified that:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add Dockerfile to cFS template, adjusting the locations of files in the template, the Cabal files, the backend and the documentation, as prescribed in the solution proposed for #353.