Adding functionality to serve an agent's store directory #328
Conversation
This file contains 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
notthetup
force-pushed
the
agent-serve-store
branch
2 times, most recently
from
c91f248
to
d333cff
Compare
notthetup
force-pushed
the
agent-serve-store
branch
2 times, most recently
from
653a526
to
17dc2ff
Compare
notthetup
force-pushed
the
agent-serve-store
branch
from
17dc2ff
to
11a70c5
Compare
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.
Adds a new API
Agent.enableServeStoreandAgent.disableServeStorewhich allow the agent to request a WebServer connected to thecontainer(if any) to serve its default store directory (for e.g.$UNET_HOME/store/org/arl/fjage/shell/ShellAgent) over HTTP.Pending #329 for review.