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
Oresat chroot uses heredocs12 extensively to generate configuration files. It would be better, in my opinion at least, to move this configuration to static files. This allows us to keep the chroot script manageable in size as mission configuration becomes more detailed. As proposed, this changes the workflow.
flowchart LR
1[Copy static files to `etc`] --> 2{Further configuration?}
2 -->|Yes| 3[Shell out to `sed` for templating]
2 -->|No| Done
Loading
This has the potentially greater benefit of simplifying configuration management and deployment.
Oresat
chrootusesheredocs1 2 extensively to generate configuration files. It would be better, in my opinion at least, to move this configuration to static files. This allows us to keep the chroot script manageable in size as mission configuration becomes more detailed. As proposed, this changes the workflow.flowchart LR 1[Copy static files to `etc`] --> 2{Further configuration?} 2 -->|Yes| 3[Shell out to `sed` for templating] 2 -->|No| DoneThis has the potentially greater benefit of simplifying configuration management and deployment.
Footnotes
https://en.wikipedia.org/wiki/Here_document ↩
https://www.baeldung.com/linux/heredoc-herestring ↩