For Livepeer AI Orchestrators joining the BlueClaw Network
Version: 1.3 — March 29, 2026
BlueClaw: https://blueclaw.network
Base URL: https://openai.blueclaw.network/v1
For Livepeer AI Orchestrators joining the BlueClaw Network
Version: 1.3 — March 29, 2026
BlueClaw: https://blueclaw.network
Base URL: https://openai.blueclaw.network/v1
| @supports (-webkit-backdrop-filter: none) or (backdrop-filter: none) { | |
| .blurred-container { | |
| -webkit-backdrop-filter: blur(10px); | |
| backdrop-filter: blur(10px); | |
| } | |
| } | |
| /* slightly transparent fallback for Firefox (not supporting backdrop-filter) */ | |
| @supports not ((-webkit-backdrop-filter: none) or (backdrop-filter: none)) { | |
| .blurred-container { |
| - uses: actions/cache@v2 | |
| with: | |
| path: ${{ env.pythonLocation }} | |
| key: ${{ env.pythonLocation }}-${{ hashFiles('setup.py') }}-${{ hashFiles('dev-requirements.txt') }} |
| steps: | |
| - uses: actions/checkout@v2 | |
| - name: Setup Python | |
| uses: actions/setup-python@v1 | |
| with: | |
| python-version: 3.7 | |
| - uses: actions/cache@v2 | |
| with: |
| { | |
| "__inputs": [ | |
| { | |
| "name": "DS_GOLIATH_INFLUXDB", | |
| "label": "goliath influxdb", | |
| "description": "", | |
| "type": "datasource", | |
| "pluginId": "influxdb", | |
| "pluginName": "InfluxDB" | |
| } |
| # Create `gh-pages` branch from scratch | |
| cd <dir> | |
| git init | |
| git remote add origin <url> | |
| git checkout --orphan gh-pages | |
| git add . | |
| git commit -m "build 1.0.0" | |
| git push origin gh-pages |
Generally, the Git proxy configuration depends on the Git Server Protocol you use. And there're two common protocols: SSH and HTTP/HTTPS. Both require a proxy setup already. In the following, I assume a SOCKS5 proxy set up on localhost:1080. But it can also be a HTTP proxy. I'll talk about how to set up a SOCKS5 proxy later.
When you do git clone ssh://[user@]server/project.git or git clone [user@]server:project.git, you're using the SSH protocol. You need to configurate your SSH client to use a proxy. Add the following to your SSH config file, say ~/.ssh/config:
ProxyCommand nc -x localhost:1080 %h %p
| ### This script wraps all executables in the anaconda bin folder so that they can be used without adding Anaconda | |
| ### to the path which would break some functionality of ROS (Robot Operating System) | |
| ### | |
| ### The commands e.g. jupyter notebook will cause the script to add anaconda to the path, start jupyter notebook | |
| ### and after jupyter notebook terminated remove anaconda from the path again | |
| ### | |
| ### Notable commands: | |
| ### * release-the-snake Adds conda to the path and removes all aliases defined by this script | |
| ### Conda will stay in the PATH until the end of the session (terminal is closed) or | |
| ### until "cage-the-snake" is called |
| # Build a Python extension module using pybind11 | |
| # pybindings_add_module(<module>) | |
| # Here <module> should be the fully qualified name for the module, | |
| # e.g. pybindings_add_module(foo.bar._baz) | |
| # <module> becomes the target name in case you wish to do something to it later | |
| # The source for the binding *must* be placed in src/pybindings/{relpath}/py{name}.cc | |
| # E.g. for module=foo.bar._baz -> src/pybindings/bar/py_baz.cc | |
| function(pybindings_add_module module) | |
| set(target_name ${module}) | |
| string(REPLACE "." "/" modpath ${module}) |