soma
soma copied to clipboard
PLUS-POSTECH
Cross-platform CTF problem container manager
Bollard updated to `0.3.0` which includes breaking changes. Also, crossterm updated to `0.9.3`.
Azure Pipelines will introduce a new image: "[VS2019-Server2019](https://github.com/Microsoft/azure-pipelines-image-generation/blob/master/images/win/Vs2019-Server2019-Readme.md)" Using this image can reduce CI time significantly as it is not required to install VC Build Tools.
```toml name = "a" [binary] os = "ubuntu:16.04" cmd = "./a" ``` This should be a valid `soma.toml` but currently rejected by the program with the following error. `missing field...
If [`publish_all_ports`](https://docs.rs/bollard/0.1.1/bollard/container/struct.HostConfig.html#structfield.publish_all_ports) option is used, a container will allocate unused ports automatically when it starts. To handle this scenario, 1. `port` becomes optional in run command and `ops::run`. 2. `HostConfig`...
Updates after initial release may contain breaking changes in (de)serialization of repository index. So, we should prepare an automatic updating mechanism of it.
We should remove all associated built images and running problem services before removing a repository. However, we can enhance user convenience by invoking auto prune on repository removal.
Soma supports local file sources only. However, there are some situations users may want to use external file source. - File is too big Git repositories may have a repository...
Implementing view of current image and container status (built, running, version, etc.) may help user to inspect Soma resources.
https://github.com/PLUS-POSTECH/soma/blob/8593333d86f401544798eb515070147aa7bb7587/src/problem/configs/binary.rs#L41 Solidify 할 때 toml에 적어 놓은 순서 보존 안 되고 무조건 executable이 먼저 처리되는데 상관 없나요? _Originally posted by @Qwaz in https://github.com/PLUS-POSTECH/soma/pull/103/files_