style: make docs more concise

Author: deomorxsy

.github/workflows/ci.yml renamed to .github/workflows/slimjre_ci.yml

@@ -1,45 +1,40 @@
-# meuCafeList
+## meuCafeList
+[![slimjre](https://github.com/deomorxsy/meuCafeList/actions/workflows/slimjre_ci.yml/badge.svg)](https://github.com/deomorxsy/meuCafeList/actions/workflows/slimjre_ci.yml)
+[![wasm-yew](https://github.com/deomorxsy/meuCafeList/actions/workflows/wasm_ci.yml/badge.svg)](https://github.com/deomorxsy/meuCafeList/actions/workflows/wasm_ci.yml)
 
-A speedrun attempt to clone [MAL](https://myanimelist.net/) lists into a github pages subdomain, using SpringBoot. IaC automation provided by OCI containers, compose, github actions and scaffolding with shellscript.
-
-The second attempt is to make the app ~**blazingly**~ fast by having a slim container image build, featuring:
-- alpine as OCI container distro;
+Featuring:
+- Alpine as OCI container distro;
 - [corretto-22](https://hub.docker.com/_/amazoncorretto) as JRE;
-- symbol stripping with [jlink](https://docs.oracle.com/en/java/javase/17/docs/specs/man/jlink.html);
-- multi-stage builds to avoid container layer bloat.
+- Symbol stripping with [jlink](https://docs.oracle.com/en/java/javase/17/docs/specs/man/jlink.html);
+- Multi-stage builds to avoid container layer bloat.
 - TDD (Test-Driven-Development) is implemented on build on a layer that will be discarded from the final production image, which will contain the artifact.
+- yew-rs serving wasm with trunk/wasm-packer
 
-## Usage
+### Usage
 
 1. clone repository with SSH and enter directory
 ```sh
 git clone [email protected]:deomorxsy/meuCafeList.git
 cd ./meuCafeList/
 ```
+2. Build with **make build**
 
-2. **make build** to build with:
-```sh
-mvn compile exec:java -Dexec.mainClass="com.meucafelist.app.App"
-```
-3. **make test** to test the app.
-
-4. **make up/down** to respectively run or stop the app.
+3. Test with **make test**
 
-5. general infra debugging
-- [util-linux/sys-utils](https://github.com/util-linux/util-linux/tree/master/sys-utils) namespaces related tools
+4. Run/Stop the app: **make up/down**
 
-## Scaffolding
+### Scaffolding
 
-1. **make scaff** to run [setup.sh](./scripts/skel.sh) and generate the project skeleton directory structure:
+1. **make scaff** to run [setup.sh](./scripts/skel.sh) and generate a similar project directory structure
 
-## Deployment
+### Deployment
 
 This repository uses Github Actions for Continuous Integration. Similar to how to run manually, the [yaml script](./.github/workflows/ci.yml) calls Makefile, which calls compose.yml, which runs the containers based on the specific Dockerfile context. It consists in three containers:
 - server: the SpringBoot application on a slim JRE with amazon-corretto and the Alpine distro.
 - client: the Yew application frontend on a slim Rust environment. [This](./client/Dockerfile) multi-stage build was inspired by codefeetime's [article](https://www.codefeetime.com/post/docker-config-for-actix-web-diesel-and-postgres/).
 - nginx as web server, reverse proxy, etc.
 
-### compose (+ Podman Service)
+#### compose (+ Podman Service)
 
 Compose concentrates in orchestrating multiple containers in a single host. To do this with k8s, you would need [kind](https://kind.sigs.k8s.io/), [minikube](https://minikube.sigs.k8s.io/docs/start/), [k3s](https://k3s.io/) (does not use virtualization) or similar. It was made to be compatible with other OCI runtimes, such as Podman, which was one of the first to enable rootless containers, and can be setup with compose using the Podman Service's systemd unit file for unix sockets.
 
@@ -51,7 +46,7 @@ Source the script and run it to run compose with podman, or just put a ```make u
 ; source ./scripts/ccr.sh; checker
 ```
 
-### k8s
+#### k8s
 
 Kubernetes is a container orchestrator that have a YAML syntax similar to the CI deployment from this repo. To run this project on single host just like the Compose tool, you can use tools like kind or minikube in a full-virtualized environment or k3s which don't use full-virtualization. The cluster setup such as ingress and egress will not be covered here.