WHY42 - 用户贡献 [zh-cn]

Mac colima

2026-05-07T03:52:40Z

Riguz：创建页面，内容为“ <syntaxhighlight lang="bash"> sudo ports install docker mkdir -p ~/.docker/cli-plugins curl -SL https://github.com/docker/compose/releases/latest/download/docker-compose-darwin-$(uname -m | sed 's/x86_64/x86_64/;s/arm64/aarch64/') \ -o ~/.docker/cli-plugins/docker-compose chmod +x ~/.docker/cli-plugins/docker-compose docker compose version colima start </syntaxhighlight> Catgory:Linux/Unix”

<syntaxhighlight lang="bash">
sudo ports install docker
mkdir -p ~/.docker/cli-plugins
curl -SL https://github.com/docker/compose/releases/latest/download/docker-compose-darwin-$(uname -m | sed 's/x86_64/x86_64/;s/arm64/aarch64/') \
-o ~/.docker/cli-plugins/docker-compose
chmod +x ~/.docker/cli-plugins/docker-compose
docker compose version

colima start
</syntaxhighlight>

[[Catgory:Linux/Unix]]

Linux server setup

2026-03-28T14:03:01Z

Riguz：/* ssh config */

Ubuntu server setup:

=System settings =
Add admin user:
<syntaxhighlight lang="bash">
adduser sammy
usermod -aG sudo sammy
su - sammy
</syntaxhighlight>
== Update system ==
<syntaxhighlight lang="bash">
sudo apt update
sudo apt upgrade
do-release-upgrade

reboot
</syntaxhighlight>

== hostname ==

<syntaxhighlight lang="bash">
vim /etc/hostname
</syntaxhighlight>

== user ==
<syntaxhighlight lang="bash">
adduser ubuntu
usermod -aG sudo ubuntu
</syntaxhighlight>

== ssh config ==

<syntaxhighlight lang="bash">
ssh-copy-id -p 50000 ubuntu@12.98.23.12

# vim /etc/ssh/sshd_config
Port 54194
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

service ssh restart
ssh -p 50000 ubuntu@12.98.23.12
</syntaxhighlight>

Note: for Ubuntu 24.04+ with systemd socket
<syntaxhighlight lang="bash">
# To change the port
sudo vim /lib/systemd/system/ssh.socket
[Socket]
ListenStream=0.0.0.0:54194
ListenStream=[::]:54194

sudo systemctl daemon-reload
sudo systemctl stop ssh.socket
sudo systemctl restart ssh
netstat -anp | grep 54194
(No info could be read for "-p": geteuid()=1000 but you should be root.)
tcp 0 0 0.0.0.0:54194 0.0.0.0:* LISTEN -
tcp6 0 0 :::54194 :::* LISTEN -
</syntaxhighlight>

== ufw==
<syntaxhighlight lang="bash">
sudo ufw enable
sudo ufw allow 80
sudo ufw allow 443
sudo ufw allow 50000
sudo ufw status numbered
</syntaxhighlight>

== V2ray ==

[[V2Ray global proxy]]

= Web server =
== Ngnix ==
<syntaxhighlight lang="bash">
$ sudo apt install nginx
$ sudo systemctl status nginx

</syntaxhighlight>

== Certbot ==
Install via pip<ref>https://certbot.eff.org/instructions?ws=nginx&os=pip&commit=%3E</ref>
<syntaxhighlight lang="bash">
sudo apt install certbot
sudo apt install python3 python3-dev python3-venv libaugeas-dev gcc
sudo python3 -m venv /opt/certbot/
sudo /opt/certbot/bin/pip install --upgrade pip
sudo /opt/certbot/bin/pip install certbot certbot-nginx
sudo ln -s /opt/certbot/bin/certbot /usr/bin/certbot
sudo certbot --nginx
sudo nginx -s reload
</syntaxhighlight>

[[Category:Linux/Unix]]

Leetcode top75

2026-03-25T01:44:20Z

Riguz：

Array/String:

* 1768. Merge Strings Alternately: use StringBuilder
* 1071. Greatest Common Divisor of Strings: if str1 and str2 can be divided, then
<math>
str1 + str2 = str2 + str1
\gcd(a,b)=\gcd(b,a \bmod b)
</math>
just get the substring of gcd length
* 1431. Kids With the Greatest Number of Candies: find the max value first
* 605. Can Place Flowers: check neighbours
* 345. Reverse Vowels of a String: exchange local array
* 151. Reverse Words in a String: split and then concat/ reverse array
* 238. Product of Array Except Self: p = p_left * p_right
* 334. Increasing Triplet Subsequence: tracking the smallest, the second smallest num

Leetcode top75

2026-03-25T01:11:20Z

Riguz：

Leetcode top75

2026-03-24T16:23:01Z

Riguz：

Leetcode top75

2026-03-24T15:13:57Z

Riguz：

Leetcode top75

2026-03-24T15:13:27Z

Riguz：创建页面，内容为“Array/String: * 1768. Merge Strings Alternately: use StringBuilder * 1071. Greatest Common Divisor of Strings: if str1 and str2 can be divided, then <math> str1 + str2 = str2 + str1 \gcd(a,b)=\gcd(b,a \bmod b) </math> just get the substring of gcd length”

Linux server setup

2026-03-06T04:59:51Z

Riguz：/* System settings */

Ubuntu server setup:

=System settings =
Add admin user:
<syntaxhighlight lang="bash">
adduser sammy
usermod -aG sudo sammy
su - sammy
</syntaxhighlight>
== Update system ==
<syntaxhighlight lang="bash">
sudo apt update
sudo apt upgrade
do-release-upgrade

reboot
</syntaxhighlight>

== hostname ==

<syntaxhighlight lang="bash">
vim /etc/hostname
</syntaxhighlight>

== user ==
<syntaxhighlight lang="bash">
adduser ubuntu
usermod -aG sudo ubuntu
</syntaxhighlight>

== ssh config ==

<syntaxhighlight lang="bash">
ssh-copy-id -p 50000 ubuntu@12.98.23.12

# vim /etc/ssh/sshd_config
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

service ssh restart
ssh -p 50000 ubuntu@12.98.23.12
</syntaxhighlight>

== ufw==
<syntaxhighlight lang="bash">
sudo ufw enable
sudo ufw allow 80
sudo ufw allow 443
sudo ufw allow 50000
sudo ufw status numbered
</syntaxhighlight>

== V2ray ==

[[V2Ray global proxy]]

= Web server =
== Ngnix ==
<syntaxhighlight lang="bash">
$ sudo apt install nginx
$ sudo systemctl status nginx

</syntaxhighlight>

== Certbot ==
Install via pip<ref>https://certbot.eff.org/instructions?ws=nginx&os=pip&commit=%3E</ref>
<syntaxhighlight lang="bash">
sudo apt install certbot
sudo apt install python3 python3-dev python3-venv libaugeas-dev gcc
sudo python3 -m venv /opt/certbot/
sudo /opt/certbot/bin/pip install --upgrade pip
sudo /opt/certbot/bin/pip install certbot certbot-nginx
sudo ln -s /opt/certbot/bin/certbot /usr/bin/certbot
sudo certbot --nginx
sudo nginx -s reload
</syntaxhighlight>

[[Category:Linux/Unix]]

Linux server setup

2026-03-06T04:58:29Z

Riguz：

Ubuntu server setup:

=System settings =
== Update system ==
<syntaxhighlight lang="bash">
sudo apt update
sudo apt upgrade
do-release-upgrade

reboot
</syntaxhighlight>

== hostname ==

<syntaxhighlight lang="bash">
vim /etc/hostname
</syntaxhighlight>

== user ==
<syntaxhighlight lang="bash">
adduser ubuntu
usermod -aG sudo ubuntu
</syntaxhighlight>

== ssh config ==

<syntaxhighlight lang="bash">
ssh-copy-id -p 50000 ubuntu@12.98.23.12

# vim /etc/ssh/sshd_config
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

service ssh restart
ssh -p 50000 ubuntu@12.98.23.12
</syntaxhighlight>

== ufw==
<syntaxhighlight lang="bash">
sudo ufw enable
sudo ufw allow 80
sudo ufw allow 443
sudo ufw allow 50000
sudo ufw status numbered
</syntaxhighlight>

== V2ray ==

[[V2Ray global proxy]]

= Web server =
== Ngnix ==
<syntaxhighlight lang="bash">
$ sudo apt install nginx
$ sudo systemctl status nginx

</syntaxhighlight>

== Certbot ==
Install via pip<ref>https://certbot.eff.org/instructions?ws=nginx&os=pip&commit=%3E</ref>
<syntaxhighlight lang="bash">
sudo apt install certbot
sudo apt install python3 python3-dev python3-venv libaugeas-dev gcc
sudo python3 -m venv /opt/certbot/
sudo /opt/certbot/bin/pip install --upgrade pip
sudo /opt/certbot/bin/pip install certbot certbot-nginx
sudo ln -s /opt/certbot/bin/certbot /usr/bin/certbot
sudo certbot --nginx
sudo nginx -s reload
</syntaxhighlight>

[[Category:Linux/Unix]]

Rock5b+

2025-12-10T15:34:24Z

Riguz：/* Armbian */

= Install system =

<ref>https://docs.radxa.com/rock5/rock5b/getting-started/install-os/boot_from_sd_card</ref>

Prerequsits:

* Install Etcher

== Rock5b+ Official image ==
Download image from rock site https://docs.radxa.com/rock5/rock5b/download:

rock-5b-plus_bookworm_kde_b2.output.img.xz

Note that the image must be decompressed first.

[[Image:etcher-rock5b.png|600px]]

[[Image:etcher-rock5b-finished.png|600px]]

You may get error like:

[[Image:etcher-error-mac.png|600px]]

Grant full disk access to etcher in privacy setting and run as sudo user:

<syntaxhighlight lang="java">
# see https://github.com/balena-io/etcher/issues/4451
sudo open -a balenaEtcher
</syntaxhighlight>

== Armbian ==

Download image from https://www.armbian.com/rock-5b-plus/.

eg.
<syntaxhighlight lang="bash" inline>Armbian_25.11.1_Rock-5b_noble_vendor_6.1.115_gnome_desktop.img.xz</syntaxhighlight>

Note that the xz file must be extracted before writing.

<syntaxhighlight lang="bash">
shasum -a 256 ~/Downloads/Armbian_25.11.1_Rock-5b_noble_vendor_6.1.115_gnome_desktop.img.xz
d3977e1bb9932b35a10e891fddb4e5d4840d709f2094c5a0cfdfb15cfa97b522 /Users/riguz/Downloads/Armbian_25.11.1_Rock-5b_noble_vendor_6.1.115_gnome_desktop.img.xz
</syntaxhighlight>

Write to image using etcher or USBImager. <ref>https://docs.armbian.com/User-Guide_Getting-Started/</ref>

<syntaxhighlight lang="bash">
(base) ➜ ~ picocom -b 1500000 -d 8 /dev/tty.wchusbserial5ABA0915851
picocom v3.2a

port is : /dev/tty.wchusbserial5ABA0915851
flowcontrol : none
baudrate is : 1500000
parity is : none
databits are : 8
stopbits are : 1
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
hangup is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv -E
imap is :
omap is :
emap is : crcrlf,delbs,
logfile is : none
initstring : none
exit_after is : not set
exit is : no

Type [C-a] [C-h] to see available commands
Terminal ready

Repeat root password: ****
Rejected - passwords do not match. Try again [3].
Create root password: *********
Repeat root password: *********

Choose default system command shell:

1) bash
2) zsh
2

Shell: ZSH

Creating a new user account. Press <Ctrl-C> to abort

Desktop environment will not be enabled if you abort the new user creation

Please provide a username (eg. your first name): riguz
Create user (riguz) password: *********
Repeat user (riguz) password: *********

Please provide your real name: Riguz

Dear Riguz, your account riguz has been created and is sudo enabled.
Please use this account for your daily work from now on.

Internet connection was not detected.

Connect via wireless? [Y/n]
</syntaxhighlight>

== TTL connection ==

<syntaxhighlight lang="bash">
ls /dev/tty.*
/dev/tty.wchusbserial5ABA0915851
picocom -b 1500000 -d 8 /dev/tty.wchusbserial5ABA0915851
</syntaxhighlight>

== Install system ==

[[Category:Embedding]]

Rock5b+

2025-12-10T15:24:37Z

Riguz：/* Armbian */

Rock5b+

2025-12-10T14:57:46Z

Riguz：/* Rock5b+ Official image */

文件:Etcher-error-mac.png

2025-12-10T14:56:47Z

Riguz：

Rock5b+

2025-12-10T14:56:19Z

Riguz：/* Rock5b+ Official image */

Rock5b+

2025-12-10T14:55:07Z

Riguz：/* Armbian */

Rock5b+

2025-12-10T14:30:09Z

Riguz：/* Rock5b+ Official image */

文件:Etcher-rock5b-finished.png

2025-12-10T14:29:35Z

Riguz：

文件:Etcher-rock5b.png

2025-12-10T14:28:52Z

Riguz：

Rock5b+

2025-12-10T14:28:22Z

Riguz：/* Install system */

Rock5b+

2025-11-04T14:01:48Z

Riguz：创建页面，内容为“= Install system = == TTL connection == <syntaxhighlight lang="bash"> ls /dev/tty.* /dev/tty.wchusbserial5ABA0915851 picocom -b 1500000 -d 8 /dev/tty.wchusbserial5ABA0915851 </syntaxhighlight> == Install system == Category:Embedding”

= Install system =
== TTL connection ==

<syntaxhighlight lang="bash">
ls /dev/tty.*
/dev/tty.wchusbserial5ABA0915851
picocom -b 1500000 -d 8 /dev/tty.wchusbserial5ABA0915851
</syntaxhighlight>

== Install system ==

[[Category:Embedding]]

Keycloak

2025-10-08T09:54:02Z

Riguz：

== Install ==
<syntaxhighlight lang="bash">
docker network create dev-zone
docker stop yai-postgres && docker rm yai-postgres
docker run \
--name yai-postgres \
-p 5432:5432 \
-e POSTGRES_USER=${POSTGRES_USER} \
-e POSTGRES_DB=development-db \
-e POSTGRES_PASSWORD=${POSTGRES_PASSWORD} \
-v ./postgres-data:/var/lib/postgresql/18/docker \
--network dev-zone \
-d postgres:18

# create the schema manually

docker run --name yai-keycloak \
-p 8081:8080 -d \
-e KC_BOOTSTRAP_ADMIN_USERNAME=${KC_BOOTSTRAP_ADMIN_USERNAME} \
-e KC_BOOTSTRAP_ADMIN_PASSWORD=${KC_BOOTSTRAP_ADMIN_PASSWORD} \
-e KC_DB=postgres \
-e KC_DB_URL=jdbc:postgresql://yai-postgres:5432/development-db \
-e KC_DB_SCHEMA=keycloak \
-e KC_DB_USERNAME=${POSTGRES_USER} \
-e KC_DB_PASSWORD=${POSTGRES_PASSWORD} \
--network yai-zone \
quay.io/keycloak/keycloak:26.3.2 start-dev \
--hostname=https://auth.example.com
</syntaxhighlight>

Reversed proxy<ref>https://medium.com/@asynchronouscal/keycloak-production-mode-with-docker-step-by-step-guide-b284927e72c0</ref> <ref>https://www.keycloak.org/server/reverseproxy</ref>:

<syntaxhighlight lang="config">
server {

server_name oauth.example.com;

location / {
root html;
index index.html index.htm;
proxy_pass http://localhost:8081;

proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port 443;
}
...
}
</syntaxhighlight>

== Configure ==
* Create realm: my-org
* Create users: whatever
* Create client: my-app

* Client ID: my-app
* Valid redirect URIs: http://localhost:5173/auth/callback
* Valid post logout redirect URIs : http://localhost:5173
* Web origins: http://localhost:5173 (No slash at end!!!)
* Client authentication: off (for public clients)
* Authentication flow: Standard flow, Direct access grants

[[Category:OAuth]]

Keycloak

2025-10-06T15:18:47Z

Riguz：/* Install */

== Install ==
<syntaxhighlight lang="bash">
docker network create dev-zone
docker stop yai-postgres && docker rm yai-postgres
docker run \
--name yai-postgres \
-p 5432:5432 \
-e POSTGRES_USER=${POSTGRES_USER} \
-e POSTGRES_DB=development-db \
-e POSTGRES_PASSWORD=${POSTGRES_PASSWORD} \
-v ./postgres-data:/var/lib/postgresql/18/docker \
--network dev-zone \
-d postgres:18

docker run --name yai-keycloak \
-p 8081:8080 -d \
-e KC_BOOTSTRAP_ADMIN_USERNAME=${KC_BOOTSTRAP_ADMIN_USERNAME} \
-e KC_BOOTSTRAP_ADMIN_PASSWORD=${KC_BOOTSTRAP_ADMIN_PASSWORD} \
-e KC_DB=postgres \
-e KC_DB_URL=jdbc:postgresql://yai-postgres:5432/development-db \
-e KC_DB_SCHEMA=keycloak \
-e KC_DB_USERNAME=${POSTGRES_USER} \
-e KC_DB_PASSWORD=${POSTGRES_PASSWORD} \
--network yai-zone \
quay.io/keycloak/keycloak:26.3.2 start-dev \
--hostname=https://auth.example.com
</syntaxhighlight>

Reversed proxy<ref>https://medium.com/@asynchronouscal/keycloak-production-mode-with-docker-step-by-step-guide-b284927e72c0</ref> <ref>https://www.keycloak.org/server/reverseproxy</ref>:

<syntaxhighlight lang="config">
server {

server_name oauth.example.com;

location / {
root html;
index index.html index.htm;
proxy_pass http://localhost:8081;

proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Forwarded-Port 443;
}
...
}
</syntaxhighlight>

== Configure ==
* Create realm: my-org
* Create users: whatever
* Create client: my-app

* Client ID: my-app
* Valid redirect URIs: http://localhost:5173/auth/callback
* Valid post logout redirect URIs : http://localhost:5173
* Web origins: http://localhost:5173 (No slash at end!!!)
* Client authentication: off (for public clients)
* Authentication flow: Standard flow, Direct access grants

[[Category:OAuth]]

Sphinx

2025-10-06T10:57:04Z

Riguz：

<syntaxhighlight lang="bash">
pip install sphinx myst-parser
pip install sphinxcontrib-bibtex sphinx-design sphinx-copybutton sphinxext-opengraph
pip install sphinx-mathjax-offline
pip install sphinx-book-theme

cd blog
sphinx-quickstart
</syntaxhighlight>

Sphinx

2025-10-06T01:45:03Z

Riguz：创建页面，内容为“<syntaxhighlight lang="bash"> pip install sphinx myst-parser pip install sphinxcontrib-bibtex sphinx-design sphinx-copybutton sphinxext-opengraph pip install sphinx-mathjax-offline cd blog sphinx-quickstart </syntaxhighlight>”

Linux server setup

2025-10-05T14:44:19Z

Riguz：/* Web server */

=System settings =
== Update system ==
<syntaxhighlight lang="bash">
sudo apt update
sudo apt upgrade
do-release-upgrade

reboot
</syntaxhighlight>

== hostname ==

<syntaxhighlight lang="bash">
vim /etc/hostname
</syntaxhighlight>

== user ==
<syntaxhighlight lang="bash">
adduser ubuntu
usermod -aG sudo ubuntu
</syntaxhighlight>

== ssh config ==

<syntaxhighlight lang="bash">
ssh-copy-id -p 50000 ubuntu@12.98.23.12

# vim /etc/ssh/sshd_config
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes

service ssh restart
ssh -p 50000 ubuntu@12.98.23.12
</syntaxhighlight>

== ufw==
<syntaxhighlight lang="bash">
sudo ufw enable
sudo ufw allow 80
sudo ufw allow 443
sudo ufw allow 50000
sudo ufw status numbered
</syntaxhighlight>

== V2ray ==

[[V2Ray global proxy]]

= Web server =
== Ngnix ==
<syntaxhighlight lang="bash">
$ sudo apt install nginx
$ sudo systemctl status nginx

</syntaxhighlight>

== Certbot ==
Install via pip<ref>https://certbot.eff.org/instructions?ws=nginx&os=pip&commit=%3E</ref>
<syntaxhighlight lang="bash">
sudo apt install certbot
sudo apt install python3 python3-dev python3-venv libaugeas-dev gcc
sudo python3 -m venv /opt/certbot/
sudo /opt/certbot/bin/pip install --upgrade pip
sudo /opt/certbot/bin/pip install certbot certbot-nginx
sudo ln -s /opt/certbot/bin/certbot /usr/bin/certbot
sudo certbot --nginx
sudo nginx -s reload
</syntaxhighlight>

[[Category:Linux/Unix]]

Linux server setup

2025-10-05T10:38:26Z

Riguz：/* V2ray */

Linux server setup

2025-10-05T10:00:14Z

Riguz：/* V2ray */

Linux server setup

2025-10-05T10:00:06Z

Riguz：/* System settings */

V2Ray global proxy

2025-10-05T09:59:22Z

Riguz：/* Basic Config */

= Install V2Ray (Server side) =
== Install ==
https://github.com/v2fly/fhs-install-v2ray

<syntaxhighlight lang="bash">
# switch to root user and then install
$ sudo su -

$ bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-release.sh)
$ systemctl enable v2ray
$ systemctl start v2ray

$ bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-dat-release.sh)

$ v2ray version
V2Ray 5.22.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.23.2 linux/amd64)
A unified platform for anti-censorship.
</syntaxhighlight>

== Basic Config ==
<syntaxhighlight lang="bash">
$ systemctl status v2ray
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; preset: enable>
Drop-In: /etc/systemd/system/v2ray.service.d
└─10-donot_touch_single_conf.conf
Active: active (running) since Fri 2025-04-18 14:11:22 UTC; 5 months 17 da>
Docs: https://www.v2fly.org/
Main PID: 719 (v2ray)
Tasks: 14 (limit: 9441)
Memory: 35.8M (peak: 103.4M)
CPU: 8h 56min 41.528s
CGroup: /system.slice/v2ray.service
└─719 /usr/local/bin/v2ray run -config /usr/local/etc/v2ray/config>

Warning: some journal files were not opened due to insufficient permissions.
</syntaxhighlight>

/usr/local/etc/v2ray/config.json
<syntaxhighlight lang="json">
{
"inbounds": [{
"port": 10086,
"protocol": "vmess",
"settings": {
"clients": [{ "id": "b831381d-6324-4d53-ad4f-8cda48b30811" }]
}
}],
"outbounds": [{
"protocol": "freedom",
"settings": {}
}]
}
</syntaxhighlight>

restart v2ray server:
<syntaxhighlight lang="cpp">
$ sudo systemctl restart v2ray
</syntaxhighlight>

== V2RayU Client ==
Configure -> add v2ray server, input ip/port and client id.

Git ssh over socks proxy:

<syntaxhighlight lang="bash">
# vim ~/.ssh/config
Host github.com
HostName github.com
User git
ProxyCommand nc -v -x 127.0.0.1:1080 %h %p

</syntaxhighlight>

[[Category:Linux/Unix]]

V2Ray global proxy

2025-10-05T09:43:01Z

Riguz：/* Install */

= Install V2Ray (Server side) =
== Install ==
https://github.com/v2fly/fhs-install-v2ray

<syntaxhighlight lang="bash">
# switch to root user and then install
$ sudo su -

$ bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-release.sh)
$ systemctl enable v2ray
$ systemctl start v2ray

$ bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-dat-release.sh)

$ v2ray version
V2Ray 5.22.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.23.2 linux/amd64)
A unified platform for anti-censorship.
</syntaxhighlight>

== Basic Config ==
<syntaxhighlight lang="bash">
$ systemctl status v2ray
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; preset: enable>
Drop-In: /etc/systemd/system/v2ray.service.d
└─10-donot_touch_single_conf.conf
Active: active (running) since Fri 2025-04-18 14:11:22 UTC; 5 months 17 da>
Docs: https://www.v2fly.org/
Main PID: 719 (v2ray)
Tasks: 14 (limit: 9441)
Memory: 35.8M (peak: 103.4M)
CPU: 8h 56min 41.528s
CGroup: /system.slice/v2ray.service
└─719 /usr/local/bin/v2ray run -config /usr/local/etc/v2ray/config>

Warning: some journal files were not opened due to insufficient permissions.
</syntaxhighlight>

/usr/local/etc/v2ray/config.json
<syntaxhighlight lang="json">
{
"inbounds": [{
"port": 10086,
"protocol": "vmess",
"settings": {
"clients": [{ "id": "b831381d-6324-4d53-ad4f-8cda48b30811" }]
}
}],
"outbounds": [{
"protocol": "freedom",
"settings": {}
}]
}
</syntaxhighlight>

restart v2ray server:

sudo systemctl restart v2ray

== V2RayU Client ==
Configure -> add v2ray server, input ip/port and client id.

Git ssh over socks proxy:

<syntaxhighlight lang="bash">
# vim ~/.ssh/config
Host github.com
HostName github.com
User git
ProxyCommand nc -v -x 127.0.0.1:1080 %h %p

</syntaxhighlight>

[[Category:Linux/Unix]]

V2Ray global proxy

2025-10-05T09:42:40Z

Riguz：/* Basic Config */

= Install V2Ray (Server side) =
== Install ==
https://github.com/v2fly/fhs-install-v2ray

<syntaxhighlight lang="bash">
# switch to root user and then install
sudo su -

bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-release.sh)
systemctl enable v2ray
systemctl start v2ray

bash <(curl -L https://raw.githubusercontent.com/v2fly/fhs-install-v2ray/master/install-dat-release.sh)

v2ray version
V2Ray 5.22.0 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.23.2 linux/amd64)
A unified platform for anti-censorship.
</syntaxhighlight>

== Basic Config ==
<syntaxhighlight lang="bash">
$ systemctl status v2ray
● v2ray.service - V2Ray Service
Loaded: loaded (/etc/systemd/system/v2ray.service; enabled; preset: enable>
Drop-In: /etc/systemd/system/v2ray.service.d
└─10-donot_touch_single_conf.conf
Active: active (running) since Fri 2025-04-18 14:11:22 UTC; 5 months 17 da>
Docs: https://www.v2fly.org/
Main PID: 719 (v2ray)
Tasks: 14 (limit: 9441)
Memory: 35.8M (peak: 103.4M)
CPU: 8h 56min 41.528s
CGroup: /system.slice/v2ray.service
└─719 /usr/local/bin/v2ray run -config /usr/local/etc/v2ray/config>

Warning: some journal files were not opened due to insufficient permissions.
</syntaxhighlight>

/usr/local/etc/v2ray/config.json
<syntaxhighlight lang="json">
{
"inbounds": [{
"port": 10086,
"protocol": "vmess",
"settings": {
"clients": [{ "id": "b831381d-6324-4d53-ad4f-8cda48b30811" }]
}
}],
"outbounds": [{
"protocol": "freedom",
"settings": {}
}]
}
</syntaxhighlight>

restart v2ray server:

sudo systemctl restart v2ray

== V2RayU Client ==
Configure -> add v2ray server, input ip/port and client id.

Git ssh over socks proxy:

<syntaxhighlight lang="bash">
# vim ~/.ssh/config
Host github.com
HostName github.com
User git
ProxyCommand nc -v -x 127.0.0.1:1080 %h %p

</syntaxhighlight>

[[Category:Linux/Unix]]

V2Ray global proxy

2025-10-05T09:41:30Z

Riguz：/* Install */

Linux server setup

2025-10-05T05:37:48Z

Riguz：/* ssh config */

Linux server setup

2025-10-05T05:31:44Z

Riguz：/* ssh config */

Linux server setup

2025-10-05T05:27:10Z

Riguz：/* ssh config */

Linux server setup

2025-10-05T05:25:52Z

Riguz：/* hostname */

Linux server setup

2025-10-05T05:22:52Z

Riguz：/* System settings */

Linux server setup

2025-10-05T03:27:54Z

Riguz：

=System settings =
<syntaxhighlight lang="bash">
sudo apt update
sudo apt upgrade
do-release-upgrade
</syntaxhighlight>

[[Category:Linux/Unix]]

Linux server setup

2025-10-05T03:17:04Z

Riguz：创建页面，内容为“ Category:Linux/Unix”

[[Category:Linux/Unix]]

未来住所设计

2025-09-08T14:12:53Z

Riguz：

= 装修 =
==布局==
==水电==
==网络==

=区域设计=
== 书房/工作室==
== 客厅==
== 卧室==
== 厨房==
== 洗手间==
== 阳台==

= 功能 =
== 太阳能电站 ==
== 机房 ==
== NAS ==
== 家庭影院==
== HIFI ==

== 生态系统==

= 创意 =

[[Category:House Design]]
[[Category:Reminder]]

未来住所设计

2025-09-08T14:09:52Z

Riguz：/* 客厅 */

= 装修 =
==布局==
==水电==
==网络==

=区域设计=
== 书房/工作室==
== 客厅==

== 卧室==
== 厨房==
== 洗手间==
== 阳台==

= 创意 =

[[Category:House Design]]
[[Category:Reminder]]

未来住所设计

2025-09-08T14:09:19Z

Riguz：创建页面，内容为“= 装修 = ==布局== ==水电== ==网络== =区域设计= == 书房/工作室== == 客厅== == 卧室== == 厨房== == 洗手间== == 阳台== = 创意 = Category:House Design Category:Reminder”

= 装修 =
==布局==
==水电==
==网络==

=区域设计=
== 书房/工作室==
== 客厅==
== 卧室==
== 厨房==
== 洗手间==
== 阳台==

= 创意 =

[[Category:House Design]]
[[Category:Reminder]]

DDD guide

2025-08-26T12:41:02Z

Riguz：/* Layers in DDD */

= Domain-Driven Design (DDD) Guide =

This guide provides an overview of key concepts and best practices for implementing Domain-Driven Design (DDD), focusing on the separation of concerns between the domain model, repository, and persistence layer.

== Key Principles of DDD ==
* '''Focus on the Domain''':
** The domain model represents the core business logic and rules.
** It should be independent of technical concerns like persistence or frameworks.

* '''Separation of Concerns''':
** Divide responsibilities between the domain layer, application layer, and infrastructure layer.
** Keep the domain layer free from infrastructure dependencies.

* '''Ubiquitous Language''':
** Use a shared language between developers and domain experts to ensure clarity and alignment.

* '''Repository Pattern''':
** Use repositories to abstract persistence logic and provide access to domain objects.

== Layers in DDD ==
<ref> https://learn.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice</ref>

<syntaxhighlight lang="cpp">
com.example.todo
├── application
│ ├── service
│ └── dto
├── domain
│ ├── model
│ ├── repository
│ └── service
├── infrastructure
│ ├── persistence
│ ├── messaging
│ └── configuration
└── interface
├── controller
└── mapper
</syntaxhighlight>

Dependency rule<ref>https://khalilstemmler.com/wiki/dependency-rule/</ref>:

[[Image:ddd-dependency-rule.svg|600px]]

=== Domain Layer ===
The domain layer contains the core business logic and domain models.

* '''Responsibilities''':
** Encapsulate business rules and behavior.
** Represent the core concepts of the domain.

* '''Key Components''':
** '''Entities''': Objects with a unique identity (e.g., `Todo`).
** '''Value Objects''': Immutable objects that represent a concept (e.g., `TodoId`).
** '''Aggregates''': A cluster of domain objects treated as a single unit.

* '''Best Practices''':
** Avoid adding persistence-related methods (e.g., `save()` or `delete()`) to domain models.
** Keep domain models focused on business logic.

* '''Example''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

public Todo(TodoId id, String title, String description) {
this.id = id;
this.title = title;
this.description = description;
this.completed = false;
}

public void markAsCompleted() {
this.completed = true;
}

// Getters and setters
}
</syntaxhighlight>

=== Application Layer ===
The application layer coordinates use cases and orchestrates interactions between the domain and infrastructure layers.

* '''Responsibilities''':
** Handle application-specific logic (e.g., workflows, use cases).
** Delegate persistence to repositories.

* '''Example''':
<syntaxhighlight lang="java">
public class TodoApplicationService {
private final TodoRepository todoRepository;

public TodoApplicationService(TodoRepository todoRepository) {
this.todoRepository = todoRepository;
}

public void createTodo(String title, String description) {
Todo todo = new Todo(new TodoId(UUID.randomUUID()), title, description);
todoRepository.save(todo);
}
}
</syntaxhighlight>

=== Infrastructure Layer ===
The infrastructure layer handles technical concerns like persistence, messaging, and external APIs.

* '''Responsibilities''':
** Implement repository interfaces defined in the domain layer.
** Map between domain models and database entities.

* '''Example''':
<syntaxhighlight lang="java">
@Repository
public class JpaTodoRepository implements TodoRepository {
private final SpringDataTodoEntityRepository entityRepository;

public JpaTodoRepository(SpringDataTodoEntityRepository entityRepository) {
this.entityRepository = entityRepository;
}

@Override
public void save(Todo todo) {
TodoEntity entity = mapToEntity(todo);
entityRepository.save(entity);
}

@Override
public Optional<Todo> findById(TodoId id) {
return entityRepository.findById(id.getValue())
.map(this::mapToDomain);
}

private TodoEntity mapToEntity(Todo todo) {
TodoEntity entity = new TodoEntity();
entity.setId(todo.getId().getValue());
entity.setTitle(todo.getTitle());
entity.setDescription(todo.getDescription());
entity.setCompleted(todo.isCompleted());
return entity;
}

private Todo mapToDomain(TodoEntity entity) {
return new Todo(
new TodoId(entity.getId()),
entity.getTitle(),
entity.getDescription(),
entity.isCompleted()
);
}
}
</syntaxhighlight>

== Repository Pattern ==
The repository pattern abstracts persistence logic and provides access to domain objects.

* '''Interface in the Domain Layer''':
** Define the contract for persistence using domain models.
<syntaxhighlight lang="java">
public interface TodoRepository {
void save(Todo todo);
Optional<Todo> findById(TodoId id);
List<Todo> findAll();
}
</syntaxhighlight>

* '''Implementation in the Infrastructure Layer''':
** Implement the repository interface using database-specific entities and persistence mechanisms.

== Mapping Between Domain Models and Database Entities ==
To keep the domain layer independent of persistence, map between domain models and database entities in the infrastructure layer.

* '''Domain Model''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

// Business logic
}
</syntaxhighlight>

* '''Database Entity''':
<syntaxhighlight lang="java">
@Entity
@Table(name = "todos")
public class TodoEntity {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

private String title;
private String description;
private boolean completed;

// Getters and setters
}
</syntaxhighlight>

== Best Practices ==
* Use '''domain models''' in the repository interface, not database entities.
* Keep the domain layer free from persistence concerns.
* Use mappers (manual or libraries like MapStruct) to convert between domain models and database entities.
* Avoid adding persistence-related methods (e.g., `save()`) to domain models.
* Use the '''Unit of Work''' or '''event-driven mechanisms''' for automatic persistence if needed.

== Summary ==
* The domain layer focuses on business logic and uses repositories to abstract persistence.
* The infrastructure layer handles persistence and maps between domain models and database entities.
* Keep the domain layer decoupled from technical concerns to ensure clean, maintainable, and testable code.

=FAQ =
== Difference between repository and persistence ==
The repository in the domain layer and the persistence layer in the infrastructure serve different purposes and are part of the separation of concerns in DDD.

* The repository in the domain layer is an abstraction (interface) that defines how the domain interacts with persistence.
* The persistence layer in the infrastructure is the implementation of that abstraction, handling the actual database operations.

== Should I use domain model or database entity in repository? ==
In the repository interface (defined in the domain layer), you should use domain models because the repository is part of the domain layer and should work with the core business concepts. However, in the repository implementation (in the infrastructure layer), you can map between domain models and database entities to handle persistence.

== Should I have a save() method in domain model ==

No, the domain model (Todo) should not have a save() method. In Domain-Driven Design (DDD), the domain model is responsible for encapsulating business logic and representing the core concepts of the domain. It should not be concerned with persistence or infrastructure details like saving to a database.

== Should I handle messages in repository? ==

Message brokers like Kafka, RabbitMQ, or others are not persistence mechanisms in the traditional sense but are instead used for communication and event-driven architectures. Therefore, creating a repository for a message broker is generally not recommended. Instead, you should handle message brokers in the application layer or infrastructure layer.

* Do not create a repository for message brokers like Kafka.
* Use the application layer to handle message publishing/consuming.
* Abstract the message broker interaction using interfaces and implement them in the infrastructure layer.
* Leverage domain events to integrate with message brokers in an event-driven architecture.

Whether you should create a repository for Redis depends on how you are using Redis in your application.

* Use a repository for Redis only if it is a primary data store for domain entities.
* For caching, use decorators or handle it in the infrastructure layer.
* For non-domain purposes (e.g., rate limiting, session storage), handle Redis interactions directly in the infrastructure or application layer.
* Always keep the domain layer free of Redis-specific logic to maintain separation of concerns.

== Do I need a service layer? ==
Whether you need a service layer depends on the complexity of your application and how you structure your code. In Domain-Driven Design (DDD), the service layer (often referred to as the application layer) plays an important role in coordinating use cases and workflows.

You might skip the service layer if:

* Your application is simple
* Your domain logic is self-contained

[[Category:DDD]]
[[Category:MicroService]]

文件:Ddd-dependency-rule.svg

2025-08-26T12:40:31Z

Riguz：

DDD guide

2025-08-26T12:40:19Z

Riguz：/* Layers in DDD */

= Domain-Driven Design (DDD) Guide =

This guide provides an overview of key concepts and best practices for implementing Domain-Driven Design (DDD), focusing on the separation of concerns between the domain model, repository, and persistence layer.

== Key Principles of DDD ==
* '''Focus on the Domain''':
** The domain model represents the core business logic and rules.
** It should be independent of technical concerns like persistence or frameworks.

* '''Separation of Concerns''':
** Divide responsibilities between the domain layer, application layer, and infrastructure layer.
** Keep the domain layer free from infrastructure dependencies.

* '''Ubiquitous Language''':
** Use a shared language between developers and domain experts to ensure clarity and alignment.

* '''Repository Pattern''':
** Use repositories to abstract persistence logic and provide access to domain objects.

== Layers in DDD ==
<ref> https://learn.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice</ref>

<syntaxhighlight lang="cpp">
com.example.todo
├── application
│ ├── service
│ └── dto
├── domain
│ ├── model
│ ├── repository
│ └── service
├── infrastructure
│ ├── persistence
│ ├── messaging
│ └── configuration
└── interface
├── controller
└── mapper
</syntaxhighlight>

Dependency rule:

[[Image:ddd-dependency-rule.svg|600px]]

=== Domain Layer ===
The domain layer contains the core business logic and domain models.

* '''Responsibilities''':
** Encapsulate business rules and behavior.
** Represent the core concepts of the domain.

* '''Key Components''':
** '''Entities''': Objects with a unique identity (e.g., `Todo`).
** '''Value Objects''': Immutable objects that represent a concept (e.g., `TodoId`).
** '''Aggregates''': A cluster of domain objects treated as a single unit.

* '''Best Practices''':
** Avoid adding persistence-related methods (e.g., `save()` or `delete()`) to domain models.
** Keep domain models focused on business logic.

* '''Example''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

public Todo(TodoId id, String title, String description) {
this.id = id;
this.title = title;
this.description = description;
this.completed = false;
}

public void markAsCompleted() {
this.completed = true;
}

// Getters and setters
}
</syntaxhighlight>

=== Application Layer ===
The application layer coordinates use cases and orchestrates interactions between the domain and infrastructure layers.

* '''Responsibilities''':
** Handle application-specific logic (e.g., workflows, use cases).
** Delegate persistence to repositories.

* '''Example''':
<syntaxhighlight lang="java">
public class TodoApplicationService {
private final TodoRepository todoRepository;

public TodoApplicationService(TodoRepository todoRepository) {
this.todoRepository = todoRepository;
}

public void createTodo(String title, String description) {
Todo todo = new Todo(new TodoId(UUID.randomUUID()), title, description);
todoRepository.save(todo);
}
}
</syntaxhighlight>

=== Infrastructure Layer ===
The infrastructure layer handles technical concerns like persistence, messaging, and external APIs.

* '''Responsibilities''':
** Implement repository interfaces defined in the domain layer.
** Map between domain models and database entities.

* '''Example''':
<syntaxhighlight lang="java">
@Repository
public class JpaTodoRepository implements TodoRepository {
private final SpringDataTodoEntityRepository entityRepository;

public JpaTodoRepository(SpringDataTodoEntityRepository entityRepository) {
this.entityRepository = entityRepository;
}

@Override
public void save(Todo todo) {
TodoEntity entity = mapToEntity(todo);
entityRepository.save(entity);
}

@Override
public Optional<Todo> findById(TodoId id) {
return entityRepository.findById(id.getValue())
.map(this::mapToDomain);
}

private TodoEntity mapToEntity(Todo todo) {
TodoEntity entity = new TodoEntity();
entity.setId(todo.getId().getValue());
entity.setTitle(todo.getTitle());
entity.setDescription(todo.getDescription());
entity.setCompleted(todo.isCompleted());
return entity;
}

private Todo mapToDomain(TodoEntity entity) {
return new Todo(
new TodoId(entity.getId()),
entity.getTitle(),
entity.getDescription(),
entity.isCompleted()
);
}
}
</syntaxhighlight>

== Repository Pattern ==
The repository pattern abstracts persistence logic and provides access to domain objects.

* '''Interface in the Domain Layer''':
** Define the contract for persistence using domain models.
<syntaxhighlight lang="java">
public interface TodoRepository {
void save(Todo todo);
Optional<Todo> findById(TodoId id);
List<Todo> findAll();
}
</syntaxhighlight>

* '''Implementation in the Infrastructure Layer''':
** Implement the repository interface using database-specific entities and persistence mechanisms.

== Mapping Between Domain Models and Database Entities ==
To keep the domain layer independent of persistence, map between domain models and database entities in the infrastructure layer.

* '''Domain Model''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

// Business logic
}
</syntaxhighlight>

* '''Database Entity''':
<syntaxhighlight lang="java">
@Entity
@Table(name = "todos")
public class TodoEntity {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

private String title;
private String description;
private boolean completed;

// Getters and setters
}
</syntaxhighlight>

== Best Practices ==
* Use '''domain models''' in the repository interface, not database entities.
* Keep the domain layer free from persistence concerns.
* Use mappers (manual or libraries like MapStruct) to convert between domain models and database entities.
* Avoid adding persistence-related methods (e.g., `save()`) to domain models.
* Use the '''Unit of Work''' or '''event-driven mechanisms''' for automatic persistence if needed.

== Summary ==
* The domain layer focuses on business logic and uses repositories to abstract persistence.
* The infrastructure layer handles persistence and maps between domain models and database entities.
* Keep the domain layer decoupled from technical concerns to ensure clean, maintainable, and testable code.

=FAQ =
== Difference between repository and persistence ==
The repository in the domain layer and the persistence layer in the infrastructure serve different purposes and are part of the separation of concerns in DDD.

* The repository in the domain layer is an abstraction (interface) that defines how the domain interacts with persistence.
* The persistence layer in the infrastructure is the implementation of that abstraction, handling the actual database operations.

== Should I use domain model or database entity in repository? ==
In the repository interface (defined in the domain layer), you should use domain models because the repository is part of the domain layer and should work with the core business concepts. However, in the repository implementation (in the infrastructure layer), you can map between domain models and database entities to handle persistence.

== Should I have a save() method in domain model ==

No, the domain model (Todo) should not have a save() method. In Domain-Driven Design (DDD), the domain model is responsible for encapsulating business logic and representing the core concepts of the domain. It should not be concerned with persistence or infrastructure details like saving to a database.

== Should I handle messages in repository? ==

Message brokers like Kafka, RabbitMQ, or others are not persistence mechanisms in the traditional sense but are instead used for communication and event-driven architectures. Therefore, creating a repository for a message broker is generally not recommended. Instead, you should handle message brokers in the application layer or infrastructure layer.

* Do not create a repository for message brokers like Kafka.
* Use the application layer to handle message publishing/consuming.
* Abstract the message broker interaction using interfaces and implement them in the infrastructure layer.
* Leverage domain events to integrate with message brokers in an event-driven architecture.

Whether you should create a repository for Redis depends on how you are using Redis in your application.

* Use a repository for Redis only if it is a primary data store for domain entities.
* For caching, use decorators or handle it in the infrastructure layer.
* For non-domain purposes (e.g., rate limiting, session storage), handle Redis interactions directly in the infrastructure or application layer.
* Always keep the domain layer free of Redis-specific logic to maintain separation of concerns.

== Do I need a service layer? ==
Whether you need a service layer depends on the complexity of your application and how you structure your code. In Domain-Driven Design (DDD), the service layer (often referred to as the application layer) plays an important role in coordinating use cases and workflows.

You might skip the service layer if:

* Your application is simple
* Your domain logic is self-contained

[[Category:DDD]]
[[Category:MicroService]]

DDD guide

2025-08-17T14:00:36Z

Riguz：/* Layers in DDD */

= Domain-Driven Design (DDD) Guide =

This guide provides an overview of key concepts and best practices for implementing Domain-Driven Design (DDD), focusing on the separation of concerns between the domain model, repository, and persistence layer.

== Key Principles of DDD ==
* '''Focus on the Domain''':
** The domain model represents the core business logic and rules.
** It should be independent of technical concerns like persistence or frameworks.

* '''Separation of Concerns''':
** Divide responsibilities between the domain layer, application layer, and infrastructure layer.
** Keep the domain layer free from infrastructure dependencies.

* '''Ubiquitous Language''':
** Use a shared language between developers and domain experts to ensure clarity and alignment.

* '''Repository Pattern''':
** Use repositories to abstract persistence logic and provide access to domain objects.

== Layers in DDD ==
<ref> https://learn.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/ddd-oriented-microservice</ref>

<syntaxhighlight lang="cpp">
com.example.todo
├── application
│ ├── service
│ └── dto
├── domain
│ ├── model
│ ├── repository
│ └── service
├── infrastructure
│ ├── persistence
│ ├── messaging
│ └── configuration
└── interface
├── controller
└── mapper
</syntaxhighlight>
=== Domain Layer ===
The domain layer contains the core business logic and domain models.

* '''Responsibilities''':
** Encapsulate business rules and behavior.
** Represent the core concepts of the domain.

* '''Key Components''':
** '''Entities''': Objects with a unique identity (e.g., `Todo`).
** '''Value Objects''': Immutable objects that represent a concept (e.g., `TodoId`).
** '''Aggregates''': A cluster of domain objects treated as a single unit.

* '''Best Practices''':
** Avoid adding persistence-related methods (e.g., `save()` or `delete()`) to domain models.
** Keep domain models focused on business logic.

* '''Example''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

public Todo(TodoId id, String title, String description) {
this.id = id;
this.title = title;
this.description = description;
this.completed = false;
}

public void markAsCompleted() {
this.completed = true;
}

// Getters and setters
}
</syntaxhighlight>

=== Application Layer ===
The application layer coordinates use cases and orchestrates interactions between the domain and infrastructure layers.

* '''Responsibilities''':
** Handle application-specific logic (e.g., workflows, use cases).
** Delegate persistence to repositories.

* '''Example''':
<syntaxhighlight lang="java">
public class TodoApplicationService {
private final TodoRepository todoRepository;

public TodoApplicationService(TodoRepository todoRepository) {
this.todoRepository = todoRepository;
}

public void createTodo(String title, String description) {
Todo todo = new Todo(new TodoId(UUID.randomUUID()), title, description);
todoRepository.save(todo);
}
}
</syntaxhighlight>

=== Infrastructure Layer ===
The infrastructure layer handles technical concerns like persistence, messaging, and external APIs.

* '''Responsibilities''':
** Implement repository interfaces defined in the domain layer.
** Map between domain models and database entities.

* '''Example''':
<syntaxhighlight lang="java">
@Repository
public class JpaTodoRepository implements TodoRepository {
private final SpringDataTodoEntityRepository entityRepository;

public JpaTodoRepository(SpringDataTodoEntityRepository entityRepository) {
this.entityRepository = entityRepository;
}

@Override
public void save(Todo todo) {
TodoEntity entity = mapToEntity(todo);
entityRepository.save(entity);
}

@Override
public Optional<Todo> findById(TodoId id) {
return entityRepository.findById(id.getValue())
.map(this::mapToDomain);
}

private TodoEntity mapToEntity(Todo todo) {
TodoEntity entity = new TodoEntity();
entity.setId(todo.getId().getValue());
entity.setTitle(todo.getTitle());
entity.setDescription(todo.getDescription());
entity.setCompleted(todo.isCompleted());
return entity;
}

private Todo mapToDomain(TodoEntity entity) {
return new Todo(
new TodoId(entity.getId()),
entity.getTitle(),
entity.getDescription(),
entity.isCompleted()
);
}
}
</syntaxhighlight>

== Repository Pattern ==
The repository pattern abstracts persistence logic and provides access to domain objects.

* '''Interface in the Domain Layer''':
** Define the contract for persistence using domain models.
<syntaxhighlight lang="java">
public interface TodoRepository {
void save(Todo todo);
Optional<Todo> findById(TodoId id);
List<Todo> findAll();
}
</syntaxhighlight>

* '''Implementation in the Infrastructure Layer''':
** Implement the repository interface using database-specific entities and persistence mechanisms.

== Mapping Between Domain Models and Database Entities ==
To keep the domain layer independent of persistence, map between domain models and database entities in the infrastructure layer.

* '''Domain Model''':
<syntaxhighlight lang="java">
public class Todo {
private TodoId id;
private String title;
private String description;
private boolean completed;

// Business logic
}
</syntaxhighlight>

* '''Database Entity''':
<syntaxhighlight lang="java">
@Entity
@Table(name = "todos")
public class TodoEntity {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;

private String title;
private String description;
private boolean completed;

// Getters and setters
}
</syntaxhighlight>

== Best Practices ==
* Use '''domain models''' in the repository interface, not database entities.
* Keep the domain layer free from persistence concerns.
* Use mappers (manual or libraries like MapStruct) to convert between domain models and database entities.
* Avoid adding persistence-related methods (e.g., `save()`) to domain models.
* Use the '''Unit of Work''' or '''event-driven mechanisms''' for automatic persistence if needed.

== Summary ==
* The domain layer focuses on business logic and uses repositories to abstract persistence.
* The infrastructure layer handles persistence and maps between domain models and database entities.
* Keep the domain layer decoupled from technical concerns to ensure clean, maintainable, and testable code.

=FAQ =
== Difference between repository and persistence ==
The repository in the domain layer and the persistence layer in the infrastructure serve different purposes and are part of the separation of concerns in DDD.

* The repository in the domain layer is an abstraction (interface) that defines how the domain interacts with persistence.
* The persistence layer in the infrastructure is the implementation of that abstraction, handling the actual database operations.

== Should I use domain model or database entity in repository? ==
In the repository interface (defined in the domain layer), you should use domain models because the repository is part of the domain layer and should work with the core business concepts. However, in the repository implementation (in the infrastructure layer), you can map between domain models and database entities to handle persistence.

== Should I have a save() method in domain model ==

No, the domain model (Todo) should not have a save() method. In Domain-Driven Design (DDD), the domain model is responsible for encapsulating business logic and representing the core concepts of the domain. It should not be concerned with persistence or infrastructure details like saving to a database.

== Should I handle messages in repository? ==

Message brokers like Kafka, RabbitMQ, or others are not persistence mechanisms in the traditional sense but are instead used for communication and event-driven architectures. Therefore, creating a repository for a message broker is generally not recommended. Instead, you should handle message brokers in the application layer or infrastructure layer.

* Do not create a repository for message brokers like Kafka.
* Use the application layer to handle message publishing/consuming.
* Abstract the message broker interaction using interfaces and implement them in the infrastructure layer.
* Leverage domain events to integrate with message brokers in an event-driven architecture.

Whether you should create a repository for Redis depends on how you are using Redis in your application.

* Use a repository for Redis only if it is a primary data store for domain entities.
* For caching, use decorators or handle it in the infrastructure layer.
* For non-domain purposes (e.g., rate limiting, session storage), handle Redis interactions directly in the infrastructure or application layer.
* Always keep the domain layer free of Redis-specific logic to maintain separation of concerns.

== Do I need a service layer? ==
Whether you need a service layer depends on the complexity of your application and how you structure your code. In Domain-Driven Design (DDD), the service layer (often referred to as the application layer) plays an important role in coordinating use cases and workflows.

You might skip the service layer if:

* Your application is simple
* Your domain logic is self-contained

[[Category:DDD]]
[[Category:MicroService]]

Ystack

2025-08-17T13:45:06Z

Riguz：

= Services and responsibilities =
== Auth / Identity (Keycloak) ==
* Responsibility: Authentication, user identity, SSO, OIDC tokens.
* Data owned: Keycloak user record (sub), basic profile attributes.
* Notes: Other services store keycloak_id as foreign reference only.

== Customer Service (customer profile / account)==

* Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records.
* Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata).
* API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders.
* When to call: read-heavy for CRM and billing, write when profile changes.

== Product / Plan (Catalog) Service ==

* Responsibility: define and manage plans, price points, features, trial configuration, promotions/coupons, entitlements (features JSON).
* Data owned: plans, SKUs, pricing tiers, feature flags, metadata.
* Notes: Admin interfaces to create/retire plans; this is authoritative for what users can buy.

== Order / Checkout Service ==

* Responsibility: orchestrate purchase flows and create “orders” as transient/immutable records that represent a purchase attempt. Validate requested plan, pricing, coupons, compute totals and taxes, create provider checkout session or payment intent.
* Data owned: orders (order_id, customer_id, plan_id, price_at_purchase, status: created/processing/succeeded/failed/expired, idempotency key).
* Notes: Produces events (OrderCreated, OrderSucceeded, OrderFailed) consumed by Billing/Subscription and Customer services. Should be idempotent (use idempotency key).

== Subscription / Billing Service ==

* Responsibility: map orders into subscriptions, maintain subscription lifecycle (trialing, active, past_due, canceled), reconcile provider subscription state with local state, schedule renewals and billing windows, track current_period_start/end, cancel_at_period_end flags.
* Data owned: subscriptions table, subscription status history, subscription invoices (link to invoices table).
* Notes: Acts on provider webhooks and Order events to create/update local subscription rows.

== Payment Gateway Adapter ==
* Responsibility: encapsulate provider SDKs (Stripe, Paddle, etc.), create customers, payment methods, checkout sessions, subscriptions, invoices; normalize webhook payloads and verify signatures.
* Data owned: none (keeps provider ids for mapping).
* Notes: Keep this pluggable; return normalized result objects and propagate provider ids back to Order/Billing/Customer services.

== Invoice & Payments Service (or module inside Billing) ==

* Responsibility: store invoices and payments, record payment attempts, refunds, reconciliation with provider invoices, retention of raw payloads for audits.
* Data owned: invoices, payments, receipts.
* Notes: Expose APIs to query invoices and download receipts.

== Usage / Metering Service (optional, for metered billing) ==

* Responsibility: record per-feature usage (tokens, API calls), aggregate usage for billing periods, report usage to provider or generate usage-based invoices.
* Data owned: usage_records, aggregates.
* Notes: Support batching and idempotency (external_id) to avoid double-counting.

[[Category:Ystack]]
[[Category:DDD]]
[[Category:Distributed]]

Ystack

2025-08-17T13:41:19Z

Riguz：

Ystack

2025-08-17T13:41:08Z

Riguz：

= Services and responsibilities
== Auth / Identity (Keycloak) ==
* Responsibility: Authentication, user identity, SSO, OIDC tokens.
* Data owned: Keycloak user record (sub), basic profile attributes.
* Notes: Other services store keycloak_id as foreign reference only.

== Customer Service (customer profile / account)==
* Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records.
* Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata).
* API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders.
* When to call: read-heavy for CRM and billing, write when profile changes.

[[Category:Ystack]]
[[Category:DDD]]
[[Category:Distributed]]

Ystack

2025-08-17T13:40:53Z

Riguz：创建页面，内容为“ = Services and responsibilities == Auth / Identity (Keycloak) == Responsibility: Authentication, user identity, SSO, OIDC tokens. Data owned: Keycloak user record (sub), basic profile attributes. Notes: Other services store keycloak_id as foreign reference only. == Customer Service (customer profile / account)== Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId…”

= Services and responsibilities
== Auth / Identity (Keycloak) ==
Responsibility: Authentication, user identity, SSO, OIDC tokens.
Data owned: Keycloak user record (sub), basic profile attributes.
Notes: Other services store keycloak_id as foreign reference only.

== Customer Service (customer profile / account)==
Responsibility: canonical customer profile (name, emails, billing address, company, contact info), payment-customer mapping (e.g., providerCustomerId), invoice delivery preferences, links to internal user records.
Data owned: customer table (customer_id, keycloak_id, contact info, provider customer id, metadata).
API examples: GET/PUT customer, attach payment method token, list customer’s subscriptions/orders.
When to call: read-heavy for CRM and billing, write when profile changes.

[[Category:Ystack]]
[[Category:DDD]]
[[Category:Distributed]]