There are a few things that will make managing your pico engine and writing KRL code easier.
...
Update to the Latest Version
You can update to the latest version using the command
| Code Block |
|---|
npm update -g pico-engine |
Check Your Version
You can see which version you are using near the top-left corner of the "My Picos" page (localhost:8080) or by running the command
| Code Block |
|---|
npm ls -g pico-engine |
...
Remove the pico engine code.
| Code Block |
|---|
npm rm -g pico-engine |
Update to the Latest Version
You can update to the latest version using the command
| Code Block |
|---|
npm update -g pico-engine |
Check Your Version
You can see which version you are using near the top-left corner of the "My Picos" page (localhost:8080) or by running the command
| Code Block |
|---|
npm ls -g pico-engine |
Initialize
If you wish to remove all picos and start over, use one or more of these commands.
...
- 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.
...