Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
flamenco-worker-python
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
blender
flamenco-worker-python
Commits
ed3f3d9d
Commit
ed3f3d9d
authored
8 years ago
by
Sybren A. Stüvel
Browse files
Options
Downloads
Patches
Plain Diff
Clarified readme a bit
parent
0a3b2a34
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+10
-5
10 additions, 5 deletions
README.md
with
10 additions
and
5 deletions
README.md
+
10
−
5
View file @
ed3f3d9d
...
@@ -26,25 +26,30 @@ When those files do not exist, they are skipped (i.e. this is not an error). The
...
@@ -26,25 +26,30 @@ When those files do not exist, they are skipped (i.e. this is not an error). The
should be in INI format, as specified by the
should be in INI format, as specified by the
[
configparser documentation
](
https://docs.python.org/3/library/configparser.html
)
[
configparser documentation
](
https://docs.python.org/3/library/configparser.html
)
### Configuration contents:
### Configuration contents:
All configuration keys should be placed in the
`[flamenco-worker]`
section of the
All configuration keys should be placed in the
`[flamenco-worker]`
section of the
config files.
config files.
-
`manager_url`
: Flamenco Manager URL.
-
`manager_url`
: Flamenco Manager URL.
-
`worker_id`
: ID of the worker, handed out by the Manager upon registration (see
Registration below) and used for authentication with the Manager.
-
`worker_secret`
: Secret key of the worker, given to the Manager upon registration
and authentication.
-
`job_types`
: Space-separated list of job types this worker may execute.
-
`job_types`
: Space-separated list of job types this worker may execute.
-
`task_update_queue_db`
: filename of the SQLite3 database holding the queue of task
-
`task_update_queue_db`
: filename of the SQLite3 database holding the queue of task
updates to be sent to the Master.
updates to be sent to the Master.
These configuration keys are also required, but are created automatically upon startup
when they don't exist yet:
-
`worker_id`
: ID of the worker, handed out by the Manager upon registration (see
Registration below) and used for authentication with the Manager.
-
`worker_secret`
: Secret key of the worker, generated by the Worker and given to the
Manager upon registration and authentication.
### TODO
### TODO
-
Certain settings are currently only settable by editing constants in the Python source code.
-
Certain settings are currently only settable by editing constants in the Python source code.
It might be nice to read them from the config file too, at some point.
It might be nice to read them from the config file too, at some point.
-
Update worker address in MongoDB when communicating with it.
## Invocation
## Invocation
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment