not really known
Go to file
fang cfaca77569
bark: remove /sur/hark dependency from thread
The "save summary" thread still had hark flagged as one of its dependencies,
but doesn't actually use that for anything anymore.

Here we simply remove the import.
2023-07-28 20:34:41 +02:00
.github ops: update livenet deploy workflow with correct project name and region 2023-05-24 12:55:21 -05:00
.husky initial commit of next/landscape to new master 2022-08-02 08:33:37 -05:00
desk bark: remove /sur/hark dependency from thread 2023-07-28 20:34:41 +02:00
desk-dev various: remove trailing whitespace and empty lines 2023-02-10 13:38:30 +01:00
ui Show loading spinner while loading storage settings (to make it clear that the fields are disabled) 2023-07-25 15:35:53 +03:00
.gitignore ops: ignore creds 2023-01-31 17:24:45 -06:00
README.md notifications: fix mix-blend mode for dark mode 2023-02-02 08:01:32 -05:00

Landscape

Landscape provides the primary launching interface for Tlon's suite of userspace applications. This repository contains the front-end web application to power said interface.

Landscape is built primarily using React, Typescript, and Tailwind CSS. Vite ensures that all code and assets are loaded appropriately, bundles the application for distribution and provides a functional dev environment.

Getting Started

To get started using Landscape first you need to run npm i from the ui directory.

Once that's done, you can then run npm run mock if you'd like to get started immediately. This will use hard-coded mock data to power the interface so you can work on the interface without being connected to a ship.

To develop against a working ship, you first need to add a .env.local file to the ./ui directory. This file will not be committed. Adding VITE_SHIP_URL={URL} where {URL} is the URL of the ship you would like to point to, will allow you to run npm run dev. This will proxy all requests to the ship except for those powering the interface, allowing you to see live data.

Regardless of what you run to develop, Vite will hot-reload code changes as you work so you don't have to constantly refresh.

Deploying

Deploys to internal moons are managed via github actions.