https://github.com/deomorxsy/meucafelist
A slim JRE and yew-rs setup to deploy your custom MAL list
https://github.com/deomorxsy/meucafelist
corretto jlink jre wasm yew-rs
Last synced: 8 days ago
JSON representation
A slim JRE and yew-rs setup to deploy your custom MAL list
- Host: GitHub
- URL: https://github.com/deomorxsy/meucafelist
- Owner: deomorxsy
- License: gpl-3.0
- Created: 2024-04-06T01:09:56.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-07-22T17:30:43.000Z (about 1 year ago)
- Last Synced: 2025-01-08T06:46:47.139Z (9 months ago)
- Topics: corretto, jlink, jre, wasm, yew-rs
- Language: Dockerfile
- Homepage:
- Size: 54.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
## meuCafeList
[](https://github.com/deomorxsy/meuCafeList/actions/workflows/slimjre_ci.yml)
[](https://github.com/deomorxsy/meuCafeList/actions/workflows/wasm_ci.yml)
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.
- 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
1. clone repository with SSH and enter directory
```sh
git clone git@github.com:deomorxsy/meuCafeList.git
cd ./meuCafeList/
```
2. Build with **make build**
3. Test with **make test**
4. Run/Stop the app: **make up/down**
### Scaffolding
1. **make scaff** to run [setup.sh](./scripts/skel.sh) and generate a similar project directory structure
### 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 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.
The orchestration tool docker-compose supports Podman Service through the DOCKER_HOST environment variable. This makes it possible to run containers with podman but with the benefit of rootless.
Source the script and run it to run compose with podman, or just put a ```make up```. XD
```sh
; source ./scripts/ccr.sh; checker
```
#### 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.
```sh
; kubectl apply -f ./deploy.yml
```