🚒Engines
Sepana Engines are effectively tables in a database, though these Engines can have nested data. This means they can be non-relational in nature.
Last updated
Sepana Engines are effectively tables in a database, though these Engines can have nested data. This means they can be non-relational in nature.
Last updated
After a user successfully signs up and logs in, they can start building Engines from the home screen. Simply click "New Engine" or "Create New Engine."
This will prompt the user to enter an Engine name. Simply choose a name and click "Create."
When the Engine is successfully created, you will see a new view called "Engine view."
At the top we have our main header bar in which you can view & edit your engines.The "Engine Dropdown" lets you select an engine to navigate to. The "New Engine" button allows you to create a new engine. The "Manage APIs" button allows you to view the API keys associated with your account.
Just below the Engine name is the Engine ID, which is a unique ID for every Engine within Sepana. This is how we identify Engines in our system. Engine IDs are extensively used for different Sepana APIs, which we will discuss in more depth in the Search API section of our Docs.
There are various sections on this page which we will briefly review:
Click on the three dots on the right side to rename or delete the Engine
Click on "Add Records" to add data into the Engine. You can upload CSV, JSON and TSV files. A maximum of 500 records can be inserted at a time. If the file has more than 500 records, the data will be divided into chunks of 500 and be inserted into the Engine.
The "New Engine" button allows you to create a new engine. The "Manage APIs" allows you to view the API keys associated with your account. The "+" button lets you insert the data into the Engine just like the "Add Records" button discussed in the previous section. The other two boxes represent the stats associated with the Engine. "Total Searches" gives you the total number of searches made in the Engine. "Size" gives you the information about the storage size consumed by the data in the Engine.
