Page Comparison

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:

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):

Image Modified

or by running the command:

npm ls -g pico-engine

...

If you need to set the URL for your engine, you can add the PICO_ENGINE_BASE_URL env variable. For example:

docker run -p 80443:3000 -v ~/images/pico-image:/var/pico-image -d pjw/pico-engine -e PICO_ENGINE_BASE_URL=https://picos.picolabs.io

...

1. 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)
2. 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:

npm install -g krl-compiler
krl-compiler -v                # v1.0.1

...