Doughnut

About

Doughnut is a Personal Knowledge Management (PKM) tool combining zettelkasten style of knowledge capture with some features to enhance learning (spaced-repetition, smart reminders) and ability to share knowledge bits with other people (for buddy/team learning).

For more background info you can read:

Product Backlog

Story Map

How to Contribute

We welcome product ideas and code contribution.
Collaborate over:
- GitHub Discussions for product ideas/features,
- GitHub Issues for reporting issues or bugs, OR
- doughnut gitter.im
FOSS style; Fork and submit GitHub PR.
- Please keep the PR small and on only one topic
- The code need to come with tests

Doughnut Technology Stack

Getting started

1. Quick Start - doughnut development environment setup

From the root of doughnut directory:

./setup-doughnut-dev.sh

If you hit problems with the above quick-start setup, you should manually walk through the local development environment nix setup.

2. Setup and run doughnut with migrations in 'E2E' profile (backend app started on port 9081)

yarn sut

Rerun it each time you reset the database.

Run full backend unit tests suite

From doughnut source root directory:

yarn backend:test

3. End-to-End Test / Features / Cucumber / SbE / ATDD

We use cucumber Gherkin + cypress (test driver) Javascript/Typescript framework to drive the end-to-end test suite.

Cucumber

The Cypress+Cucumber tests are in JavaScript/TypeScript.

cypress + cypress-cucumber-preprocessor

Commands

For MS Windows WSL2 users:

you need to ensure your WSL2 Linux has xvfb installed manually before you can run cypress. This is not managed by Nix!
export NODE_OPTIONS="--max-old-space-size=4096" before running any cypress related commands (e.g. cy:open or cy:run).

Purpose	Command (run from `doughnut` source root directory)
Install needed e2e tooling	`yarn`
Start SUT (backend system under test)	`yarn sut`
Run all e2e test	`yarn test` (starts backend SUT and compile frontend and cypress headless)
Run all e2e test with FE in dev mode	`yarn test:dev` (starts backend SUT and frontend in dev mode and cypress headless)
Run cypress IDE	`yarn sut`, `yarn frontend:sut` and `yarn cy:open` (starts frontend SUT in dev mode, backend SUT and cypress IDE)
Generate TypeScript Interfaces	`yarn generateTypeScript` (Generate TypeScript Interfaces from backend JSON classes. Should run manually every time backend JSON class changes)

Structure

Purpose	Location
feature files	`cypress/integration/*.feature`
step definitions	`cypress/step_definitions/common/*.{js,ts}`
custom DSL	`cypress/support/*.js`
cucumber hooks	`cypress/step_definitions/common/hook.ts`
test fixtures	`cypress/fixtures/.`
cypress config	`cypress/config/*.json`
cypress plugins	`cypress/plugins/index.js`

4. Vue3 web-app frontend

We chose Vue3 + Vite to build our frontend.

How-to

Run frontend unit tests

From doughnut source root directory

yarn frontend:test

Build & Bundle Vue3 frontend web-app assets and startup backend app (doughnut webapp will launch on port 9081).

yarn frontend:build
yarn sut

Expect to find minified and uglified web bundle assets in backend/src/main/resources/static directory:

❯ pwd
/home/lia/doughnut/backend/src/main/resources/static
❯ tree -L 3
.
├── assets
│   ├── main.32137c85.js
│   ├── main.b097c993.css
│   └── vendor.8f9eb49d.js
├── index.html
├── odd-e.ico
└── odd-e.png

1 directory, 6 files

hatelove/doughnut