ridv/gorealis
1
0
Fork 0
Code Issues Pull requests Projects Releases 23 Packages Wiki Activity Actions

Moving from govendor to dep.

Browse source 
Vendor folder has been deleted. Use dep to regenerate vendor folder.
This commit is contained in:
Renan DelValle 2018-01-02 16:39:22 -08:00
parent 9631aa3aab
commit 03278a882b
No known key found for this signature in database
GPG key ID: C240AD6D6F443EC9
2181 changed files with 400398 additions and 346 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/getting-started.md
View file

@ -1,6 +1,6 @@
# Running custom executors on Aurora
In this document, we will be using the docker-compose executor to demonstrate
In this document we will be using the docker-compose executor to demonstrate
how Aurora can use multiple executors on a single Scheduler. For this guide,
we will be using a vagrant instance to demonstrate the setup process. Many of the same
steps also apply to an Aurora installation made via a package manager. Differences in how to configure
@ -26,14 +26,14 @@ under the custom executors section.
A sample config file for the docker-compose executor looks like this:
```
[
{
"executor":{
"command":{
[
{
"executor":{
"command":{
"value":"java -jar docker-compose-executor_0.1.0.jar",
"shell":"true",
"uris":[
{
"uris":[
{
"cache":false,
"executable":true,
"extract":false,
@ -47,10 +47,8 @@ A sample config file for the docker-compose executor looks like this:
"task_prefix":"compose-"
}
]
```
#### Configuring the Scheduler to run a custom executor
##### Setting the proper flags
Some flags need to be set on the Aurora scheduler in order for custom executors to work properly.