Migrate project activity to LFNext

docker/Makefile

@@ -81,4 +81,5 @@ clean-volumes:
 
 .PHONY: clean-powerwash
 clean-powerwash: clean-volumes
-	docker compose down --rmi all
+	docker rmi -f `docker images -q "lf-*"`
+	docker builder prune -f

docker/db/.gitignore

@@ -0,0 +1 @@
+dump

docker/db/Makefile

@@ -0,0 +1,14 @@
+clean:
+	docker compose down
+
+db:
+	docker compose up -d db
+
+dump: db
+	docker compose exec db mongodump
+	docker compose cp db:/dump ./dump
+
+restore: db
+	docker compose cp ./dump db:/dump
+	docker compose exec db mongorestore
+

docker/db/README.md

@@ -0,0 +1,43 @@
+# Creating and utilizing any test data
+
+## Create a dump
+
+1. start the app
+1. create all the data you want through the app
+1. `make dump clean` to create a `dump` folder in this directory
+1. `tar -cf <name-representative-of-data>.tar dump`, e.g., `tar -cf activity.tar dump`, and decide whether to commit this or not for others to use.
+
+## Load a dump
+
+1. `tar -xf <name-representative-of-data>.tar` and rename to `dump`
+1. `make restore clean` to load the `dump` directory
+
+# Common mongo commands
+
+> https://www.mongodb.com/docs/v4.4/mongo
+
+`mongo` within `db` container
+
+> https://www.mongodb.com/docs/manual/reference/mongo-shell/#command-helpers
+
+`show dbs`
+
+`use scriptureforge`
+
+`show collections`
+
+`exit`
+
+> https://www.mongodb.com/docs/manual/reference/mongo-shell/#queries
+
+`db.users.find()`
+
+# Test data
+
+## Activity
+
+| username | email               | password      | project     |
+| -------- | ------------------- | ------------- | ----------- |
+| admin    | admin@example.com   | password      | all         |
+| johndoe  | jd@example.org      | languageforge | project-1   |
+| janedoe  | janedoe@example.org | languageforge | project-2   |

docker/next-app/Caddyfile

@@ -7,8 +7,10 @@
 :80 {
 	@next_app_paths {
 		path /_app/*
+		# ref for existing: /src/index.php
 		path /app/changepassword
 		path /password*
+		path /projects*
 	}
 	route @next_app_paths {
 		rewrite /app/changepassword /password/change

docker/next-app/Dockerfile.next-app

@@ -3,7 +3,7 @@ FROM node:alpine AS builder
 
 WORKDIR /app
 
-COPY jsconfig.json package-lock.json package.json postcss.config.cjs svelte.config.js tailwind.config.cjs /app/
+COPY tsconfig.json package-lock.json package.json postcss.config.cjs svelte.config.js vite.config.js tailwind.config.cjs /app/
 COPY src /app/src
 COPY static /app/static
 

docker/next-app/dev/Caddyfile

@@ -6,13 +6,16 @@
 
 :80 {
 	@next_app_paths {
-		path *svelte* # when running next-app in dev mode, this is needed.
-		path *node_modules* # when running next-app in dev mode, this is needed.
-		path *vite* # when running next-app in dev mode, this is needed.
-		path /src/lib* # when running next-app in dev mode, this is needed.
-		path /_app/*
+		# when running next-app in dev mode, these are needed.
+		path /.svelte-kit/*
+		path *node_modules*
+		path /@vite/*
+		path /src/*
+
+		# ref for existing: /src/index.php
 		path /app/changepassword
 		path /password*
+		path /projects*
 	}
 	route @next_app_paths {
 		rewrite /app/changepassword /password/change

docker/next-app/dev/Dockerfile

@@ -2,7 +2,7 @@ FROM node:alpine
 
 WORKDIR /app
 
-COPY jsconfig.json package-lock.json package.json postcss.config.cjs svelte.config.js tailwind.config.cjs /app
+COPY tsconfig.json package-lock.json package.json postcss.config.cjs svelte.config.js vite.config.js tailwind.config.cjs /app/
 COPY src /app/src
 COPY static /app/static
 

docs/DEVELOPER.md

@@ -133,7 +133,7 @@ After a minute or two, your source or test changes should be applied and you sho
 ### Running dev
 
 1. `make dev` will start the legacy app in development mode, i.e. changes to source code will immediately be reflected in the locally running app.
-1. `make next-dev` will start the next app in development mode, i.e. changes to source code will immediately be reflected in the locally running app.
+1. `make next-dev` will start the next app in development mode, i.e. changes to source code will immediately be reflected in the locally running app.  Access non-ssl: http://localhost
 > TODO: There is a desire to consolidate these into a single use case, `make dev`.
 
 ### Visual Studio Code ###

next-app/README-Tech.md

@@ -90,7 +90,7 @@ A backend layer is being utilized to insulate the UI from implemenation details
 
 ### Common error handling
 
-In an effort to provide a common error experience for users and eliminate much of the biolerplate on devs, a central error handling implementation is provided in `$lib/error`.  It has both a shared API as well as a component for use in the app.  Central, generic hooks for client-side errors of all kinds have been implemented in the `$lib/error/index.js` but there are not similar hooks for _all_ error scenarios on the server-side which may result in more biolerplate for devs when it comes to error handling there.
+In an effort to provide a common error experience for users and eliminate much of the boilerplate on devs, a central error handling implementation is provided in `$lib/error`.  It has both a shared API as well as a component for use in the app.  Central, generic hooks for client-side errors of all kinds have been implemented in the `$lib/error/index.js` but there are not similar hooks for _all_ error scenarios on the server-side which may result in more boilerplate for devs when it comes to error handling there.
 
 ### Common fetch
 
@@ -104,3 +104,8 @@ Found in `$lib/fetch/client.js`.  This wrapper exports some of the most common t
 
 Found in `$lib/fetch/server.js`.  This wrapper exports some of the most common types of fetches, handles errors consistently and abides by the legacy app's `/api/sf` contract.
 
+### FAQ's
+
+#### Why are we using `$$props.class` when Svelte docs suggest against it?
+
+This a very well-known and conventional way of getting all you need from the element without the extra boilerplate code required to expose an explicit API for each [Attribute](https://developer.mozilla.org/en-US/docs/Web/API/Element/attributes) or "properties" as referred to by Svelte (https://svelte.dev/docs#template-syntax-attributes-and-props).  See https://github.com/sillsdev/web-languageforge/pull/1416/files#r894114808 for further rationale and comparison of alternative which is considered unnecessarily verbose and not as maintainable.