38 docs tagged with "LOC"

The administration panel has a series functions for management roles.

In future releases the administration panel will only be accessed by authorised LOC Owners.

Data Context is an object injected into logic functions at runtime, which containes some key components:

See Introduction and Setup first if you haven't gone through the steps above.

See Quick Start for how to deploy the necessary logic and data process for this tutorial.

Execution

Data Process

Connecting external databases with built-in drivers. Currently the following databases are supported:

LOC events allows users to generate metadata represent a data flow or data trail to indicate who have sent, used or received data. These information can be very useful for two reasons:

Emit and query LOC data events.

This is the follow-up of Emit and Inspect Events, in which we've learned the basics of emitting events.

Accessing and writing files. Supports the following storages:

CLI commands for

For sending HTTP requests to specific hosts.

LOC v0.8 Release Note (legacy version)

LOC SDK is a downloadable NPM package that defines the interfaces of data context as well as agents - a series of features provided by LOC's logic runtime that can read and/or write internal and external storages.

LOC Studio is the web-based graphical user interface for LOC Core. Thanks to its highly-interactive Reack framework and UI/UX-driven design, Studio is intuitive to use and doesn't need a lot of walkthrough to learn. You've probably already used most of it in Quick Start and Tutorials.

Developing with CLI

Project, Scenario and Data Process Hierarchy

For sharing data between tasks of one data process, which can stay persistent for a period of time.

Log (debugging) messages to LOC.

Logic are the core elements of a data process. They contains the implementation of a data pipeline (which may be part of a bigger one). And the session storage is the thing to link them up together during a task.

Read a local environment variable (not to be confused with local storage data or secrets in agent configurations). These variable can be set via Studio or CLI, which are useful for configuring a data process' behavior without modifying the logic code.

Sending emails with a SMTP server.

Payload is the data sent by triggers as initial input and is accessible from the context object. Currently there are two payload types:

Parse trigger payload to JSON and write to the session storage.

CLI commands for managing assets in LOC:

Create a "Hello World" Data Process

LOC v0.8 , as part of the ongoing effort focusing on better Studio/CLI synchronisation and logic modularisation, thus has brought some new major changes.

Finalise a JSON object as the result data. If the trigger is synchronized API route or message queue, it will be returned to the trigger, otherwise stored in LOC to be retrieved later.

Parse trigger payload to JSON and write to the session storage.

What is Agent Configuration?

For sharing data between logic during a task (execution) of a data process.

Synchronising Local and Remote Project

Some tips about handling errors in logic.

For managing API routes, one of the most common trigger for invoking data processes.

This feature is only accessed by authorised LOC Owners.

CLI commands for managing assets in LOC: