Mono documentation #21
Conversation
- upload and queue steps not tested - no config file given yet cc/ @treeder
arschles
changed the title
| Now run it to test it out: | ||
|
|
||
| ```sh | ||
| docker run --rm -v "$(pwd)":/worker -w /worker iron/mono:4.0.1 sh -c 'mono worker101.exe -payload hello.payload.json -id 123' |
There was a problem hiding this comment.
Change to env vars for payload.
I could have missed it, but I didn’t see support for grabbing a payload in https://github.com/iron-io/iron_dotnet/tree/master/src/IronSharp.IronWor ker. this should do for now cc/ @treeder
|
@treeder this now uses an env var to get the payload file as requested. none of the client libraries listed in the dev center (http://grcodemonkey.github.io/iron_sharp/, https://github.com/odeits/IronTools and https://github.com/iron-io/iron_dotnet) seem to provide payload lookup so unable right now to follow your request. still combing through the code to make sure but it's a line of code to get the value of an env var in C# anyway. please let me know if there are any other blockers to merging. |
|
Should update one of the dotnet libs (whichever is the best one) to read the env vars since that's our primary way of doing things now (regardless of language). |
|
@treeder it's on my todo list, but rather merge this now then update |
|
Ok, that doesn't look too bad like this anyways, couple lines, I like it. |
TODO:
add a config file, just as in the java examplescc/ @treeder