Arbimon

Website for exploring biodiversity data; built with Vue 3, Typescript, Vite, pnpm, Pinia, Windi CSS.

Currently depends on Arbimon Legacy.

Contributing

Sprint DoD (The Definition of Done)

The following must be true to consider a feature "DONE":

• Code follows CONTRIBUTING.md
• Updated CHANGELOG.md
• Code deployed to staging
• Demo video sent to #biodiversity-vision

Resources

• Roadmap
• Design (Figma)
• Product & Sprint Backlogs (GitHub)
• Other files (Google Drive)

Installation

One-Time Setup

1. Install tools:

• node 18 or higher: https://nodejs.org. For anyone using nvm, simply do nvm use and you will get the current recommended version.
• pnpm 9 or higher: npm i -g pnpm@9
• VSCode & extensions: pnpm node init-vscode (requires code command in path)
  • If you have Vetur installed, disable it for this workspace
• Docker Desktop: https://www.docker.com/products/docker-desktop

1. Install/update dependencies:

pnpm i

1. Create local environment:

• Copy apps/api/.env.example to .env, and fill missing variables

1. (optional) Override default environment:

• Create apps/cli/.env.local (and override variables as necessary)
• Create apps/website/.env.local (and override variables as necessary)

1. (recommended) Add yourself to an example project. Ask another developer to invite you to Puerto Rico project on staging (needed because local Bio/Arbimon still uses staging Core for projects/permissions).

Run the App!

1. Start DB, API, and Website in dev-mode:

pnpm serve (from the monorepo root)
or
pnpm -w serve (from anywhere in the project)

If you followed step 5 above then you'll find a fully hydrated project if you navigate to http://localhost:8101/puerto-rico.

1. After you finish, you might want to stop your db:

pnpm --filter=db stop

More Commands

Resetting Workspace

If you encounter an issue, you may want to clean caches and artifacts, or reinstall dependencies.

• Delete all build and lint artifacts/caches:

pnpm -r clean

• Delete all build and lint artifacts/caches AND dependencies (node_modules):

pnpm -w clean-slate (usually followed by pnpm i to reinstall a fresh copy)

Build

• Build any package (and it's dependencies):

pnpm build

• Use the pnpm arg -r to build all packages:

pnpm -r build

Lint

• Run all linters, or only a single linter:

pnpm lint (all linters)
pnpm lint:eslint
pnpm lint:prettier
pnpm lint:stylelint

• Lint is pretty heavy; use the helper to run it sequentially across all packages:

pnpm -w lint-all

• Run linters with auto-fixes:

pnpm lint-fix (one package)
pnpm -w lint-fix-all (all packages)

Test

• Start a separate test database (required for integration tests):

pnpm -w serve-int

• Each package has some of the following test scripts:

pnpm test:component (unit tests for vue components)
pnpm test:int (heavy tests or tests that require a database)
pnpm test:unit (basic unit tests)
pnpm test-ui (tests executed in a browser)

• For TDD, you probably want to execute a single file, describe, or test:

pnpm exec vitest src/_services/picker/time-of-day-picker.component.test (fast way to execute 1 file)
pnpm exec vitest src/_services/picker/time-of-day-picker.component.test -t "has all, dirunal, nocturnal options" (filter within the file; you should use this in addition to file-path filtering)

• For TDD integration tests, you need a more complex command:

pnpm exec cross-env BIO_DB_PORT=5434 vitest --no-threads src/sync/sync-history-handler.int.test

• You can also run all tests in a package, or across the entire project:

pnpm ci-all-test-component (unit tests for vue components) pnpm ci-all-test-unit (basic unit tests)
pnpm -w test-all (calls test in all packages sequentially, like lint-all)

Cheatsheet: pnpm

• Run in monorepo root: pnpm -w _command_ (can be run from anywhere)

• Run in all packages: pnpm -r _command_

• Run in some packages: pnpm -r --filter=./apps _command_

• Run in all packages, except root: pnpm --filter=!rfcx-bio _command_ (or pnpm --filter=\!rfcx-bio _command_ in zsh)

Deployment

There are 3 shared deployments:

• testing: for the DT to test features when deployed & collaborate
  • https://testing-bio.rfcx.org
  • https://testing-bio.rfcx.org/api
• staging: for stakeholders to review & give early feedback
  • https://staging-bio.rfcx.org
  • https://staging-bio.rfcx.org/api
• production: real public project
  • https://bio.rfcx.org
  • https://bio.rfcx.org/api

Deployment: Testing

Any branch can be deployed to the testing cluster:

1. Open the "Actions" tab on GitHub
2. Select the "Build-Deploy" action
3. Click on "Run workflow", and select the branch you wish to deploy

Note: develop branch is auto-deployed to testing daily

Deployment: Staging and Deployment: Production

Environments staging and production are automatically deployed by GitHub Actions (CD):

• every push to staging branch => staging deploy
• every push to master branch => production deploy

Environment (Config and Secrets)

Local Environment

• Developers can override configuration and secrets locally using:

  • /apps/api/.env (copy .env.example to get started)
  • /apps/cli/.env.local (override any variable in .env)
  • /apps/website/.env.local (override any variable in .env)

• CLI and website also support "modes", which will load respective env:

pnpm serve -- --mode=staging (from their directories; not from the monorepo root)

Deployed Environment

• Config variables are committed to Git:
  • /tools/deployment/api/<NAMESPACE>/config.yaml
  • /apps/website/.env
• Secret variables must be manually configured:
  • API secrets can be set manually via kubectl apply tools/deployment/api/production/secrets.yaml (make a copy of tools/deployment/api/secrets.example.yaml)
  • Website secrets can be set manually as GitHub secrets
  • Secrets should never be committed to Git

Feature toggle

• Developers can add a feature toggle environments to control component displayment by following this step:

1. Add vite environment inside .env
2. Add the toggle key inside website/src/_services/feature-toggles
3. Use inject() to get feature toggles for using inside the component

Note: The feature toggle value can be override following the override env file level from Modes

Configure the project for local development with rfcx-api

In some cases you wanted to test out the functionality with the core api.

Tools required from core

• psql

make sure psql is installed in your machine. You can install just libpq to make this work.

brew install libpq

make sure you have linked it to your shell by putting this inside your shell configuration file

bash export PATH="/opt/homebrew/opt/libpq/bin:$PATH"

For windows users it's easier to just install the whole database. See https://www.postgresql.org/download/windows/

• yarn You can install yarn with homebrew

brew install yarn

Or with npm

npm i -g yarn

• python3 and setuptools You can install python3 from pyenv or use a local install of python3 inside of your OS pip install setuptools

Core preparation

• Startup core by cloning rfcx-api to your machine

git clone git@github.com:rfcx/rfcx-api ./rfcx-api cd rfcx-api

• Setup environment variables for core

cp ./common/config/env-vars.js.sample ./common/config/env-vars.js

• Make sure you have AUTH0_CLIENT_ID and AUTH0_CLIENT_SECRET environment variable from the core team. So your api can be accessed and validated.

• Get one of the backend team to add you onto the seed script, or you can add yourself by.

  • In the file ./core/_cli/seeds/02-users.sql. Add yourself into the database with the email that you will be using during the development. You can use any id and guid but make sure the email matches.
  • In the file ./core/_cli/seeds/07-user-organization-roles.sql. Add yourself into the organization with an id of aaaaaaaaaaa6 and role_id of 1.
  • In the file ./core/_cli/seeds/08-user-project-roles.sql. Add yourself into Puerto rico project (id zy5jbxx4cs9f) with role_id of 1.

• Install dependencies, start core's database and perform reset-migrate-seed by running

yarn serve-db:core

• Start core server with yarn dev:core

Arbimon preparation

• Change CORE_API_BASE_URL to http://localhost:8080 inside ./apps/api/.env
• Change VITE_CORE_API_BASE_URL to http://loaclhost:8080 inside ./apps/website/.env

Now you can run your project normally on arbimon and you will be able to see 5 projects with 5 different statuses in the cnn analysis page.