There are a few things that will make managing your pico engine and writing KRL code easier.
...
Update to the Latest Version
You also use the npm install command to get the latest version, or the variant shown above if you want a specific version rather than the latest, using the command:
| Code Block |
|---|
npm install -g pico-engine |
Check Your Version
You can see which version you are using near the bottom-right corner of the developer UI page (localhost:3000):
or by running the command:
| Code Block |
|---|
npm ls -g pico-engine |
...
would use https://picos.picolabs.io and as the engine URL.
You can run the same container multiple times with different ports and mount points to have multiple engines running at the same time.
...
- GitHub works well, with one caveat. See these instructions for more information about how to use GitHub to host KRL. The caveat is that GitHub caches the resources on raw URLs for about 5 minutes. If you're making frequent changes, it can be frustrating to wait out the cache. Alternatively, GitLab should give you fewer caching problems. (raw URLs to rulesets in private repositories need an account access token)
- AWS S3 works well. Be sure to make the URL for the ruleset is readable by the engine.
...
To validate using the second method, Install the KRL Compiler using this command:
| Code Block | ||
|---|---|---|
| ||
npm install -g krl-compiler krl-compiler -v # v1.0.1 |
...