Compare commits

...
67 Commits
Author SHA1 Message Date
qwqcode 3e45bb9506 chore(landing): improve landing page and docs 2025-02-02 16:26:20 +08:00
qwqcode 64a2adbe1a chore(ci): revise github dependabot for checking ui deps 2024-12-13 13:12:38 +08:00
qwqcode 99736db27f chore(style): fix bg color of login dialog in sidebar for dark mode 2024-11-25 00:00:51 +08:00
qwqcode eb3310c537 chore(ci): tidy up frontend build shell scripts 2024-11-24 23:53:20 +08:00
duli ab2c2cf153 chore(ci): include artalk_ui_nightly.tar.gz in nightly release (#1027) 2024-11-23 21:34:49 +08:00
qwqcode 71b73a323a chore(docs/landing): fix tech icons in landing page 2024-11-06 22:22:23 +08:00
qwqcode 659023988e docs(landing): redesign landing page (#1020) 2024-11-06 21:53:23 +08:00
qwqcode c2b9afa1a1 feat(plugins): add plugin registry fetch script
- Introduce `fetch-registry.mjs` to download `registry.json` from `ArtalkJS/Community` repo for the latest release
- Update `build:docs` script to include registry fetch
2024-10-22 11:23:35 +08:00
qwqcode 258dfde60e docs: integrate git changelog plugin 2024-10-19 16:32:34 +08:00
qwqcode 91ac907778 chore(ui/deps): upgrade deps for ui 2024-10-19 16:25:48 +08:00
qwqcode 73da8740ee chore(docs): add frontend typedoc 2024-10-19 14:34:01 +08:00
qwqcode 4ad0cc1366 chore(i18n): update terminology for clarity
- Change 'Frontend' to 'Client'
- Change 'Backend' to 'Server'
2024-10-19 14:09:59 +08:00
Lance.Moe 15f2fb82a3 chore(docs): corrected react usage example (#1012) 2024-10-19 13:11:29 +08:00
qwqcode bd81b7c10c feat(ui/conf): add preferRemoteConf option (#1000) (#1011)
Add `preferRemoteConf` option (disabled by default).

Local config now takes priority, addressing the issue where remote config previously overrode local settings. (Closes #1000)

Updated config merging logic in `mount.ts`.

Deprecated `useBackendConf` in favor of `preferRemoteConf`.

(The prerequisite PR is #1007)

BREAKING CHANGE: UI client now prioritizes local config in the latest version, whereas previously, the remote config would override it. (See #1011)
2024-10-18 21:46:49 +08:00
qwqcode f6c99e949b feat(ui/eslint): update eslint-plugin-artalk to v1.0.2 (#1010)
- Add new ESLint rules for ArtalkPlugin:
  - Available rules: `noCycleDeps`, `noLifeCycleEventInNestedBlocks`, `noEventInWatchConf`, `noInjectInNestedBlocks`, `noInjectOutsidePlugin`, `onePluginPerFile`. For more details, see [eslint-plugin-artalk](https://github.com/ArtalkJS/Artalk/tree/master/ui/eslint-plugin-artalk).
- Add tests for the new ESLint rules.
- Implement Tarjan's algorithm for detecting SCCs in the `noCycleDeps` rule.
- Improve code organization and maintainability.
- Disable the 'import-x/namespace' rule for better performance. (https://github.com/import-js/eslint-plugin-import/issues/2340)
2024-10-18 19:43:01 +08:00
qwqcode dcde53f8ad refactor(ui/auth): ensure compatibility with new client types (#1009)
- Bump to new Artalk client export types
- Add `AuthContext` type definition for improved clarity
- Replace `ContextApi` with `AuthContext` for reducing the scope of variables
- Bump version to 0.0.2 for release

(The prerequisite PR is #1007)
2024-10-18 17:09:15 +08:00
qwqcode d3aacf0d14 refactor(ui/sidebar): ensure compatibility with new client types (#1008)
Since the client program already prioritizes local configuration over remote configuration by default, there's no need to use the `remoteConfModifier` magic function to alter the configuration priority.

The dependency injection function has changed from `get` to `inject`, or call a more specific method from the `Context` interface.

(The prerequisite PR is #1007)
2024-10-18 16:48:41 +08:00
qwqcode 20be96f6f8 refactor(ui): improve modularity, lifecycle, and types (#1007)
- Introduce a service dependency container for better management (#1006).
  - Replace original `services` definitions with `provide` and `inject` methods.
  - Recommend calling `inject` at the beginning of `ArtalkPlugin` to explicitly inject required dependencies.
- Replace `load` with `mount` for improved lifecycle handling.
  - Track local config.
  - Fix potential language setting not working issue. (Fixes #973)
- Refine Type definitions for clarity and maintainability.
  - See [TypeDoc](https://artalk.js.org/typedoc/) for updates.
- Enhance config logic with `ConfigManager`.
  - Deprecate `ctx.conf` and `ctx.$root`; use `getConf()` and `getEl()` instead.
  - Update client default config settings. (Fixes #1001)
- Improve event handling with `EventManager` refactor.
- Update plugin and editor architecture for greater flexibility.
  - Further eliminate global variables and avoid directly passing the `Context` interface as a function parameter. Instead, use more explicit and specific types and parameters.
- Remove deprecated and redundant code for a cleaner structure.

BREAKING CHANGE: This update changes the UI client's export Types. Although we aim to maintain backward compatibility, it may still affect downstream UI programs. Please refer to the [TypeDoc](https://artalk.js.org/typedoc/).
2024-10-18 16:40:18 +08:00
qwqcode 437892cdfa feat(ui): add dependency injection container (#1006)
- Implement `createInjectionContainer` for managing service lifecycles
- Implement `provide` and `inject` for dependency injection
- Support singleton and transient service lifecycles
- Add unit tests for container functionality
2024-10-17 22:53:25 +08:00
qwqcode 5065bb4763 chore: update CONTRIBUTING.md 2024-10-11 13:31:20 +08:00
Limeandqwqcode baa63866f4 feat(ui/page_vote): add page voting feature (#983)
* feat(plugin/page_vote): add `page_vote` plugin

* feat(plugin/page_vote): update vote count text

adjust code structure
disable `page vote` plugin by default

* feat(plugin/page_vote): reuse actions btn style

* perf(plugin/page-vote): make type strong

* feat: watch `darkMode` conf

* doc(plugin/page_vote): add config doc

* feat(ui/page_vote): add page voting feature

- Introduce page voting functionality
- Update configuration to enable/disable page voting
- Retrieve html elements for voting buttons and counts
- Enhance customization options for voting elements
- Reference: #983, #998, #997

---------

Co-authored-by: qwqcode <qwqcode@gmail.com>
2024-10-08 12:38:39 +08:00
qwqcode 7c251fd067 feat(api/vote): add get vote status endpoint (#998)
A new HTTP API endpoint `GET /votes/:target_name/:target_id` is now available. (See https://artalk.js.org/http-api.html#tag/Vote/operation/GetVote)

- Implement GET endpoint for retrieving vote status
- Add tests for vote functionality

Related to: #997

This is a prerequisite PR for #983.
2024-10-06 22:31:59 +08:00
qwqcode 02a369fe5c refactor(api/vote): refactor vote http endpoint and logic (#997)
The original `POST /votes/:type/:target_id` endpoint for creating votes has been updated to `POST /votes/:target_name/:target_id/:choice`. The `target_name` can be either `comment` or `page`, the `target_id` is a numeric value, and the `choice` can be `up` or `down`. (https://artalk.js.org/http-api.html#tag/Vote/operation/CreateVote)

The HTTP response now includes two additional fields: `is_up` and `is_down`, which indicate the user's current voting state. The `up` and `down` fields remain unchanged and continue to be of numeric type, ensuring backward compatibility with existing clients.

- Change vote endpoint to include `{target_name}` and `{choice}`
- Update vote logic to handle `up` and `down` choices
- Modify request data models and API interfaces for new vote structure
- Ensure backward compatibility with existing vote response data
- Improve vote handling and response structure

BREAKING CHANGE: Vote HTTP API endpoint have been updated. (See #997)
2024-10-06 22:15:15 +08:00
qwqcode bd0db8cd57 chore(docs): revise ui config docs 2024-10-06 21:45:01 +08:00
qwqcode 206a26d0c1 feat(ui): add npm published version check script
- Introduce check:publish script to verify npm versions
- Ensure all projects have the latest versions on npm
- Skip private packages during version checks
- Allow filtering by specific project name with -F option
2024-10-05 21:13:02 +08:00
qwqcode f1ae566134 refactor(ui/conf): introduce DeepPartial type for ui config (#996)
- Replace `Partial<ArtalkConfig>` with `ArtalkConfigPartial` for better type clarity.
- Introduce `DeepPartial` type for nested partial configurations.
- Update default configuration handling to use `RequiredExcept` and `FunctionKeys`.
- Adjust related functions and interfaces to use `ArtalkConfigPartial`.
2024-10-05 20:33:06 +08:00
qwqcode 3571a18b42 refactor(ui/comment): update reply button to use component
- Replaced manual reply button creation with ActionBtn component for consistency
- Moved styling from comment.scss to main.scss for common action button styles
2024-10-05 19:36:49 +08:00
qwqcode abac3f0f36 feat(ui/eslint): add eslint plugin for artalk ui development (#995)
- Implemented `eslint-plugin-artalk` to enforce Artalk's development conventions.
- Added setup script for UI development environment.
- Created test cases for Artalk plugin rules.
- Configured TypeScript and build settings for the plugin.
- Updated documentation with installation and configuration instructions.
2024-10-05 19:19:22 +08:00
qwqcode db960aa024 chore(deps): upgrade go deps 2024-10-04 00:31:31 +08:00
qwqcode 1b5ef279bb chore(ci/tests): fix branch filters and improve caching 2024-10-04 00:31:03 +08:00
qwqcode 754223571a chore(ci/tests): switch tests from circle ci to github actions 2024-10-03 23:02:50 +08:00
qwqcode a6eba361fc chore(ci): update branch ignore patterns on circle ci 2024-10-03 21:34:24 +08:00
qwqcode 1d5811a59c feat(config): enhance config file and data dir retrieval (#992)
* feat(config): enhance config file and data dir retrieval

- Add xdg package for XDG base directory support
- Update RetrieveConfigFile to search in XDG_CONFIG_HOME and /etc
- Add RetrieveDataDir to find data directory in XDG_DATA_HOME and /var/lib
- Improve comments for better understanding of search order

* add unit tests
2024-10-03 15:04:42 +08:00
qwqcode ea9c5d9ecb chore(docs): add install guide for fedora linux distro 2024-10-01 14:47:20 +08:00
qwqcode 8707f4f327 docs(landing): add more translations 2024-09-20 21:03:56 +08:00
qwqcode b89a1866f9 docs(i18n): add zh-TW translation for config template 2024-09-20 21:03:12 +08:00
qwqcode 7e082158cd chore(docs): add go reference badge in README.md 2024-09-19 21:41:48 +08:00
qwqcode d5d458de11 docs(landing): optimize responsive font size 2024-09-19 21:17:38 +08:00
qwqcode c087400a66 chore(docs): set up redirects for old pages 2024-09-19 21:14:07 +08:00
qwqcode 34d793697c chore(docs): refine deployment documentation 2024-09-19 18:27:24 +08:00
github-actions[bot] b9c3b2a1c3 chore: release v2.9.1 (#981)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
2024-09-18 23:50:46 +08:00
qwqcode bd121f8f94 docs: refine deployment documentation 2024-09-18 23:47:35 +08:00
qwqcode 6b0e46c86c refactor(go): hardcode version and get commit_hash via runtime/debug 2024-09-18 22:01:21 +08:00
qwqcode 53aaf27fdf chore(deps): upgrade frontend deps 2024-09-18 21:56:38 +08:00
qwqcode a3d1ccc773 feat(go): upgrade golang to v1.22.7 and some deps 2024-09-18 21:56:38 +08:00
qwqcode cf7725edba refactor(go): bump the module version and support go install (#979)
BREAKING CHANGE: The original Go module name was `github.com/ArtalkJS/Artalk`, which has now been modified to `github.com/artalkjs/artalk/v2` (all lowercase). This change may affect the CI pipeline or other areas if you are compiling the Artalk server and have specified the fixed Go module name. Regarding the original `-ldflags -X github.com/ArtalkJS/Artalk/internal/config.Version` and `CommitHash` definitions, please remove them, as they are now obsolete. The `Version` has been hardcoded into the Go code, and the `CommitHash` is now read from the Go build info via runtime/debug’s vcs.revision value. This change only affects the server developers and does not impact the frontend UI client.
2024-09-18 21:43:43 +08:00
qwqcode 9cc3252c0f chore(docs): add support for auto-redirect to language-specific docs 2024-09-18 12:51:17 +08:00
qwqcode 349eb6f5c5 chore(docs): update the Chinese slogan on the homepage 2024-09-17 23:35:05 +08:00
qwqcode 55a96f12aa chore(docs): make English the default readme 2024-09-17 22:34:09 +08:00
qwqcode 36580b5fc3 chore(docs): apply artalk locale from html lang 2024-09-17 21:46:14 +08:00
qwqcode 9afa7ca555 docs(i18n): add English translations for docs (#978)
* docs: add support for multiple languages

* docs(i18n): add English translations
2024-09-17 21:19:48 +08:00
qwqcode 6d54b721da docs(landing): add multi-language and dark-mode for landing 2024-09-17 17:48:05 +08:00
qwqcode cb4596d59d docs(landing): add demo video in landing page 2024-09-17 17:44:17 +08:00
qwqcode 4913e1aebd chore(docs): update extras.md 2024-09-17 17:41:27 +08:00
qwqcode 7ffaa04541 perf(plugin_katex): add error message for missing katex deps 2024-09-17 17:41:24 +08:00
qwqcode 2a49c0e515 fix(ui/plugin): prevent exceptions from blocking other plugins loading 2024-09-17 17:35:36 +08:00
qwqcode a98a50abbe test(mutex): add tests for keyed mutex 2024-09-16 16:55:38 +08:00
qwqcode 4bd3537c0d fix(test): separate test db to isolate concurrent test instances (#975) 2024-09-16 16:46:38 +08:00
qwqcode 9dcfd9cd91 chore(deps): upgrade deps 2024-09-15 09:52:26 +08:00
qwqcode 9fde40d843 chore(ci): improve golang build workflow on circle ci 2024-09-04 21:23:23 +08:00
qwqcode 19c3317f64 refactor(dao): improve concurrent testing for FindCreateAction function 2024-09-04 21:17:53 +08:00
qwqcode 22ff47f9ce fix(transfer): ensure consistent time format in artrans export 2024-09-04 21:14:46 +08:00
qwqcode 4eb3dbaca2 fix(db): sql error with custom table prefix (#970) 2024-09-04 21:00:13 +08:00
qwqcode 90d8503d0e chore(docs): update cases.md 2024-09-04 11:42:47 +08:00
qwqcode 2354f7aa06 chore: update README.md 2024-09-04 11:20:57 +08:00
qwqcode 7bab69c4fd chore(docs): update artalk plugin for docs 2024-09-03 22:45:02 +08:00
qwqcode 301928da4b chore(build): fix build for plugin-lightbox 2024-09-03 22:17:34 +08:00
647 changed files with 20345 additions and 7093 deletions

No files matched your search

-79
View File
@@ -1,79 +0,0 @@
version: 2.1
orbs:
node: circleci/node@5.2.0
codecov: codecov/codecov@3.3.0
executors:
base:
docker:
- image: cimg/base:stable
node:
docker:
- image: "cimg/node:20.17.0"
go:
docker:
- image: cimg/go:1.22.6
parameters:
trigger-app:
type: boolean
default: false
run-them-all:
type: boolean
default: false
jobs:
## Backend
test_app:
executor: go
working_directory: ~/go/src/github.com/ArtalkJS/Artalk
environment:
GO111MODULE: "on"
steps:
- checkout
- run:
name: "Print the Go version"
command: >
go version
- restore_cache:
keys:
- go-mod-1.22.6-{{ checksum "go.sum" }}
- run:
name: Install Dependencies
command: go mod download
- save_cache:
key: go-mod-1.22.6-{{ checksum "go.sum" }}
paths:
- "~/go/pkg/mod"
- run:
name: Run tests
command: |
mkdir -p /tmp/test-reports
gotestsum --junitfile /tmp/test-reports/unit-tests.xml -- -coverprofile=/tmp/test-reports/coverage.out ./...
- store_test_results:
path: /tmp/test-reports
- codecov/upload:
flags: go
file: /tmp/test-reports/coverage.out
all_projects:
executor: base
steps:
- run:
command: |
echo "all"
workflows:
build-app:
when:
or:
- << pipeline.parameters.trigger-app >>
- << pipeline.parameters.run-them-all >>
jobs:
- test_app
build-shared-other:
when: << pipeline.parameters.run-them-all >>
jobs:
- all_projects
-27
View File
@@ -1,27 +0,0 @@
# https://circleci.com/docs/2.0/configuration-reference
version: 2.1
# this allows you to use CircleCI's dynamic configuration
# https://circleci.com/docs/2.0/dynamic-config/
setup: true
# the path-filtering orb is required to continue a pipeline based on
# https://circleci.com/developer/orbs/orb/circleci/path-filtering
orbs:
path-filtering: circleci/path-filtering@1.0.0
workflows:
setup:
jobs:
- path-filtering/filter:
mapping: |
(cmd|internal|server|pkg|test|conf)/.* trigger-app true
main.go|go.mod|go.sum trigger-app true
base-revision: master # git branch name
config-path: .circleci/conditional_config.yml
filters:
branches:
ignore:
- gh-pages
- /release\/.+/
- nightly
+3
View File
@@ -13,6 +13,7 @@ options:
- fix
- perf
- refactor
- test
- docs
commit_groups:
sort_by: Custom
@@ -21,12 +22,14 @@ options:
- fix
- perf
- refactor
- test
- docs
title_maps:
feat: Features
fix: Bug Fixes
perf: Performance Improvements
refactor: Code Refactoring
test: Testing
docs: Documentation
header:
pattern: "^(\\w*)(?:\\(([\\w\\$\\.\\-\\*\\s\\/]*)\\))?\\:\\s(.*)$"
+4 -13
View File
@@ -18,7 +18,9 @@ updates:
open-pull-requests-limit: 15
- package-ecosystem: npm
directory: /ui
# setup only for whole workspace to fix issues with package.lock,
# SEE https://github.com/dependabot/dependabot-core/issues/4993#issuecomment-1739296001
directory: /
schedule:
interval: monthly
commit-message:
@@ -29,18 +31,7 @@ updates:
dev-deps:
dependency-type: development
open-pull-requests-limit: 15
- package-ecosystem: npm
directory: /docs
schedule:
interval: monthly
commit-message:
prefix: "chore(deps/docs): "
groups:
deps:
patterns:
- "*"
open-pull-requests-limit: 15
versioning-strategy: increase
- package-ecosystem: docker
directory: /
+3 -5
View File
@@ -11,8 +11,7 @@ on:
type: boolean
env:
GO_VERSION: 1.22.6
PKG_NAME: github.com/ArtalkJS/Artalk
GO_VERSION: 1.22.7
DOCKER_IMG: ghcr.io/goreleaser/goreleaser-cross
CACHE_DIR: /tmp/cache/docker-image
@@ -78,9 +77,8 @@ jobs:
--privileged \
-v /var/run/docker.sock:/var/run/docker.sock \
-v $(pwd)/sysroot:/sysroot \
-v $(pwd):/go/src/${PKG_NAME} \
-w /go/src/${PKG_NAME} \
-e CGO_ENABLED=1 \
-v $(pwd):/repo \
-w /repo \
--env-file local/.release-env \
ghcr.io/goreleaser/goreleaser-cross:v${GO_VERSION} \
release --release-notes local/release-notes.md ${{ inputs.dry_run && '--skip=publish' || '' }}
+8 -16
View File
@@ -52,7 +52,7 @@ jobs:
- name: Setup pnpm
uses: pnpm/action-setup@v4
with:
version: 9.9.0
version: 9.10.0
- name: Setup node
uses: actions/setup-node@v4
@@ -78,21 +78,12 @@ jobs:
run: pnpm install --frozen-lockfile
- name: Build UI
id: build_ui
run: |
make build-frontend
echo "ui_tarball=$(make -s pack-frontend)" >> $GITHUB_OUTPUT
- name: Pack UI
id: pack
run: |
SRC_FILE=$(pnpm pack -C ui/artalk --pack-destination ../.. | tail -n 1)
mkdir -p bin
PKG_FILE="bin/artalk_frontend_nigthly_$(date +'%Y%m%d').tar.gz"
mv $SRC_FILE $PKG_FILE
echo "pkg_file=$PKG_FILE" >> $GITHUB_OUTPUT
- name: Upload UI
- name: Upload UI dist
uses: actions/upload-artifact@v4
with:
name: ui-src
@@ -102,11 +93,12 @@ jobs:
if-no-files-found: error
retention-days: 1
- name: Upload UI package
- name: Upload UI tarball (included in release)
uses: actions/upload-artifact@v4
with:
name: build-ui-pkg
path: ${{ steps.pack.outputs.pkg_file }}
name: build-ui-tarball
path: ${{ steps.build_ui.outputs.ui_tarball }}
if-no-files-found: error
retention-days: 1
#
+1 -1
View File
@@ -23,7 +23,7 @@ jobs:
- name: Use pnpm
uses: pnpm/action-setup@v4
with:
version: 9.9.0
version: 9.10.0
- name: Setup node
uses: actions/setup-node@v4
+1 -1
View File
@@ -16,7 +16,7 @@ jobs:
- name: Use pnpm
uses: pnpm/action-setup@v4
with:
version: 9.9.0
version: 9.10.0
- name: Setup node
uses: actions/setup-node@v4
+4 -1
View File
@@ -68,7 +68,10 @@ jobs:
changelog=$(git-chglog --config .github/chglog/config.yml --next-tag "${VERSION}" "${VERSION}")
echo -e "${changelog}\n" | cat - CHANGELOG.md > temp && mv temp CHANGELOG.md
# modify the version of `package.json`
# modify the version for `internal/config/version.go`
perl -i -pe 's/const Version = ".*?"/const Version = "'${VERSION}'"/g' internal/config/version.go
# modify the version for `package.json`
perl -i -pe 's/"version": ".*?"/"version": "'${VERSION#v}'"/g' ui/artalk/package.json
# modify the version in docs
+72
View File
@@ -0,0 +1,72 @@
name: Test App
on:
push:
paths: ["cmd/**", "internal/**", "server/**", "test/**", "main.go", "go.mod", "go.sum"]
branches-ignore: ["release/*", "nightly"]
tags-ignore: ["v*"]
pull_request:
paths: ["cmd/**", "internal/**", "server/**", "test/**", "main.go", "go.mod", "go.sum"]
branches-ignore: ["release/*", "nightly"]
env:
REPORT_DIR: "/tmp/test-reports"
jobs:
test_app:
name: Test Go on ${{ matrix.os }}
runs-on: ${{ matrix.os }}
strategy:
fail-fast: false
matrix:
os: [ubuntu-latest, macos-latest]
steps:
- uses: actions/checkout@v4
- name: Setup Go
uses: actions/setup-go@v5
with:
go-version-file: go.mod
cache: false # https://github.com/actions/setup-go/issues/483
- id: go-vars
name: Get Go variables for cache
run: |
echo "GOCACHE=$(go env GOCACHE)" >> "$GITHUB_OUTPUT"
echo "GOMODCACHE=$(go env GOMODCACHE)" >> "$GITHUB_OUTPUT"
- name: Cache go modules
uses: actions/cache@v4
with:
path: |
${{ steps.go-vars.outputs.GOCACHE }}
${{ steps.go-vars.outputs.GOMODCACHE }}
key: go-test-${{ runner.os }}-${{ hashFiles('**/go.mod') }}
restore-keys: |
go-test-${{ runner.os }}
- name: Install tools
run: go install gotest.tools/gotestsum@latest
- name: Download Go modules
run: go mod download
- name: Run tests
run: |
mkdir -p $REPORT_DIR
gotestsum --junitfile $REPORT_DIR/unit-tests.xml --jsonfile $REPORT_DIR/unit-tests.json -- -coverprofile=$REPORT_DIR/coverage.out ./...
- name: Upload test results
uses: actions/upload-artifact@v4
with:
name: Go-Test-Results-${{ runner.os }}
path: ${{ env.REPORT_DIR }}
- if: matrix.os == 'ubuntu-latest'
name: Upload coverage to Codecov
uses: codecov/codecov-action@v4
with:
flags: go
file: ${{ env.REPORT_DIR }}/coverage.out
token: ${{ secrets.CODECOV_TOKEN }}
+3 -3
View File
@@ -2,12 +2,12 @@ name: Test Docs
on:
push:
branches: ["*", "!release/*", "!nightly"]
paths: ["docs/**"]
branches-ignore: ["release/*", "nightly"]
tags-ignore: ["v*"]
pull_request:
paths: ["docs/**"]
branches: ["*", "!release/*", "!nightly"]
branches-ignore: ["release/*", "nightly"]
jobs:
test_docs:
@@ -20,7 +20,7 @@ jobs:
- name: Use pnpm
uses: pnpm/action-setup@v4
with:
version: 9.9.0
version: 9.10.0
- name: Use Node.js
uses: actions/setup-node@v4
+8 -4
View File
@@ -2,16 +2,17 @@ name: Test Frontend
on:
push:
branches: ["*", "!release/*", "!nightly"]
paths: ["ui/**"]
branches-ignore: ["release/*", "nightly"]
tags-ignore: ["v*"]
pull_request:
paths: ["ui/**"]
branches: ["*", "!release/*", "!nightly"]
branches-ignore: ["release/*", "nightly"]
jobs:
test_ui:
strategy:
fail-fast: false
matrix:
node: [18, 20]
os: [ubuntu-latest, windows-latest]
@@ -30,7 +31,7 @@ jobs:
- uses: pnpm/action-setup@v4
with:
version: 9.9.0
version: 9.10.0
- name: Use Node.js ${{ matrix.node }}
uses: actions/setup-node@v4
@@ -44,9 +45,12 @@ jobs:
- name: Package Build Test
run: pnpm build:all
- name: Unit test
- name: Unit Test
run: pnpm test
- name: Plugins Build Test
run: pnpm build:plugins
- name: Lint
run: pnpm eslint ui && pnpm prettier --check ui
+1
View File
@@ -49,6 +49,7 @@ yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*
__debug*
vite.config.ts.timestamp-*
# frontend
node_modules
+1 -2
View File
@@ -17,6 +17,7 @@ before:
# install dependencies
- make install
- make build-frontend
- make pack-frontend
# build multi-platform
builds:
@@ -36,8 +37,6 @@ builds:
binary: "{{.ProjectName}}"
main: ./main.go
ldflags: &common_ldflags |
-X github.com/ArtalkJS/Artalk/internal/config.Version={{.Version}}
-X github.com/ArtalkJS/Artalk/internal/config.CommitHash={{ .ShortCommit }}
-s -w
# Linux (arm_64)
+4 -1
View File
@@ -9,10 +9,13 @@ pnpm-lock.yaml
**/auto-imports.d.ts
**/components.d.ts
**/typed-router.d.ts
**/vite.config.ts.timestamp-*
ui/artalk/src/api/v2.ts
docs/swagger/swagger.json
docs/swagger/swagger.yaml
docs/**
docs/docs/**/*.md
docs/docs/.vitepress/dist/**
docs/docs/.vitepress/cache/**
ui/artalk-sidebar/src/lib/md5.js
ui/artalk/src/lib/detect.ts
**/dist/**
+40
View File
@@ -1,4 +1,44 @@
## [v2.9.1](https://github.com/ArtalkJS/Artalk/compare/v2.9.0...v2.9.1) (2024-09-18)
### Features
* **go:** upgrade golang to v1.22.7 and some deps
### Bug Fixes
* **db:** sql error with custom table prefix ([#970](https://github.com/ArtalkJS/Artalk/issues/970))
* **test:** separate test db to isolate concurrent test instances ([#975](https://github.com/ArtalkJS/Artalk/issues/975))
* **transfer:** ensure consistent time format in artrans export
* **ui/plugin:** prevent exceptions from blocking other plugins loading
### Performance Improvements
* **plugin_katex:** add error message for missing katex deps
### Code Refactoring
* **dao:** improve concurrent testing for `FindCreateAction` function
* **go:** hardcode version and get commit_hash via runtime/debug
* **go:** bump the module version and support go install ([#979](https://github.com/ArtalkJS/Artalk/issues/979))
### Testing
* **mutex:** add tests for keyed mutex
### Documentation
* refine deployment documentation
* **i18n:** add English translations for docs ([#978](https://github.com/ArtalkJS/Artalk/issues/978))
* **landing:** add multi-language and dark-mode for landing
* **landing:** add demo video in landing page
### BREAKING CHANGE
The original Go module name was `github.com/ArtalkJS/Artalk`, which has now been modified to `github.com/artalkjs/artalk/v2` (all lowercase). This change may affect the CI pipeline or other areas if you are compiling the Artalk server and have specified the fixed Go module name. Regarding the original `-ldflags -X github.com/ArtalkJS/Artalk/internal/config.Version` and `CommitHash` definitions, please remove them, as they are now obsolete. The `Version` has been hardcoded into the Go code, and the `CommitHash` is now read from the Go build info via runtime/debug’s vcs.revision value. This change only affects the server developers and does not impact the frontend UI client.
## [v2.9.0](https://github.com/ArtalkJS/Artalk/compare/v2.8.7...v2.9.0) (2024-09-03)
### Features
+47 -1
View File
@@ -25,7 +25,7 @@ cd Artalk
To develop Artalk, both frontend and backend, install the following tools:
- [Node.js](https://nodejs.org/en/) (>= 20.17.0)
- [PNPM](https://pnpm.io/) (>= 9.9.0)
- [PNPM](https://pnpm.io/) (>= 9.10.0)
- [Go](https://golang.org/) (>= 1.22)
- [Docker](https://www.docker.com/) (>= 20.10.0) (optional)
- [Docker Compose](https://docs.docker.com/compose/) (>= 1.29.0) (optional)
@@ -161,6 +161,52 @@ The compiled JavaScript and CSS files will be located in the `/public` directory
For more details, refer to the `scripts/build-frontend.sh` script.
### Publish Frontend
The core artalk client code is automatically deployed to NPM by GitHub Actions. The deployment process is defined in the `.github/workflows/build-ui.yml` file.
If you are writing a artalk plugin in monorepo, it would not be automatically deployed. You should publish it manually. To publish the plugin, first ensure your version number is updated in the `package.json` file. Then, run the following command:
```sh
pnpm publish --access public
```
#### Check Published Versions
The `pnpm check:publish` script is designed to verify that all packages in the project have the latest versions published on npm. It skips private packages automatically and allows filtering to check specific packages using the `-F` option.
Check all packages:
```sh
pnpm check:publish
```
This will initiate the process of checking all public packages in the repository to ensure they are up to date on npm.
### Develop and Debug `@artalk/plugin-kit` and `eslint-plugin-artalk`
The monorepo will default to installing the latest version of `@artalk/plugin-kit` and `eslint-plugin-artalk` from NPM published packages. To develop and debug these packages, run the following commands from the root of the repository:
```sh
pnpm link --global --dir ui/eslint-plugin-artalk
pnpm link --global --dir ui/plugin-kit
pnpm link eslint-plugin-artalk
pnpm link @artalk/plugin-kit
```
After executing these commands, the `eslint-plugin-artalk` and `@artalk/plugin-kit` packages will be linked to the local development environment within the monorepo workspace. You can modify the source code located in the `ui/eslint-plugin-artalk` and `ui/plugin-kit` directories, and the changes will be automatically reflected in the monorepo workspace. If you wish to unlink the packages, run the following commands:
```sh
pnpm unlink eslint-plugin-artalk
pnpm unlink @artalk/plugin-kit
pnpm uninstall --global eslint-plugin-artalk
pnpm uninstall --global @artalk/plugin-kit
```
For more details, refer to the [pnpm link documentation](https://pnpm.io/cli/link).
## Docker Development
### Build Docker Image
+2 -2
View File
@@ -1,5 +1,5 @@
### build Artalk
FROM golang:1.22.6-alpine3.20 AS builder
FROM golang:1.22.7-alpine3.20 AS builder
WORKDIR /source
@@ -22,7 +22,7 @@ ARG SKIP_UI_BUILD=false
RUN set -ex \
&& if [ "$SKIP_UI_BUILD" = "false" ]; then \
apk add --no-cache nodejs npm \
&& npm install -g pnpm@9.9.0 \
&& npm install -g pnpm@9.10.0 \
;fi
RUN set -ex \
+17 -12
View File
@@ -1,12 +1,12 @@
PKG_NAME := github.com/ArtalkJS/Artalk
PKG_NAME := github.com/artalkjs/artalk/v2
BIN_NAME := ./bin/artalk
VERSION ?= $(shell git describe --tags --abbrev=0 --match 'v*')
COMMIT_HASH ?= $(shell git rev-parse --short HEAD)
HAS_RICHGO := $(shell which richgo)
GOTEST ?= $(if $(HAS_RICHGO), richgo test, go test)
ARGS ?= server
export CGO_ENABLED := 1
all: install build
install:
@@ -17,19 +17,19 @@ run: all
build:
go build \
-ldflags "-s -w -X $(PKG_NAME)/internal/config.Version=$(VERSION) \
-X $(PKG_NAME)/internal/config.CommitHash=$(COMMIT_HASH)" \
-ldflags "-s -w" \
-o $(BIN_NAME) \
$(PKG_NAME)
build-frontend:
./scripts/build-frontend.sh
@./scripts/build-frontend.sh
pack-frontend:
@./scripts/pack-frontend.sh
build-debug:
@echo "Building Artalk $(VERSION) for debugging..."
@echo "Building Artalk for debugging..."
@go build \
-ldflags "-X $(PKG_NAME)/internal/config.Version=$(VERSION) \
-X $(PKG_NAME)/internal/config.CommitHash=$(COMMIT_HASH)" \
-gcflags "all=-N -l" \
-o $(BIN_NAME) \
$(PKG_NAME)
@@ -59,7 +59,11 @@ update-conf:
go generate ./internal/config
update-conf-docs:
go run ./internal/config/meta/gen --format markdown --locale zh-CN -o ./docs/docs/guide/env.md
go run ./internal/config/meta/gen --format markdown --locale en -o ./docs/docs/en/guide/env.md
go run ./internal/config/meta/gen --format markdown --locale zh-CN -o ./docs/docs/zh/guide/env.md
update-docs-features:
pnpm -F docs-landing update:readme
update-swagger:
go install github.com/swaggo/swag/cmd/swag@latest
@@ -72,7 +76,8 @@ docker-build:
docker-push:
./scripts/docker-build.sh --push
.PHONY: all install run build build-frontend build-debug dev \
.PHONY: all install run build build-frontend pack-frontend build-debug dev \
test test-coverage test-coverage-html test-frontend-e2e \
update-i18n update-conf update-conf-docs update-swagger \
update-i18n update-conf update-conf-docs \
update-docs-features update-swagger \
docker-build docker-push;
-129
View File
@@ -1,129 +0,0 @@
<p align="center">
<img src="https://user-images.githubusercontent.com/22412567/171680920-6e74b77c-c565-487b-bff1-4f94976ecbe7.png" alt="Artalk" width="100%">
</p>
# Artalk
[![npm version](https://img.shields.io/npm/v/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![npm downloads](https://img.shields.io/npm/dt/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![Docker Pulls](https://img.shields.io/docker/pulls/artalk/artalk-go?style=flat-square)](https://hub.docker.com/r/artalk/artalk-go)
[![Go Report Card](https://goreportcard.com/badge/github.com/ArtalkJS/Artalk?style=flat-square)](https://goreportcard.com/report/github.com/ArtalkJS/Artalk)
[![CircleCI](https://img.shields.io/circleci/build/gh/ArtalkJS/Artalk?style=flat-square)](https://circleci.com/gh/ArtalkJS/Artalk/tree/master)
[![Codecov](https://img.shields.io/codecov/c/gh/ArtalkJS/Artalk?style=flat-square)](https://codecov.io/gh/ArtalkJS/Artalk)
[![npm bundle size](https://img.shields.io/bundlephobia/minzip/artalk?style=flat-square)](https://bundlephobia.com/package/artalk)
[中文](./README.md) • [Official Website](https://artalk.js.org) • [Latest Release](https://github.com/ArtalkJS/Artalk/releases) • [Changelog](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md)
🌌 Artalk is a simple yet feature-rich commenting system that you can deploy out of the box and integrate into any blog, website, or web application.
- 🍃 Frontend ~40KB, pure Vanilla JS
- 🍱 Backend Golang, efficient lightweight cross-platform
- 🐳 One-click deployment via Docker, convenient and fast
- 🌈 Open-source program, self-hosted, privacy-first
## Features
<!-- prettier-ignore-start -->
<!-- features -->
* [Sidebar](https://artalk.js.org/guide/frontend/sidebar.html): Quick management, intuitive browsing
* [Social Login](https://artalk.js.org/guide/frontend/auth.html): Quick login via social accounts
* [Email Notification](https://artalk.js.org/guide/backend/email.html): Multiple sending methods, email templates
* [Multi-channel Push](https://artalk.js.org/guide/backend/admin_notify.html): Multiple push methods, notification templates
* [In-site Notifications](https://artalk.js.org/guide/frontend/sidebar.html): Red dot marking, mention list
* [CAPTCHA](https://artalk.js.org/guide/backend/captcha.html): Multiple verification types, frequency limitation
* [Comment Moderation](https://artalk.js.org/guide/backend/moderator.html): Content detection, spam interception
* [Image Upload](https://artalk.js.org/guide/backend/img-upload.html): Custom upload, support for image hosting
* [Markdown](https://artalk.js.org/guide/intro.html): Support Markdown syntax
* [Emoticons](https://artalk.js.org/guide/frontend/emoticons.html): Compatible with OwO, quick integration
* [Multi-site](https://artalk.js.org/guide/backend/multi-site.html): Site isolation, centralized management
* [Admin](https://artalk.js.org/guide/backend/multi-site.html): Password verification, badge identification
* [Page Management](https://artalk.js.org/guide/frontend/sidebar.html): Quick view, one-click title jump
* [Page Views Statistics](https://artalk.js.org/guide/frontend/pv.html): Easily track page views
* [Hierarchy](https://artalk.js.org/guide/frontend/config.html#nestmax): Nested paginated lists, scroll loading
* [Comment Voting](https://artalk.js.org/guide/frontend/config.html#vote): Upvote or downvote comments
* [Comment Sorting](https://artalk.js.org/guide/frontend/config.html#listsort): Multiple sorting options, freedom to choose
* [Comment Search](https://artalk.js.org/guide/frontend/sidebar.html): Quickly search comment content
* [Comment Pinning](https://artalk.js.org/guide/frontend/sidebar.html): Pin important messages
* [Author-only View](https://artalk.js.org/guide/frontend/config.html): Show only comments from the author
* [Comment Jumping](https://artalk.js.org/guide/intro.html): Quickly jump to referenced comments
* [Auto Save](https://artalk.js.org/guide/frontend/config.html): Content input auto-saving
* [IP Geolocation](https://artalk.js.org/guide/frontend/ip-region.html): User IP location display
* [Data Migration](https://artalk.js.org/guide/transfer.html): Free migration, quick backup
* [Image Lightbox](https://artalk.js.org/guide/frontend/lightbox.html): Quickly integrate image lightbox
* [Image Lazy Loading](https://artalk.js.org/guide/frontend/img-lazy-load.html): Delay loading images, optimize experience
* [Latex](https://artalk.js.org/guide/frontend/latex.html): Latex formula parsing integration
* [Dark Mode](https://artalk.js.org/guide/frontend/config.html#darkmode): Dark mode switching
* [Extension Plugins](https://artalk.js.org/develop/): Create more possibilities
* [Multi-language](https://artalk.js.org/guide/frontend/i18n.html): Multi-language switching
* [Command Line](https://artalk.js.org/guide/backend/config.html): Command line operation management capability
* [API Documentation](https://artalk.js.org/develop/): Provides OpenAPI format documentation
* [Program Upgrade](https://artalk.js.org/guide/backend/update.html): Version detection, one-click upgrade
<!-- /features -->
<!-- prettier-ignore-end -->
## Installation
Deploy via Docker with one click:
```bash
docker run -d \
--name artalk \
-p 8080:23366 \
-v $(pwd)/data:/data \
-e "TZ=America/New_York" \
-e "ATK_LOCALE=en" \
-e "ATK_SITE_DEFAULT=Artalk Blog" \
-e "ATK_SITE_URL=https://example.com" \
artalk/artalk-go
```
Integrate Artalk into your webpage:
<!-- prettier-ignore-start -->
```ts
Artalk.init({
el: '#Comments',
site: 'Artalk Blog',
server: 'https://artalk.example.com',
pageKey: '/2018/10/02/hello-world.html'
})
```
<!-- prettier-ignore-end -->
[**Learn More →**](https://artalk.js.org/guide/deploy.html)
## For Developers
Pull requests are welcome!
See [Development](https://artalk.js.org/develop/) and [Contributing](./CONTRIBUTING.md) for information on working with the codebase, getting a local development setup, and contributing changes.
## Contributors
Your contributions enrich the open-source community, fostering learning, inspiration, and innovation. We deeply value your involvement. Thank you for being a vital part of our community! 🥰
[![](https://contrib.rocks/image?repo=ArtalkJS/Artalk)](https://github.com/ArtalkJS/Artalk/graphs/contributors)
## Supporters
[![Stargazers repo roster for @ArtalkJS/Artalk](https://reporoster.com/stars/ArtalkJS/Artalk)](https://github.com/ArtalkJS/Artalk/stargazers)
## Repobeats Analytics
![Alt](https://repobeats.axiom.co/api/embed/a9fc9191ac561bc5a8ee2cddc81e635ecaebafb6.svg 'Repobeats analytics image')
## Stargazers over time
[![Stargazers over time](https://starchart.cc/ArtalkJS/Artalk.svg)](https://starchart.cc/ArtalkJS/Artalk)
## License
[MIT](./LICENSE)
[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk?ref=badge_shield)
[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk?ref=badge_large)
+54 -49
View File
@@ -7,86 +7,87 @@
[![npm version](https://img.shields.io/npm/v/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![npm downloads](https://img.shields.io/npm/dt/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![Docker Pulls](https://img.shields.io/docker/pulls/artalk/artalk-go?style=flat-square)](https://hub.docker.com/r/artalk/artalk-go)
[![Go Reference](https://pkg.go.dev/badge/github.com/artalkjs/artalk/v2.svg)](https://pkg.go.dev/github.com/artalkjs/artalk/v2)
[![Go Report Card](https://goreportcard.com/badge/github.com/ArtalkJS/Artalk?style=flat-square)](https://goreportcard.com/report/github.com/ArtalkJS/Artalk)
[![CircleCI](https://img.shields.io/circleci/build/gh/ArtalkJS/Artalk?style=flat-square)](https://circleci.com/gh/ArtalkJS/Artalk/tree/master)
[![Codecov](https://img.shields.io/codecov/c/gh/ArtalkJS/Artalk?style=flat-square)](https://codecov.io/gh/ArtalkJS/Artalk)
[![npm bundle size](https://img.shields.io/bundlephobia/minzip/artalk?style=flat-square)](https://bundlephobia.com/package/artalk)
[English](./README.en.md) • [官方网站](https://artalk.js.org) • [最新版本](https://github.com/ArtalkJS/Artalk/releases) • [更新日志](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md)
[Homepage](https://artalk.js.org) • [Documentation](https://artalk.js.org/en/guide/deploy.html) • [Latest Release](https://github.com/ArtalkJS/Artalk/releases) • [Changelog](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md) • [简体中文](./README.zh.md)
Artalk 是一款简单易用但功能丰富的评论系统,你可以开箱即用地部署并置入任何博客、网站、Web 应用。
Artalk is an intuitive yet feature-rich comment system, ready for immediate deployment into any blog, website, or web application.
- 🍃 前端 ~40KB,纯天然 Vanilla JS
- 🍱 后端 Golang,高效轻量跨平台
- 🐳 通过 Docker 一键部署,方便快捷
- 🌈 开源程序,自托管,隐私至上
- 🍃 Client ~40KB, crafted with pure Vanilla JS, framework-agnostic
- 🍱 Server powered by Golang, offering efficient and lightweight cross-platform performance
- 🐳 One-click deployment via Docker, ensuring ease and speed
- 🌈 Open-source software, self-hosted with privacy as a priority
## 特性
## Features
<!-- prettier-ignore-start -->
<!-- features -->
* [侧边栏](https://artalk.js.org/guide/frontend/sidebar.html): 快速管理、直观浏览
* [社交登录](https://artalk.js.org/guide/frontend/auth.html): 通过社交账号快速登录
* [邮件通知](https://artalk.js.org/guide/backend/email.html): 多种发送方式、邮件模板
* [多元推送](https://artalk.js.org/guide/backend/admin_notify.html): 多种推送方式、通知模版
* [站内通知](https://artalk.js.org/guide/frontend/sidebar.html): 红点标记、提及列表
* [验证码](https://artalk.js.org/guide/backend/captcha.html): 多种验证类型、频率限制
* [评论审核](https://artalk.js.org/guide/backend/moderator.html): 内容检测、垃圾拦截
* [图片上传](https://artalk.js.org/guide/backend/img-upload.html): 自定义上传、支持图床
* [Markdown](https://artalk.js.org/guide/intro.html): 支持 Markdown 语法
* [表情包](https://artalk.js.org/guide/frontend/emoticons.html): 兼容 OwO,快速集成
* [多站点](https://artalk.js.org/guide/backend/multi-site.html): 站点隔离、集中管理
* [管理员](https://artalk.js.org/guide/backend/multi-site.html): 密码验证、徽章标识
* [页面管理](https://artalk.js.org/guide/frontend/sidebar.html): 快速查看、标题一键跳转
* [浏览量统计](https://artalk.js.org/guide/frontend/pv.html): 轻松统计网页浏览量
* [层级结构](https://artalk.js.org/guide/frontend/config.html#nestmax): 嵌套分页列表、滚动加载
* [评论投票](https://artalk.js.org/guide/frontend/config.html#vote): 赞同或反对评论
* [评论排序](https://artalk.js.org/guide/frontend/config.html#listsort): 多种排序方式,自由选择
* [评论搜索](https://artalk.js.org/guide/frontend/sidebar.html): 快速搜索评论内容
* [评论置顶](https://artalk.js.org/guide/frontend/sidebar.html): 重要消息置顶显示
* [仅看作者](https://artalk.js.org/guide/frontend/config.html): 仅显示作者的评论
* [评论跳转](https://artalk.js.org/guide/intro.html): 快速跳转到引用的评论
* [自动保存](https://artalk.js.org/guide/frontend/config.html): 输入内容防丢功能
* [IP 属地](https://artalk.js.org/guide/frontend/ip-region.html): 用户 IP 属地展示
* [数据迁移](https://artalk.js.org/guide/transfer.html): 自由迁移、快速备份
* [图片灯箱](https://artalk.js.org/guide/frontend/lightbox.html): 图片灯箱快速集成
* [图片懒加载](https://artalk.js.org/guide/frontend/img-lazy-load.html): 延迟加载图片,优化体验
* [Latex](https://artalk.js.org/guide/frontend/latex.html): Latex 公式解析集成
* [夜间模式](https://artalk.js.org/guide/frontend/config.html#darkmode): 夜间模式切换
* [扩展插件](https://artalk.js.org/develop/): 创造更多可能性
* [多语言](https://artalk.js.org/guide/frontend/i18n.html): 多国语言切换
* [命令行](https://artalk.js.org/guide/backend/config.html): 命令行操作管理能力
* [API 文档](https://artalk.js.org/develop/): 提供 OpenAPI 格式文档
* [程序升级](https://artalk.js.org/guide/backend/update.html): 版本检测,一键升级
* [Sidebar](https://artalk.js.org/guide/frontend/sidebar.html): Quick management, intuitive browsing
* [Social Login](https://artalk.js.org/guide/frontend/auth.html): Fast login via social accounts
* [Email Notification](https://artalk.js.org/guide/backend/email.html): Various sending methods, email templates
* [Diverse Push](https://artalk.js.org/guide/backend/admin_notify.html): Multiple push methods, notification templates
* [Site Notification](https://artalk.js.org/guide/frontend/sidebar.html): Red dot marks, mention list
* [Captcha](https://artalk.js.org/guide/backend/captcha.html): Various verification types, frequency limits
* [Comment Moderation](https://artalk.js.org/guide/backend/moderator.html): Content detection, spam interception
* [Image Upload](https://artalk.js.org/guide/backend/img-upload.html): Custom upload, supports image hosting
* [Markdown](https://artalk.js.org/guide/intro.html): Supports Markdown syntax
* [Emoji Pack](https://artalk.js.org/guide/frontend/emoticons.html): Compatible with OwO, quick integration
* [Multi-Site](https://artalk.js.org/guide/backend/multi-site.html): Site isolation, centralized management
* [Admin](https://artalk.js.org/guide/backend/multi-site.html): Password verification, badge identification
* [Page Management](https://artalk.js.org/guide/frontend/sidebar.html): Quick view, one-click title navigation
* [Page View Statistics](https://artalk.js.org/guide/frontend/pv.html): Easily track page views
* [Hierarchical Structure](https://artalk.js.org/guide/frontend/config.html#nestmax): Nested paginated list, infinite scroll
* [Comment Voting](https://artalk.js.org/guide/frontend/config.html#vote): Upvote or downvote comments
* [Comment Sorting](https://artalk.js.org/guide/frontend/config.html#listsort): Various sorting options, freely selectable
* [Comment Search](https://artalk.js.org/guide/frontend/sidebar.html): Quick comment content search
* [Comment Pinning](https://artalk.js.org/guide/frontend/sidebar.html): Pin important messages
* [View Author Only](https://artalk.js.org/guide/frontend/config.html): Show only the author's comments
* [Comment Jump](https://artalk.js.org/guide/intro.html): Quickly jump to quoted comment
* [Auto Save](https://artalk.js.org/guide/frontend/config.html): Content loss prevention
* [IP Region](https://artalk.js.org/guide/frontend/ip-region.html): Display user's IP region
* [Data Migration](https://artalk.js.org/guide/transfer.html): Free migration, quick backup
* [Image Lightbox](https://artalk.js.org/guide/frontend/lightbox.html): Quick integration of image lightbox
* [Image Lazy Load](https://artalk.js.org/guide/frontend/img-lazy-load.html): Lazy load images, optimize experience
* [Latex](https://artalk.js.org/guide/frontend/latex.html): Integrate Latex formula parsing
* [Night Mode](https://artalk.js.org/guide/frontend/config.html#darkmode): Switch to night mode
* [Extension Plugin](https://artalk.js.org/develop/plugin.html): Create more possibilities
* [Multi-Language](https://artalk.js.org/guide/frontend/i18n.html): Switch between multiple languages
* [Command Line](https://artalk.js.org/guide/backend/config.html): Command line operation management
* [API Documentation](https://artalk.js.org/http-api.html): Provides OpenAPI format documentation
* [Program Upgrade](https://artalk.js.org/guide/backend/update.html): Version check, one-click upgrade
<!-- /features -->
<!-- prettier-ignore-end -->
## 安装
## Installation
通过 Docker 一键部署:
Deploy Artalk Server with Docker in one step:
```bash
docker run -d \
--name artalk \
-p 8080:23366 \
-v $(pwd)/data:/data \
-e "TZ=Asia/Shanghai" \
-e "ATK_LOCALE=zh-CN" \
-e "ATK_SITE_DEFAULT=Artalk 的博客" \
-e "TZ=America/New_York" \
-e "ATK_LOCALE=en" \
-e "ATK_SITE_DEFAULT=Artalk Blog" \
-e "ATK_SITE_URL=https://example.com" \
artalk/artalk-go
```
在网页中引入 Artalk:
Integrate Artalk Client into your webpage:
<!-- prettier-ignore-start -->
```ts
Artalk.init({
el: '#Comments',
site: 'Artalk 的博客',
site: 'Artalk Blog',
server: 'https://artalk.example.com',
pageKey: '/2018/10/02/hello-world.html'
})
@@ -94,13 +95,15 @@ Artalk.init({
<!-- prettier-ignore-end -->
[**了解更多 →**](https://artalk.js.org/guide/deploy.html)
We offer various installation methods, including binary files, go install, and package managers for Linux distributions.
[**Learn More →**](https://artalk.js.org/en/guide/deploy.html)
## For Developers
Pull requests are welcome!
See [Development](https://artalk.js.org/develop/) and [Contributing](./CONTRIBUTING.md) for information on working with the codebase, getting a local development setup, and contributing changes.
See [Development](https://artalk.js.org/en/develop/) and [Contributing](./CONTRIBUTING.md) for information on working with the codebase, getting a local development setup, and contributing changes.
## Contributors
@@ -118,6 +121,8 @@ Your contributions enrich the open-source community, fostering learning, inspira
## Stargazers over time
<a href="https://trendshift.io/repositories/6290" target="_blank"><img src="https://trendshift.io/api/badge/repositories/6290" alt="ArtalkJS%2FArtalk | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
[![Stargazers over time](https://starchart.cc/ArtalkJS/Artalk.svg)](https://starchart.cc/ArtalkJS/Artalk)
## License
+134
View File
@@ -0,0 +1,134 @@
<p align="center">
<img src="https://user-images.githubusercontent.com/22412567/171680920-6e74b77c-c565-487b-bff1-4f94976ecbe7.png" alt="Artalk" width="100%">
</p>
# Artalk
[![npm version](https://img.shields.io/npm/v/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![npm downloads](https://img.shields.io/npm/dt/artalk.svg?style=flat-square)](https://www.npmjs.com/package/artalk)
[![Docker Pulls](https://img.shields.io/docker/pulls/artalk/artalk-go?style=flat-square)](https://hub.docker.com/r/artalk/artalk-go)
[![Go Reference](https://pkg.go.dev/badge/github.com/artalkjs/artalk/v2.svg)](https://pkg.go.dev/github.com/artalkjs/artalk/v2)
[![Go Report Card](https://goreportcard.com/badge/github.com/ArtalkJS/Artalk?style=flat-square)](https://goreportcard.com/report/github.com/ArtalkJS/Artalk)
[![CircleCI](https://img.shields.io/circleci/build/gh/ArtalkJS/Artalk?style=flat-square)](https://circleci.com/gh/ArtalkJS/Artalk/tree/master)
[![Codecov](https://img.shields.io/codecov/c/gh/ArtalkJS/Artalk?style=flat-square)](https://codecov.io/gh/ArtalkJS/Artalk)
[![npm bundle size](https://img.shields.io/bundlephobia/minzip/artalk?style=flat-square)](https://bundlephobia.com/package/artalk)
[官方网站](https://artalk.js.org) • [最新版本](https://github.com/ArtalkJS/Artalk/releases) • [更新日志](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md) • [English](./README.md)
Artalk 是一款简单易用但功能丰富的评论系统,你可以开箱即用地部署并置入任何博客、网站、Web 应用。
- 🍃 前端 ~40KB,纯天然 Vanilla JS
- 🍱 后端 Golang,高效轻量跨平台
- 🐳 通过 Docker 一键部署,方便快捷
- 🌈 开源程序,自托管,隐私至上
## 特性
<!-- prettier-ignore-start -->
<!-- features -->
* [侧边栏](https://artalk.js.org/guide/frontend/sidebar.html): 快速管理、直观浏览
* [社交登录](https://artalk.js.org/guide/frontend/auth.html): 通过社交账号快速登录
* [邮件通知](https://artalk.js.org/guide/backend/email.html): 多种发送方式、邮件模板
* [多元推送](https://artalk.js.org/guide/backend/admin_notify.html): 多种推送方式、通知模版
* [站内通知](https://artalk.js.org/guide/frontend/sidebar.html): 红点标记、提及列表
* [验证码](https://artalk.js.org/guide/backend/captcha.html): 多种验证类型、频率限制
* [评论审核](https://artalk.js.org/guide/backend/moderator.html): 内容检测、垃圾拦截
* [图片上传](https://artalk.js.org/guide/backend/img-upload.html): 自定义上传、支持图床
* [Markdown](https://artalk.js.org/guide/intro.html): 支持 Markdown 语法
* [表情包](https://artalk.js.org/guide/frontend/emoticons.html): 兼容 OwO,快速集成
* [多站点](https://artalk.js.org/guide/backend/multi-site.html): 站点隔离、集中管理
* [管理员](https://artalk.js.org/guide/backend/multi-site.html): 密码验证、徽章标识
* [页面管理](https://artalk.js.org/guide/frontend/sidebar.html): 快速查看、标题一键跳转
* [浏览量统计](https://artalk.js.org/guide/frontend/pv.html): 轻松统计网页浏览量
* [层级结构](https://artalk.js.org/guide/frontend/config.html#nestmax): 嵌套分页列表、滚动加载
* [评论投票](https://artalk.js.org/guide/frontend/config.html#vote): 赞同或反对评论
* [评论排序](https://artalk.js.org/guide/frontend/config.html#listsort): 多种排序方式,自由选择
* [评论搜索](https://artalk.js.org/guide/frontend/sidebar.html): 快速搜索评论内容
* [评论置顶](https://artalk.js.org/guide/frontend/sidebar.html): 重要消息置顶显示
* [仅看作者](https://artalk.js.org/guide/frontend/config.html): 仅显示作者的评论
* [评论跳转](https://artalk.js.org/guide/intro.html): 快速跳转到引用的评论
* [自动保存](https://artalk.js.org/guide/frontend/config.html): 输入内容防丢功能
* [IP 属地](https://artalk.js.org/guide/frontend/ip-region.html): 用户 IP 属地展示
* [数据迁移](https://artalk.js.org/guide/transfer.html): 自由迁移、快速备份
* [图片灯箱](https://artalk.js.org/guide/frontend/lightbox.html): 图片灯箱快速集成
* [图片懒加载](https://artalk.js.org/guide/frontend/img-lazy-load.html): 延迟加载图片,优化体验
* [Latex](https://artalk.js.org/guide/frontend/latex.html): Latex 公式解析集成
* [夜间模式](https://artalk.js.org/guide/frontend/config.html#darkmode): 夜间模式切换
* [扩展插件](https://artalk.js.org/develop/plugin.html): 创造更多可能性
* [多语言](https://artalk.js.org/guide/frontend/i18n.html): 多国语言切换
* [命令行](https://artalk.js.org/guide/backend/config.html): 命令行操作管理能力
* [API 文档](https://artalk.js.org/http-api.html): 提供 OpenAPI 格式文档
* [程序升级](https://artalk.js.org/guide/backend/update.html): 版本检测,一键升级
<!-- /features -->
<!-- prettier-ignore-end -->
## 安装
通过 Docker 一键部署 Artalk 服务器:
```bash
docker run -d \
--name artalk \
-p 8080:23366 \
-v $(pwd)/data:/data \
-e "TZ=Asia/Shanghai" \
-e "ATK_LOCALE=zh-CN" \
-e "ATK_SITE_DEFAULT=Artalk 的博客" \
-e "ATK_SITE_URL=https://example.com" \
artalk/artalk-go
```
在你的网页中引入 Artalk 客户端:
<!-- prettier-ignore-start -->
```ts
Artalk.init({
el: '#Comments',
site: 'Artalk 的博客',
server: 'https://artalk.example.com',
pageKey: '/2018/10/02/hello-world.html'
})
```
<!-- prettier-ignore-end -->
我们提供多种安装方法,包括二进制文件、`go install` 和通过 Linux 发行版的包管理器安装。
[**了解更多 →**](https://artalk.js.org/zh/guide/deploy.html)
## 参与开发
我们欢迎你的 Pull Request!
有关如何使用代码库、设置本地开发环境和贡献更改的信息,请参阅 [开发文档](https://artalk.js.org/zh/develop/) 和 [贡献指南](./CONTRIBUTING.md)。
## 贡献者们
你的贡献丰富了开源社区,促进了学习、灵感和创新。我们非常重视你的参与。感谢你成为我们社区的重要一员!🥰
[![](https://contrib.rocks/image?repo=ArtalkJS/Artalk)](https://github.com/ArtalkJS/Artalk/graphs/contributors)
## 支持者们
[![Stargazers repo roster for @ArtalkJS/Artalk](https://reporoster.com/stars/ArtalkJS/Artalk)](https://github.com/ArtalkJS/Artalk/stargazers)
## Repobeats 分析
![Alt](https://repobeats.axiom.co/api/embed/a9fc9191ac561bc5a8ee2cddc81e635ecaebafb6.svg 'Repobeats analytics image')
## Star 趋势
<a href="https://trendshift.io/repositories/6290" target="_blank"><img src="https://trendshift.io/api/badge/repositories/6290" alt="ArtalkJS%2FArtalk | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>
[![Stargazers over time](https://starchart.cc/ArtalkJS/Artalk.svg)](https://starchart.cc/ArtalkJS/Artalk)
## 开源许可协议
[MIT](./LICENSE) (麻省理工学院许可证)
[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk.svg?type=shield)](https://app.fossa.com/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk?ref=badge_shield)
[![FOSSA Status](https://app.fossa.com/api/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk.svg?type=large)](https://app.fossa.com/projects/git%2Bgithub.com%2FArtalkJS%2FArtalk?ref=badge_large)
+4 -4
View File
@@ -7,10 +7,10 @@ import (
"strings"
"syscall"
"github.com/ArtalkJS/Artalk/internal/entity"
"github.com/ArtalkJS/Artalk/internal/i18n"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/ArtalkJS/Artalk/internal/utils"
"github.com/artalkjs/artalk/v2/internal/entity"
"github.com/artalkjs/artalk/v2/internal/i18n"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/artalkjs/artalk/v2/internal/utils"
"github.com/spf13/cobra"
"golang.org/x/term"
)
+50 -15
View File
@@ -4,17 +4,18 @@ import (
"fmt"
"os"
"os/signal"
"path"
"syscall"
"github.com/ArtalkJS/Artalk/internal/config"
"github.com/ArtalkJS/Artalk/internal/core"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/adrg/xdg"
"github.com/artalkjs/artalk/v2/internal/config"
"github.com/artalkjs/artalk/v2/internal/core"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/artalkjs/artalk/v2/internal/utils"
"github.com/fatih/color"
"github.com/spf13/cobra"
)
var Version = config.Version + `/` + config.CommitHash
var Banner = `
________ ________ _________ ________ ___ ___ __
|\ __ \|\ __ \|\___ ___\\ __ \|\ \ |\ \|\ \
@@ -24,7 +25,7 @@ var Banner = `
\ \__\ \__\ \__\\ _\ \ \__\ \ \__\ \__\ \_______\ \__\\ \__\
\|__|\|__|\|__|\|__| \|__| \|__|\|__|\|_______|\|__| \|__|
Artalk (` + Version + `)
Artalk (` + config.VersionString() + `)
-> A Self-hosted Comment System.
-> https://artalk.js.org
@@ -52,7 +53,7 @@ func New() *ArtalkCmd {
Use: "artalk",
Short: "Artalk: A self-hosted comment system",
Long: Banner,
Version: Version,
Version: config.VersionString(),
Run: func(cmd *cobra.Command, args []string) {
fmt.Println(Banner)
fmt.Print("-------------------------------\n\n")
@@ -66,11 +67,11 @@ func New() *ArtalkCmd {
// Parse base flags
cmd.eagerParseFlags()
// Change work directory
if cmd.workDir != "" {
if err := os.Chdir(cmd.workDir); err != nil {
log.Fatal("Working directory change error: ", err)
}
// Init data directory (work directory)
if workDir, err := initDataDir(cmd.workDir); err == nil {
cmd.workDir = workDir
} else {
log.Fatal("Data directory fail: ", err)
}
return cmd
@@ -169,16 +170,50 @@ func (atk *ArtalkCmd) Launch() error {
return nil
}
func initDataDir(workDir string) (string, error) {
// If work directory is not specified, try to find it
if workDir == "" {
// If `data` in current directory exists, not change work directory
if utils.CheckDirExist("./data") {
// log.Warn("[DEPRECATED] The `data` directory is deprecated, please move to `~/.local/share/artalk/data`")
return "", nil
}
// Retrieve data directory assuming it's already exists
workDir = config.RetrieveDataDir()
}
// Create new data directory if not exists
if workDir == "" {
// default data path is `~/.local/share/artalk`
workDir = path.Join(xdg.DataHome, "artalk")
if err := utils.EnsureDir(workDir); err != nil {
return "", fmt.Errorf("data directory creation error: %v", err)
}
}
// Change work directory
if workDir != "" {
if err := os.Chdir(workDir); err != nil {
return "", fmt.Errorf("working directory change error: %v", err)
}
}
return workDir, nil
}
// Create new config instance by specific config filename
func getConfig(cfgFile string) (*config.Config, error) {
// Retrieve config file by default names when specific filename is empty
// If config file is not specified, try to find it
if cfgFile == "" {
// Retrieve config file assuming it's already exists
cfgFile = config.RetrieveConfigFile()
}
// Generate new config file when retrieve failed
// Generate new config file if not exists
if cfgFile == "" {
cfgFile = config.CONF_DEFAULT_FILENAMES[0]
// default config path is `~/.config/artalk/artalk.yml`
cfgFile = path.Join(xdg.ConfigHome, "artalk", config.CONF_DEFAULT_FILENAMES[0])
core.Gen("config", cfgFile, false)
}
+1 -1
View File
@@ -4,7 +4,7 @@ import (
"encoding/json"
"fmt"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/spf13/cobra"
)
+4 -4
View File
@@ -7,10 +7,10 @@ import (
"path/filepath"
"time"
"github.com/ArtalkJS/Artalk/internal/artransfer"
"github.com/ArtalkJS/Artalk/internal/i18n"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/ArtalkJS/Artalk/internal/utils"
"github.com/artalkjs/artalk/v2/internal/artransfer"
"github.com/artalkjs/artalk/v2/internal/i18n"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/artalkjs/artalk/v2/internal/utils"
"github.com/spf13/cobra"
)
+1 -1
View File
@@ -1,7 +1,7 @@
package cmd
import (
"github.com/ArtalkJS/Artalk/internal/core"
"github.com/artalkjs/artalk/v2/internal/core"
"github.com/spf13/cobra"
)
+3 -3
View File
@@ -5,9 +5,9 @@ import (
"errors"
"os"
"github.com/ArtalkJS/Artalk/internal/artransfer"
"github.com/ArtalkJS/Artalk/internal/i18n"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/artalkjs/artalk/v2/internal/artransfer"
"github.com/artalkjs/artalk/v2/internal/i18n"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/spf13/cobra"
)
+2 -2
View File
@@ -3,8 +3,8 @@ package cmd
import (
"fmt"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/ArtalkJS/Artalk/server"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/artalkjs/artalk/v2/server"
"github.com/spf13/cobra"
)
+3 -3
View File
@@ -5,9 +5,9 @@ import (
"os"
"strings"
"github.com/ArtalkJS/Artalk/internal/config"
"github.com/ArtalkJS/Artalk/internal/i18n"
"github.com/ArtalkJS/Artalk/internal/log"
"github.com/artalkjs/artalk/v2/internal/config"
"github.com/artalkjs/artalk/v2/internal/i18n"
"github.com/artalkjs/artalk/v2/internal/log"
"github.com/blang/semver"
"github.com/rhysd/go-github-selfupdate/selfupdate"
"github.com/spf13/cobra"
+2 -1
View File
@@ -3,6 +3,7 @@ package cmd
import (
"fmt"
"github.com/artalkjs/artalk/v2/internal/config"
"github.com/spf13/cobra"
)
@@ -11,7 +12,7 @@ func NewVersionCommand() *cobra.Command {
Use: "version",
Short: "Output version information",
Run: func(cmd *cobra.Command, args []string) {
fmt.Println("Artalk (" + Version + ")")
fmt.Println("Artalk (" + config.VersionString() + ")")
},
Annotations: map[string]string{
BootModeKey: MODE_MINI_BOOT,
+1 -1
View File
@@ -401,7 +401,7 @@ frontend:
emoticons: https://cdn.jsdelivr.net/gh/ArtalkJS/Emoticons/grps/default.json
# Vote button
vote: true
# Dislike button
# Vote down button
voteDown: false
# User UA badge
uaBadge: false
+457
View File
@@ -0,0 +1,457 @@
# 伺服器地址
host: "0.0.0.0"
# 伺服器端口
port: 23366
# 加密密鑰
app_key: ""
# 偵錯模式
debug: false
# 語言 ["en", "zh-CN", "zh-TW", "ja", "fr", "ko", "ru"]
locale: zh-TW
# 時區
timezone: Asia/Taipei
# 預設站點名稱
site_default: 預設站點
# 預設站點地址
site_url: ""
# 登入有效時長 (單位:秒)
login_timeout: 259200
# 資料庫
db:
# 資料庫類型 ["sqlite", "mysql", "pgsql", "mssql"]
type: sqlite
# 資料庫文件 (僅 SQLite 資料庫需填寫)
file: ./data/artalk.db
# 資料庫名稱
name: artalk
# 資料庫地址
host: localhost
# 資料庫端口
port: 3306
# 資料庫帳號
user: root
# 資料庫密碼
password: ""
# 編碼格式
charset: utf8mb4
# 表前綴 (例如:"atk_")
table_prefix: ""
# 啟用 SSL
ssl: false
# 預編譯語句
prepare_stmt: true
# 伺服器
http:
# 請求體大小限制 (單位:MB)
body_limit: 100
# 代理標頭名 (當使用 CDN 時填寫 `X-Forwarded-For` 獲取用戶真實 IP)
proxy_header: ""
# 日誌
log:
# 啟用日誌
enabled: true
# 日誌文件路徑
filename: ./data/artalk.log
# 快取
cache:
# 啟用快取
enabled: false
# 快取類型 ["redis", "memcache", "builtin"]
type: builtin
# 快取過期時間 (單位:分鐘)
expires: 30
# 快取啟動預熱 (程式啟動時預熱快取)
warm_up: false
# 快取伺服器地址 (例如:"localhost:6379")
server: ""
# Redis 配置
redis:
# 連接方式 ["tcp", "unix"]
network: tcp
# 用戶名
username: ""
# 密碼
password: ""
# 資料庫編號 (例如使用零號資料庫填寫 0)
db: 0
# 可信網域
# -- 例如:["https://artalk.example.com:23366"] --
trusted_domains: []
# SSL
ssl:
# 啟用 SSL
enabled: false
# 憑證文件路徑
cert_path: ""
# 密鑰文件路徑
key_path: ""
# 管理員帳戶
# --
# - name: "admin"
# email: "admin@example.com"
# password: "" # 支持 bcrypt 或 md5 加密,如:"(bcrypt)$2y$10$ti4vZYIrxVN8rLcYXVgXCO.GJND0dyI49r7IoF3xqIx8bBRmIBZRm"
# badge_name: "管理員"
# badge_color: "#0083FF"
# --
admin_users: []
# 評論審核
moderator:
# 預設待審 (發表新評論需要後台人工審核後才能顯示)
pending_default: false
# API 請求錯誤時攔截 (關閉此項當請求錯誤時讓評論放行)
api_fail_block: false
# Akismet Key
# (Akismet 反垃圾服務,https://akismet.com)
akismet_key: ""
# 騰訊雲文本內容安全
# (https://cloud.tencent.com/document/product/1124/64508)
tencent:
enabled: false
secret_id: ""
secret_key: ""
region: ap-guangzhou
# 阿里雲內容安全
# (https://help.aliyun.com/document_detail/28417.html)
aliyun:
enabled: false
access_key_id: ""
access_key_secret: ""
region: cn-shanghai
# 關鍵詞過濾 (本地離線詞庫)
keywords:
enabled: false
# 匹配成功設為待審狀態
pending: false
# 詞庫文件 (支持多個詞庫文件)
files:
- ./data/詞庫_1.txt
# 詞庫文件內容分割符 (例如填寫 "\n" 文件中一行一個關鍵詞)
file_sep: "\n"
# 替換字符
replace_to: x
# 驗證碼
captcha:
# 啟用驗證碼
enabled: true
# 總是需要驗證碼
always: false
# 驗證類型 ["image", "turnstile", "recaptcha", "hcaptcha", "geetest"]
captcha_type: image
# 激活驗證碼所需操作次數
action_limit: 3
# 重置操作計數器超時 (單位:s, 設為 -1 不重置)
action_reset: 60
# Turnstile
# (https://www.cloudflare.com/products/turnstile/)
turnstile:
site_key: ""
secret_key: ""
# reCaptcha
# (https://www.google.com/recaptcha/about/)
recaptcha:
site_key: ""
secret_key: ""
# hCaptcha (https://www.hcaptcha.com/)
hcaptcha:
site_key: ""
secret_key: ""
# Geetest 極驗 (https://www.geetest.com)
geetest:
captcha_id: ""
captcha_key: ""
# IP 屬地
ip_region:
# 啟用 IP 屬地展示
enabled: false
# 數據文件路徑 (.xdb 格式)
db_path: ./data/ip2region.xdb
# 顯示精度 ["province", "city", "country"]
precision: province
# 圖片上傳
img_upload:
# 啟用圖片上傳
enabled: true
# 圖片存放路徑
path: ./data/artalk-img/
# 圖片大小限制 (單位:MB)
max_size: 5
# 圖片連結基礎路徑 (默認為 "/static/images/")
public_path: null
# Upgit 配置
# (使用 Upgit 將圖片上傳到 GitHub 或圖床:https://github.com/pluveto/upgit)
upgit:
# 啟用 Upgit
enabled: false
# 命令行參數
exec: upgit -c <upgit配置文件路徑> -t /artalk-img
# 上傳後刪除本地的圖片
del_local: true
# 郵件通知
email:
# 啟用郵件通知
enabled: false
# 發送方式 ["smtp", "ali_dm", "sendmail"]
send_type: smtp
# 發信人暱稱
send_name: "{{reply_nick}}"
# 發信人地址
send_addr: noreply@example.com
# 郵件標題
mail_subject: "[{{site_name}}] 您收到了來自 @{{reply_nick}} 的回覆"
# 郵件模板文件 (填入文件路徑使用自定義模板)
mail_tpl: default
# SMTP 發送 (啟用請將發送方式設為 "smtp")
smtp:
# 發件地址
host: smtp.qq.com
# 發件端口
port: 587
# 用戶名
username: example@qq.com
# 密碼
password: ""
# 阿里雲郵件推送
# (啟用請將發送方式設為 "ali_dm";參考:https://help.aliyun.com/document_detail/29444.html)
ali_dm:
access_key_id: ""
access_key_secret: ""
account_name: noreply@example.com
# 多元推送
admin_notify:
# 通知模板 (填入文件路徑使用自定義模板)
notify_tpl: default
# 待審評論仍然發送通知 (當評論被攔截時仍然發送通知)
notify_pending: false
# 嘈雜模式
noise_mode: false
# 郵件通知管理員
email:
# 開啟 (當使用其他推送方式時,可以關閉管理員郵件通知)
enabled: true
# 郵件標題 (發送給管理員的郵件標題)
mail_subject: "[{{site_name}}] 您的文章「{{page_title}}」有新回覆"
# 管理員郵件模板文件 (填入文件路徑使用自定義模板)
mail_tpl: ""
# Telegram
telegram:
enabled: false
api_token: ""
receivers:
- 7777777
# Bark
bark:
enabled: false
server: http://day.app/xxxxxxx/
# 飛書
lark:
enabled: false
webhook_url: ""
# 消息類型 ["text", "card"]
msg_type: "text"
# WebHook
webhook:
enabled: false
url: ""
# 釘釘
ding_talk:
enabled: false
token: ""
secret: ""
# Slack
slack:
enabled: false
oauth_token: ""
receivers:
- CHANNEL_ID
# LINE
line:
enabled: false
channel_secret: ""
channel_access_token: ""
receivers:
- USER_ID_1
- GROUP_ID_1
# 社交登錄
auth:
# 啟用社交登錄
enabled: false
# 允許匿名評論 (允許跳過驗證,僅填寫匿名的暱稱和郵箱)
anonymous: false
# 回調地址 (https://example.com/api/v2/auth/{provider}/callback)
callback: "http://localhost:23366/api/v2/auth/{provider}/callback"
# Email
email:
# 啟用郵箱密碼登錄
enabled: true
# 郵箱驗證郵件標題
verify_subject: "您的驗證碼是 - {{code}}"
# 郵箱驗證郵件模板 (填入文件路徑使用自定義模板)
verify_tpl: default
# GitHub
github:
enabled: false
client_id: ""
client_secret: ""
# GitLab
gitlab:
enabled: false
client_id: ""
client_secret: ""
# Gitea
gitea:
enabled: false
client_id: ""
client_secret: ""
# Google
google:
enabled: false
client_id: ""
client_secret: ""
# Mastodon
mastodon:
enabled: false
client_id: ""
client_secret: ""
# Twitter
twitter:
enabled: false
client_id: ""
client_secret: ""
# Facebook
facebook:
enabled: false
client_id: ""
client_secret: ""
# Discord
discord:
enabled: false
client_id: ""
client_secret: ""
# Steam
steam:
enabled: false
api_key: ""
# Apple
apple:
enabled: false
client_id: ""
client_secret: ""
# Microsoft
microsoft:
enabled: false
client_id: ""
client_secret: ""
# 微信
wechat:
enabled: false
client_id: ""
client_secret: ""
# Tiktok
tiktok:
enabled: false
client_id: ""
client_secret: ""
# Slack
slack:
enabled: false
client_id: ""
client_secret: ""
# Line
line:
enabled: false
client_id: ""
client_secret: ""
# Patreon
patreon:
enabled: false
client_id: ""
client_secret: ""
# Auth0
auth0:
enabled: false
client_id: ""
client_secret: ""
domain: ""
# 介面配置
frontend:
# 評論框占位文字
placeholder: ""
# 無評論顯示文字
noComment: ""
# 發送按鈕文字
sendBtn: ""
# 評論框穿梭
editorTravel: true
# 表情包
emoticons: https://cdn.jsdelivr.net/gh/ArtalkJS/Emoticons/grps/default.json
# 投票按鈕
vote: true
# 反對按鈕
voteDown: false
# 用戶 UA 徽章
uaBadge: false
# 評論排序功能
listSort: true
# 編輯器實時預覽功能
preview: true
# 平鋪模式 ["auto", true, false]
flatMode: auto
# 夜間模式 ["inherit", "auto"]
darkMode: inherit
# 最大嵌套層數
nestMax: 2
# 嵌套評論排序規則 ["DATE_ASC", "DATE_DESC", "VOTE_UP_DESC"]
nestSort: DATE_ASC
# 頭像 Gravatar
gravatar:
# API 地址
mirror: https://weavatar.com/avatar/
# API 參數
params: sha256=1&d=mp&s=240
# 評論分頁
pagination:
# 每頁評論數
pageSize: 20
# 加載更多模式 (關閉則使用分頁條)
readMore: true
# 滾動加載
autoLoad: true
# 內容限高
heightLimit:
# 評論內容限高 (單位:px)
content: 300
# 子評論區域限高 (單位:px)
children: 400
# 滾動限高 (允許限高區域滾動)
scrollable: false
# 圖片懶加載 [false, "native", "data-src"]
imgLazyLoad: false
# 請求超時 (單位:毫秒)
reqTimeout: 15000
# 版本檢測
versionCheck: true
# 插件
pluginURLs: []
-222
View File
@@ -1,222 +0,0 @@
import { defineConfig } from 'vitepress'
import iterator from 'markdown-it-for-inline'
import * as Version from '../code/ArtalkVersion.json'
export default defineConfig({
title: 'Artalk',
description: '一款简洁的自托管评论系统',
lang: 'zh-CN',
head: [
['link', { rel: 'icon', href: '/favicon.png' }],
[
'meta',
{
name: 'viewport',
content:
'width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no, target-densitydpi=device-dpi',
},
],
],
lastUpdated: true,
markdown: {
// @link https://github.com/shikijs/shiki
theme: {
light: 'github-light',
dark: 'github-dark',
},
config: (md) => {
md.use(iterator, 'artalk_version', 'text', function (tokens, idx) {
tokens[idx].content = tokens[idx].content.replace(
/:ArtalkVersion:/g,
Version.latest,
)
})
md.use(iterator, 'artalk_version_link', 'link_open', (tokens, idx) => {
const href = tokens[idx].attrGet('href')
tokens[idx].attrSet(
'href',
href.replace(/:ArtalkVersion:/g, Version.latest),
)
})
},
},
locales: {
root: {
label: '简体中文',
lang: 'zh',
link: 'https://artalk.js.org/',
},
en: {
label: 'English',
lang: 'en',
link: 'https://artalk-js-org.translate.goog/guide/intro?_x_tr_sl=auto&_x_tr_tl=en-US&_x_tr_hl=en-US&_x_tr_pto=wapp',
},
},
themeConfig: {
sidebar: {
'/guide/': [
{
text: '快速开始',
collapsed: false,
items: [
{ text: '项目介绍', link: '/guide/intro.md' },
{ text: '程序部署', link: '/guide/deploy.md' },
{ text: '数据迁移', link: '/guide/transfer.md' },
],
},
{
text: '核心指南',
collapsed: false,
items: [
{ text: '侧边栏', link: '/guide/frontend/sidebar.md' },
{ text: '邮件通知', link: '/guide/backend/email.md' },
{ text: '多元推送', link: '/guide/backend/admin_notify.md' },
{ text: '社交登录', link: '/guide/frontend/auth.md' },
{ text: '评论审核', link: '/guide/backend/moderator.md' },
{ text: '验证码', link: '/guide/backend/captcha.md' },
{ text: '图片上传', link: '/guide/backend/img-upload.md' },
{ text: '账户与多站点', link: '/guide/backend/multi-site.md' },
{ text: '解析相对路径', link: '/guide/backend/relative-path.md' },
],
},
{
text: '进阶指南',
collapsed: false,
items: [
{ text: '表情包', link: '/guide/frontend/emoticons.md' },
{ text: '浏览量统计', link: '/guide/frontend/pv.md' },
{ text: 'LaTeX', link: '/guide/frontend/latex.md' },
{ text: '图片灯箱', link: '/guide/frontend/lightbox.md' },
{ text: '图片懒加载', link: '/guide/frontend/img-lazy-load.md' },
{ text: 'IP 属地', link: '/guide/frontend/ip-region.md' },
{ text: '多语言', link: '/guide/frontend/i18n.md' },
{ text: '开发文档', link: '/develop/index.md' },
],
},
{
text: '配置文档',
collapsed: false,
items: [
{ text: '环境变量', link: '/guide/env.md' },
{ text: '配置文件', link: '/guide/backend/config.md' },
{ text: '界面配置', link: '/guide/frontend/config.md' },
],
},
{
text: '部署说明',
collapsed: true,
items: [
{ text: '守护进程', link: '/guide/backend/daemon.md' },
{ text: '反向代理', link: '/guide/backend/reverse-proxy.md' },
{ text: '编译构建', link: '/develop/contributing.md' },
{ text: '程序升级', link: '/guide/backend/update.md' },
{ text: 'Docker', link: '/guide/backend/docker.md' },
],
},
{
text: '更多内容',
collapsed: true,
items: [
{ text: '安全防范', link: '/guide/security.md' },
{ text: '扩展阅读', link: '/guide/extras.md' },
{ text: '案例展示', link: '/guide/cases.md' },
{ text: '关于我们', link: '/guide/about.md' },
],
},
],
'/develop/': [
{
text: '开发文档',
items: [
{ text: '开发说明', link: '/develop/index.md' },
{ text: '贡献指南', link: '/develop/contributing.md' },
{ text: '置入博客', link: '/develop/import-blog.md' },
{ text: '置入框架', link: '/develop/import-framework.md' },
{ text: '前端 API', link: '/develop/fe-api.md' },
{ text: '前端 Event', link: '/develop/event.md' },
{ text: '插件开发', link: '/develop/plugin.md' },
{ text: '兼容性', link: '/develop/compatibility.md' },
{
text: 'HTTP API',
link: 'https://artalk.js.org/http-api.html',
},
],
},
],
},
nav: [
// NavbarItem
{
text: '介绍',
link: '/guide/intro',
},
{
text: '部署',
link: '/guide/deploy',
},
{
text: '配置',
link: '/guide/backend/config',
},
{
text: '迁移',
link: '/guide/transfer',
},
{
text: '案例',
link: '/guide/cases',
},
{
text: '开发',
link: '/develop/',
},
// NavbarGroup
{
text: '传送',
items: [
{
text: '代码仓库',
link: 'https://github.com/ArtalkJS/Artalk',
},
// {
// text: "文档镜像 (国内)",
// link: "https://artalk-docs.qwqaq.com",
// },
],
},
],
socialLinks: [
{ icon: 'github', link: 'https://github.com/ArtalkJS/Artalk' },
],
search: {
provider: 'algolia',
options: {
appId: '2WNJ32WVTY',
apiKey: '6c6ebc345a87b738264f19095b78c91c',
indexName: 'artalk-js',
searchParameters: {
facetFilters: ['lang:zh-CN'],
},
},
},
editLink: {
pattern: 'https://github.com/ArtalkJS/Artalk/edit/master/docs/docs/:path',
text: '完善文档',
},
},
vite: {
server: {
open: '/guide/intro.html',
},
},
})
+127
View File
@@ -0,0 +1,127 @@
import { defineConfig } from 'vitepress'
export const en = defineConfig({
lang: 'en-US',
description: 'A Self-hosted Comment System.',
themeConfig: {
sidebar: {
'/en/guide/': [
{
text: 'Quick Start',
collapsed: false,
items: [
{ text: 'Introduction', link: '/en/guide/intro.md' },
{ text: 'Getting Started', link: '/en/guide/deploy.md' },
{ text: 'Data Migration', link: '/en/guide/transfer.md' },
],
},
{
text: 'Basic Usage',
collapsed: false,
items: [
{ text: 'Sidebar', link: '/en/guide/frontend/sidebar.md' },
{ text: 'Email Notification', link: '/en/guide/backend/email.md' },
{ text: 'Multi-channel Notification', link: '/en/guide/backend/admin_notify.md' },
{ text: 'Social Login', link: '/en/guide/frontend/auth.md' },
{ text: 'Comment Moderation', link: '/en/guide/backend/moderator.md' },
{ text: 'Captcha', link: '/en/guide/backend/captcha.md' },
{ text: 'Image Upload', link: '/en/guide/backend/img-upload.md' },
{ text: 'Admins and Multi-Site', link: '/en/guide/backend/multi-site.md' },
{ text: 'Resolve Relative Path', link: '/en/guide/backend/relative-path.md' },
],
},
{
text: 'Extensions',
collapsed: false,
items: [
{ text: 'Emoticons', link: '/en/guide/frontend/emoticons.md' },
{ text: 'Page View Statistics', link: '/en/guide/frontend/pv.md' },
{ text: 'LaTeX', link: '/en/guide/frontend/latex.md' },
{ text: 'Image Lightbox', link: '/en/guide/frontend/lightbox.md' },
{ text: 'Image Lazy Load', link: '/en/guide/frontend/img-lazy-load.md' },
{ text: 'Voting', link: '/zh/guide/frontend/voting.md' },
{ text: 'IP Region', link: '/en/guide/frontend/ip-region.md' },
{ text: 'Localization', link: '/en/guide/frontend/i18n.md' },
{ text: 'Development Documentation', link: '/en/develop/index.md' },
],
},
{
text: 'Configurations',
collapsed: false,
items: [
{ text: 'Environment Variables', link: '/en/guide/env.md' },
{ text: 'Configuration File', link: '/en/guide/backend/config.md' },
{ text: 'UI Configuration', link: '/en/guide/frontend/config.md' },
],
},
{
text: 'Deployment details',
collapsed: false,
items: [
{ text: 'Daemon Process', link: '/en/guide/backend/daemon.md' },
{ text: 'Reverse Proxy', link: '/en/guide/backend/reverse-proxy.md' },
{
text: 'Compile Source',
link: 'https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md',
},
{ text: 'Program Upgrade', link: '/en/guide/backend/update.md' },
{ text: 'Docker', link: '/en/guide/backend/docker.md' },
],
},
],
'/en/develop/': [
{
text: 'Development Documentation',
items: [
{ text: 'Development Instructions', link: '/en/develop/index.md' },
{
text: 'Contribution Guide',
link: 'https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md',
target: '_blank',
},
{ text: 'Import to Blog', link: '/en/develop/import-blog.md' },
{ text: 'Import to Framework', link: '/en/develop/import-framework.md' },
{ text: 'Frontend API', link: '/en/develop/fe-api.md' },
{ text: 'Frontend Events', link: '/en/develop/event.md' },
{ text: 'Frontend Types', link: 'https://artalk.js.org/typedoc/' },
{ text: 'Plugin Development', link: '/en/develop/plugin.md' },
{ text: 'Compatibility', link: '/en/develop/compatibility.md' },
{
text: 'HTTP API',
link: 'https://artalk.js.org/http-api.html',
},
],
},
],
},
nav: [
{
text: 'Introduction',
link: '/en/guide/intro',
},
{
text: 'Installation',
link: '/en/guide/deploy',
},
{
text: 'Configuration',
link: '/en/guide/backend/config',
},
{
text: 'Migration',
link: '/en/guide/transfer',
},
{
text: 'Development',
link: '/en/develop/',
},
],
editLink: {
pattern: 'https://github.com/ArtalkJS/Artalk/edit/master/docs/docs/:path',
text: 'Improve this document',
},
},
})
+12
View File
@@ -0,0 +1,12 @@
import { defineConfig } from 'vitepress'
import { shared } from './shared'
import { zh } from './zh'
import { en } from './en'
export default defineConfig({
...shared,
locales: {
en: { label: 'English', ...en },
zh: { label: '简体中文', ...zh },
},
})
+98
View File
@@ -0,0 +1,98 @@
import { defineConfig } from 'vitepress'
import {
GitChangelog,
GitChangelogMarkdownSection,
} from '@nolebase/vitepress-plugin-git-changelog/vite'
import * as Version from '../../code/ArtalkVersion.json'
export const shared = defineConfig({
title: 'Artalk',
/* prettier-ignore */
head: [
['link', { rel: 'icon', type: 'image/png', href: '/favicon.png' }],
['meta', { property: 'og:type', content: 'website' }],
['meta', { property: 'og:locale', content: 'en' }],
['meta', { property: 'og:title', content: 'Artalk - A Self-hosted Comment System'}],
['meta', { property: 'og:site_name', content: 'Artalk' }],
['meta', { property: 'og:image', content: 'https://artalk.js.org/assets/images/artalk-banner.png' }],
['meta', { property: 'og:url', content: 'https://artalk.js.org/' }],
['meta', { name: 'viewport', content: 'width=device-width, initial-scale=1.0, maximum-scale=1.0, minimum-scale=1.0, user-scalable=no, target-densitydpi=device-dpi' }],
],
markdown: {
// @link https://github.com/shikijs/shiki
theme: {
light: 'github-light',
dark: 'github-dark',
},
config: (md) => {
const renderVersion = (c: string) => String(c).replace(/:ArtalkVersion:/g, Version.latest)
md.core.ruler.push('artalk_version', (state) => {
state.tokens?.forEach((token) => {
if (token.type === 'inline') {
token.children?.forEach((child) => {
if (['text', 'link_open', 'code_inline'].includes(child.type))
child.content = renderVersion(child.content)
})
} else if (token.type === 'fence') {
token.content = renderVersion(token.content)
}
})
})
},
},
sitemap: {
hostname: 'https://artalk.js.org',
transformItems(items) {
return items.filter((item) => !item.url.includes('migration'))
},
},
lastUpdated: true,
cleanUrls: false,
metaChunk: true,
themeConfig: {
socialLinks: [{ icon: 'github', link: 'https://github.com/ArtalkJS/Artalk' }],
search: {
provider: 'algolia',
options: {
appId: '2WNJ32WVTY',
apiKey: '6c6ebc345a87b738264f19095b78c91c',
indexName: 'artalk-js',
},
},
},
vite: {
server: {
open: '/zh/guide/intro.html',
},
plugins: [
GitChangelog({
repoURL: () => 'https://github.com/ArtalkJS/Artalk',
mapAuthors: [
{
name: 'qwqcode',
username: 'qwqcode',
mapByEmailAliases: ['qwqcode@gmail.com', '22412567+qwqcode@users.noreply.github.com'],
},
{
name: 'pluveto',
username: 'pluveto',
mapByEmailAliases: ['i@pluvet.com', '50045289+pluveto@users.noreply.github.com'],
},
{
name: 'Mr.Hope',
username: 'Mister-Hope',
mapByEmailAliases: ['mister-hope@outlook.com'],
},
],
}),
GitChangelogMarkdownSection(),
],
},
})
+135
View File
@@ -0,0 +1,135 @@
import { defineConfig } from 'vitepress'
export const zh = defineConfig({
lang: 'zh-CN',
description: '由 Golang 驱动的自托管评论系统',
themeConfig: {
sidebar: {
'/zh/guide/': [
{
text: '快速开始',
collapsed: false,
items: [
{ text: '项目介绍', link: '/zh/guide/intro.md' },
{ text: '程序部署', link: '/zh/guide/deploy.md' },
{ text: '数据迁移', link: '/zh/guide/transfer.md' },
],
},
{
text: '核心指南',
collapsed: false,
items: [
{ text: '侧边栏', link: '/zh/guide/frontend/sidebar.md' },
{ text: '邮件通知', link: '/zh/guide/backend/email.md' },
{ text: '多元推送', link: '/zh/guide/backend/admin_notify.md' },
{ text: '社交登录', link: '/zh/guide/frontend/auth.md' },
{ text: '评论审核', link: '/zh/guide/backend/moderator.md' },
{ text: '验证码', link: '/zh/guide/backend/captcha.md' },
{ text: '图片上传', link: '/zh/guide/backend/img-upload.md' },
{ text: '账户与多站点', link: '/zh/guide/backend/multi-site.md' },
{ text: '解析相对路径', link: '/zh/guide/backend/relative-path.md' },
],
},
{
text: '进阶指南',
collapsed: false,
items: [
{ text: '表情包', link: '/zh/guide/frontend/emoticons.md' },
{ text: '浏览量统计', link: '/zh/guide/frontend/pv.md' },
{ text: 'LaTeX', link: '/zh/guide/frontend/latex.md' },
{ text: '图片灯箱', link: '/zh/guide/frontend/lightbox.md' },
{ text: '图片懒加载', link: '/zh/guide/frontend/img-lazy-load.md' },
{ text: '投票功能', link: '/zh/guide/frontend/voting.md' },
{ text: 'IP 属地', link: '/zh/guide/frontend/ip-region.md' },
{ text: '多语言', link: '/zh/guide/frontend/i18n.md' },
{ text: '开发文档', link: '/zh/develop/index.md' },
],
},
{
text: '配置文档',
collapsed: false,
items: [
{ text: '环境变量', link: '/zh/guide/env.md' },
{ text: '配置文件', link: '/zh/guide/backend/config.md' },
{ text: '界面配置', link: '/zh/guide/frontend/config.md' },
],
},
{
text: '部署说明',
collapsed: true,
items: [
{ text: '守护进程', link: '/zh/guide/backend/daemon.md' },
{ text: '反向代理', link: '/zh/guide/backend/reverse-proxy.md' },
{ text: '编译构建', link: '/zh/develop/contributing.md' },
{ text: '程序升级', link: '/zh/guide/backend/update.md' },
{ text: 'Docker', link: '/zh/guide/backend/docker.md' },
],
},
{
text: '更多内容',
collapsed: true,
items: [
{ text: '安全防范', link: '/zh/guide/security.md' },
{ text: '扩展阅读', link: '/zh/guide/extras.md' },
{ text: '案例展示', link: '/zh/guide/cases.md' },
{ text: '关于我们', link: '/zh/guide/about.md' },
],
},
],
'/zh/develop/': [
{
text: '开发文档',
items: [
{ text: '开发说明', link: '/zh/develop/index.md' },
{ text: '贡献指南', link: '/zh/develop/contributing.md' },
{ text: '置入博客', link: '/zh/develop/import-blog.md' },
{ text: '置入框架', link: '/zh/develop/import-framework.md' },
{ text: '前端 API', link: '/zh/develop/fe-api.md' },
{ text: '前端 Events', link: '/zh/develop/event.md' },
{ text: '前端 Types', link: 'https://artalk.js.org/typedoc/' },
{ text: '插件开发', link: '/zh/develop/plugin.md' },
{ text: '兼容性', link: '/zh/develop/compatibility.md' },
{
text: 'HTTP API',
link: 'https://artalk.js.org/http-api.html',
},
],
},
],
},
nav: [
// NavbarItem
{
text: '介绍',
link: '/zh/guide/intro',
},
{
text: '部署',
link: '/zh/guide/deploy',
},
{
text: '配置',
link: '/zh/guide/backend/config',
},
{
text: '迁移',
link: '/zh/guide/transfer',
},
{
text: '案例',
link: '/zh/guide/cases',
},
{
text: '开发',
link: '/zh/develop/',
},
],
editLink: {
pattern: 'https://github.com/ArtalkJS/Artalk/edit/master/docs/docs/:path',
text: '完善文档',
},
},
})
+15 -4
View File
@@ -10,7 +10,7 @@ import { ArtalkKatexPlugin } from '@artalk/plugin-katex'
import { ArtalkLightboxPlugin } from '@artalk/plugin-lightbox'
import 'lightgallery/css/lightgallery.css'
import 'katex/dist/katex.min.css'
import 'artalk/dist/Artalk.css'
import 'artalk/Artalk.css'
const el = ref<HTMLElement | null>(null)
@@ -43,8 +43,16 @@ function initArtalk(conf: any) {
Artalk.use(ArtalkKatexPlugin)
Artalk.use(ArtalkLightboxPlugin, {
lightGallery: {
lib: async () => (await import('lightgallery')).default
}
lib: async () => (await import('lightgallery')).default,
},
})
Artalk.use((ctx) => {
ctx.on('mounted', () => {
// TODO: Optimize the locale setting, which is overwritten by the remote server config
const locale = document.documentElement.lang.includes('zh') ? 'zh-CN' : 'en'
if (locale !== ctx.getConf().locale) ctx.updateConf({ locale })
})
})
artalk = Artalk.init({
@@ -58,7 +66,10 @@ function initArtalk(conf: any) {
function getConfByPage() {
return {
pageKey: 'https://artalk.js.org' + router.route.path,
pageKey: `https://artalk.js.org/${router.route.path
.replace(/^\/+/, '')
.replace(/^zh\//, '')
.replace(/\.html$/, '')}.html`,
pageTitle: page.value.title,
server: 'https://artalk.qwqaq.com',
site: 'ArtalkDocs',
+8 -1
View File
@@ -1,9 +1,16 @@
<script setup>
import DefaultTheme from 'vitepress/theme'
import { onMounted } from 'vue'
import { inBrowser, useData } from 'vitepress'
import { watchEffect } from 'vue'
import './style.scss'
const { Layout } = DefaultTheme
const { lang } = useData()
watchEffect(() => {
if (inBrowser)
document.cookie = `nf_lang=${lang.value}; expires=Mon, 1 Jan 2030 00:00:00 UTC; path=/`
})
</script>
<template>
+4
View File
@@ -1,9 +1,12 @@
import DefaultTheme from 'vitepress/theme'
import { Theme } from 'vitepress'
import { NolebaseGitChangelogPlugin } from '@nolebase/vitepress-plugin-git-changelog/client'
import Layout from './Layout.vue'
import Artalk from './Artalk.vue'
import Artransfer from './Artransfer.vue'
import '@nolebase/vitepress-plugin-git-changelog/client/style.css'
export default {
...DefaultTheme,
@@ -12,6 +15,7 @@ export default {
enhanceApp({ app, router, siteData }) {
app.component('Artransfer', Artransfer)
app.component('Artalk', Artalk)
app.use(NolebaseGitChangelogPlugin)
// app is the Vue 3 app instance from `createApp()`.
// router is VitePress' custom router. `siteData` is
+1 -1
View File
@@ -1,3 +1,3 @@
{
"latest": "2.9.0"
"latest": "2.9.1"
}
-592
View File
@@ -1,592 +0,0 @@
# HTTP API
::: warning
该 HTTP API 文档已过时
:::
::: tip 无特殊说明时 API 调用响应格式
| 字段名 | 类型 | 说明 |
| --------- | ------- | --------------------------------------------- |
| `success` | Boolean | 接口调用结果 |
| `msg` | String | 返回消息,出错时此字段包含错误消息 |
| `data` | Any | 返回数据,可能为 Object / String / Array 类型 |
:::
## Normal API
### 评论新增
**POST** `/api/add`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------------ | -------- | :--: | ------------------------------------------------- |
| `name` | String | 是 | 待新增评论者昵称 |
| `email` | String | 是 | 待新增评论者邮箱 |
| `link` | String | 否 | 待新增评论者链接 |
| `content` | String | 是 | 待新增评论内容 |
| `rid` | Number | 否 | 待新增评论为回复评论时传入父评论 `ID`,否则为 `0` |
| `page_key` | String | 是 | 待新增评论目标页面唯一标识符 |
| `page_title` | String | 否 | 待新增评论目标页面标题 |
| `token` | String | 否 | 评论请求 Token |
| `site_name` | String | 否 | 待新增评论目标站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ------------------------------ | -------- | :----: | -------------------------------------- |
| `success` | Boolean | `true` | 评论新增成功 |
| `data.comment` | Object | - | 评论数据 |
| `data.comment.id` | Number | - | 评论 ID |
| `data.comment.content` | String | - | 评论正文 |
| `data.comment.nick` | String | - | 评论者昵称 |
| `data.comment.email_encrypted` | String | - | 评论者邮箱 SHA256 加密值 |
| `data.comment.link` | String | - | 评论者链接 |
| `data.comment.ua` | String | - | 评论者 User-Agent |
| `data.comment.date` | String | - | 评论时间,格式为 `1970-01-01 00:00:00` |
| `data.comment.is_collapsed` | Boolean | - | 评论是否折叠 |
| `data.comment.is_pending` | Boolean | - | 评论是否待审 |
| `data.comment.is_allow_reply` | Boolean | - | 评论是否允许回复 |
| `data.comment.rid` | Number | `0` | 待新增评论为回复评论时返回父评论 `ID` |
| `data.comment.badge_name` | String | - | 评论者徽章文字 |
| `data.comment.badge_color` | String | - | 评论者徽章颜色 |
| `data.comment.visible` | Boolean | `true` | 评论是否可见 |
| `data.comment.vote_up` | Number | `0` | 评论赞同数 |
| `data.comment.vote_down` | Number | `0` | 评论反对数 |
| `data.comment.page_key` | String | - | 评论所在页面唯一标识符 |
| `data.comment.site_name` | String | - | 评论所在站点名称 |
### 评论获取
**POST** `/api/get`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ----------- | -------- | :--: | -------------------------- |
| `page_key` | String | 是 | 待获取评论页面的唯一标识符 |
| `limit` | Number | 否 | 待获取评论的数量限制 |
| `offset` | Number | 否 | 待获取评论的起始位置偏移 |
| `type` | String | 否 | 获取指定类型的评论 |
| `name` | String | 否 | 获取指定昵称的评论 |
| `email` | String | 否 | 获取指定邮箱的评论 |
| `site_name` | String | 否 | 获取指定站点名称的评论 |
| `flat_mode` | Boolean | 否 | 待获取评论是否平铺模式 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ---------------------- | -------- | :----: | ------------------------------ |
| `success` | Boolean | `true` | 评论获取成功 |
| `data.comments` | Array | - | 页面评论数据 |
| `data.total` | Number | - | 页面评论总数(包括所有子评论) |
| `data.total_parents` | Number | - | 页面评论中父级评论总数 |
| `data.page` | Object | - | 页面数据 |
| `data.page.id` | Number | - | 页面 ID |
| `data.page.admin_only` | Boolean | - | 页面是否仅管理员可评论 |
| `data.page.key` | String | - | 页面唯一标识符 |
| `data.page.url` | String | - | 页面链接 |
| `data.page.title` | String | - | 页面标题 |
| `data.page.site_name` | String | - | 页面所在站点名称 |
| `data.page.vote_up` | Number | - | 页面赞同数 |
| `data.page.vote_down` | Number | - | 页面反对数 |
| `data.unread` | Array | - | 未读的评论提醒数据 |
| `data.unread_count` | Number | - | 未读的评论提醒数据总数 |
| `data.api_version` | Object | - | 目标 Artalk 后端版本数据 |
::: tip
- `data.comments` 数组中元素结构参考 [评论新增接口](#评论新增) `/api/add` 响应的 `data.comment`
- `data.unread` 数组中元素结构如下
| 字段名 | 数据类型 | 默认 | 说明 |
| ----- | ------- | :-: | --- |
| `id` | Number | - | 评论提醒 ID |
| `user_id` | Number | - | 评论提醒目标用户 ID |
| `comment_id` | Number | - | 评论提醒来源评论 ID |
| `is_read` | Boolean | - | 评论提醒是否已读 |
| `is_emailed` | Boolean | - | 评论提醒是否已发送邮件 |
| `read_link` | String | - | 评论提醒已读地址 |
- `data.api_version` 对象结构参考 [Artalk 版本接口](#artalk-版本) `/api/version` 响应
:::
### 用户获取
**POST** `/api/user-get`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------- | -------- | :--: | ---------------- |
| `name` | String | 否 | 待获取用户的昵称 |
| `email` | String | 否 | 待获取用户的邮箱 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ----------------------- | -------- | :----: | ---------------------------------- |
| `success` | Boolean | `true` | 用户获取成功 |
| `data.user` | Object | `null` | 获取的用户数据,若用户不存在返回空 |
| `data.user.id` | Number | - | 用户 ID |
| `data.user.name` | String | - | 用户昵称 |
| `data.user.email` | String | - | 用户邮箱 |
| `data.user.link` | String | - | 用户链接 |
| `data.user.badge_name` | String | - | 用户徽章文字 |
| `data.user.badge_color` | String | - | 用户徽章颜色 |
| `data.user.is_admin` | Boolean | - | 用户是否管理员 |
| `data.is_login` | Boolean | - | 用户是否登录 |
| `data.unread` | Array | `[]` | 用户未读的评论提醒数据 |
| `data.unread_count` | Number | `0` | 用户未读的评论提醒数据总数 |
::: tip
- `data.unread` 数组中元素结构参考 [评论获取接口](#评论获取) `/api/get` **TIP**
:::
### 用户登录
**GET/POST** `/api/login`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ---------- | -------- | :--: | ---------------------------------- |
| `name` | String | 是 | 待登录用户的昵称 |
| `email` | String | 是 | 待登录用户的邮箱 |
| `password` | String | 是 | 待登录用户的密码(管理员身份验证) |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ------------ | -------- | :----: | ---------------- |
| `success` | Boolean | `true` | 用户登录成功 |
| `data.token` | String | - | 登录的用户 Token |
### 提醒已读
**POST** `/api/mark-read`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------------ | -------- | :--: | -------------------- |
| `notify_key` | String | 否 | 评论提醒唯一标识符 |
| `name` | String | 否 | 评论提醒用户的昵称 |
| `email` | String | 否 | 评论提醒用户的邮箱 |
| `all_read` | Boolean | 否 | 评论提醒是否已读 |
| `site_name` | String | 否 | 评论提醒所在站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 提醒已读成功 |
### 评论投票
**POST** `/api/vote`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ----------- | -------- | :--: | ----------------------------------------------------------------------------------------------------------- |
| `target_id` | Number | 是 | 待投票评论 ID |
| `type` | String | 否 | 待投票类型,前缀 `comment_`、`page_` 依次代表对评论投票、对页面投票,后缀 `_up`、`_down` 依次代表赞同、反对 |
| `name` | String | 否 | 投票用户昵称 |
| `email` | String | 否 | 投票用户邮箱 |
| `site_name` | String | 否 | 投票目标评论或页面所在站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------------- | -------- | :----: | ------------------------------ |
| `success` | Boolean | `true` | 评论投票成功 |
| `data.vote_num` | Number | - | 目标评论或页面指定类型投票数据 |
### Artalk 版本
::: warning
此接口较特殊,返回结果不包含 `success`、`msg`、`data` 字段,直接返回包含指定字段的 JSON。
:::
**GET/POST** `/api/version`
**参数** 无
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ---------------- | -------- | :------: | ------------------------------- |
| `app` | String | `artalk` | Artalk 后端程序名 |
| `version` | String | - | Artalk 后端程序版本号 |
| `commit_hash` | String | - | Artalk 后端程序 Git 提交哈希值 |
| `fe_min_version` | String | - | Artalk 后端程序所需前端最低版本 |
## Captcha API
### 验证码刷新
**GET** `/api/captcha/refresh`
**参数** 无
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------------- | -------- | :----: | ------------------------------------ |
| `success` | Boolean | `true` | 验证码刷新成功 |
| `data.img_data` | String | - | 根据 IP 获取的验证码图片 Base64 编码 |
### 验证码检验
**GET** `/api/captcha/check`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------- | -------- | :--: | ------ |
| `value` | String | 是 | 验证码 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------------- | -------- | :----: | -------------------------------------------------------- |
| `success` | Boolean | `true` | 验证码检验成功 |
| `data.img_data` | String | - | 新的验证码图片 Base64 编码,仅验证码检验出错时存在此字段 |
## Admin API
### 评论编辑
**POST** `/api/admin/comment-edit`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| -------------- | -------- | :--: | ------------------------------------------------- |
| `id` | Number | 是 | 待编辑评论 ID,**不可修改** |
| `site_name` | String | 否 | 待编辑评论所在站点名称,**不可修改** |
| `content` | String | 否 | 待编辑评论正文 |
| `page_key` | String | 否 | 待编辑评论所在页面唯一标识符 |
| `nick` | String | 否 | 待编辑评论所属用户昵称 |
| `email` | String | 否 | 待编辑评论所属用户邮箱 |
| `link` | String | 否 | 待编辑评论所属用户链接 |
| `rid` | String | 否 | 待编辑评论为回复评论时传入父评论 `ID`,否则为 `0` |
| `ua` | String | 否 | 待编辑评论所属用户 User-Agent |
| `ip` | String | 否 | 待编辑评论所属用户 IP |
| `is_collapsed` | Boolean | 否 | 待编辑评论是否折叠 |
| `is_pending` | Boolean | 否 | 待编辑评论是否待审 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| -------------- | -------- | :----: | ---------------- |
| `success` | Boolean | `true` | 评论编辑成功 |
| `data.comment` | Object | - | 编辑评论的新数据 |
::: tip
- `data.comment` 对象结构参考 [评论新增接口](#评论新增) `/api/add` 响应的 `data.comment`
:::
### 评论删除
::: danger
此接口不推荐外部调用。
调用此接口前请务必核实评论 ID,一旦调用成功将删除该评论下所有相关数据。
:::
**POST** `/api/admin/comment-del`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ----------- | -------- | :--: | ---------------------- |
| `id` | Number | 是 | 待删除评论 ID |
| `site_name` | String | 是 | 待删除评论所在站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 评论删除成功 |
### 页面获取
**POST** `/api/admin/page-get`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ----------- | -------- | :--: | ---------------------- |
| `site_name` | String | 是 | 待获取页面目标站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ------------ | -------- | :----: | ------------------ |
| `success` | Boolean | `true` | 页面获取成功 |
| `data.pages` | Array | - | 目标站点的页面数据 |
| `data.sites` | Array | - | 所有站点数据 |
::: tip
- `data.pages` 数组中元素结构参考 [评论获取接口](#评论获取) `/api/get` 响应的 `data.page`
- `data.sites` 数组中元素结构参考 [站点编辑接口](#站点编辑) `/api/admin/site-edit` 响应的 `data.site`
:::
### 页面编辑
**POST** `/api/admin/page-edit`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------------ | -------- | :--: | ------------------------------------ |
| `id` | Number | 是 | 待编辑页面 ID,**不可修改** |
| `site_name` | String | 否 | 待编辑页面所在站点名称,**不可修改** |
| `key` | String | 否 | 待编辑页面唯一标识符 |
| `title` | String | 否 | 待编辑页面标题 |
| `admin_only` | Boolean | 否 | 待编辑页面是否仅管理员可评论 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ----------- | -------- | :----: | ---------------- |
| `success` | Boolean | `true` | 页面编辑成功 |
| `data.page` | Object | - | 编辑页面的新数据 |
::: tip
- `data.page` 对象结构参考 [评论获取接口](#评论获取) `/api/get` 响应的 `data.page`
:::
### 页面删除
::: danger
此接口不推荐外部调用。
调用此接口前请务必核实页面 ID,一旦调用成功将删除该页面下所有相关数据。
:::
**POST** `/api/admin/page-del`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ----------- | -------- | :--: | ---------------------- |
| `key` | String | 是 | 待删除页面唯一标识符 |
| `site_name` | String | 是 | 待删除页面所在站点名称 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 页面删除成功 |
### 页面更新
**POST** `/api/admin/page-fetch`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------ | -------- | :--: | ------------- |
| `id` | Number | 是 | 待更新页面 ID |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ----------- | -------- | :----: | ---------------- |
| `success` | Boolean | `true` | 页面更新成功 |
| `data.page` | Object | - | 更新页面的新数据 |
::: tip
- `data.page` 对象结构参考 [评论获取接口](#评论获取) `/api/get` 响应的 `data.page`
:::
### 站点获取
**POST** `/api/admin/site-get`
**参数** 无
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| ------------ | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 站点获取成功 |
| `data.sites` | Array | - | 所有站点数据 |
::: tip
- `data.sites` 数组中元素结构参考 [站点编辑接口](#站点编辑) `/api/admin/site-edit` 响应的 `data.site`
:::
### 站点新增
**POST** `/api/admin/site-add`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------ | -------- | :--: | ------------------------------------------------- |
| `name` | String | 是 | 待新增站点名称 |
| `urls` | String | 是 | 待新增站点链接,如有多个需以英文半角符号 `,` 分割 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------------------- | -------- | :----: | ----------------------------------------------- |
| `success` | Boolean | `true` | 站点新增成功 |
| `data.site` | Object | - | 新增站点的数据 |
| `data.site.id` | Number | - | 站点 ID |
| `data.site.name` | String | - | 站点名称 |
| `data.site.urls` | Array | - | 站点链接数组,元素为单个站点链接字符串 |
| `data.site.urls_raw` | String | - | 站点链接数组合并字符串,以英文半角符号 `,` 分割 |
| `data.site.first_url` | String | - | 站点第一链接 |
### 站点编辑
**POST** `/api/admin/site-edit`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------ | -------- | :--: | ---------------- |
| `id` | Number | 是 | 待编辑站点 ID |
| `name` | String | 是 | 待编辑站点新名称 |
| `urls` | String | 是 | 待编辑站点新链接 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------------------- | -------- | :----: | ----------------------------------------------- |
| `success` | Boolean | `true` | 站点编辑成功 |
| `data.site` | Object | - | 编辑站点的新数据 |
| `data.site.id` | Number | - | 站点 ID |
| `data.site.name` | String | - | 站点名称 |
| `data.site.urls` | Array | - | 站点链接数组,元素为单个站点链接字符串 |
| `data.site.urls_raw` | String | - | 站点链接数组合并字符串,以英文半角符号 `,` 分割 |
| `data.site.first_url` | String | - | 站点第一链接 |
### 站点删除
::: danger
此接口不推荐外部调用。
调用此接口前请务必核实站点 ID,一旦调用成功将删除该站点下所有相关数据。
:::
**POST** `/api/admin/site-del`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------------- | -------- | :--: | ------------------------------------------------------------------- |
| `id` | Number | 是 | 待删除站点 ID |
| `del_content` | Boolean | 否 | 是否删除站点所有数据,为 `false` 时仅删除站点配置而保留站点评论数据 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 站点删除成功 |
### 设置获取
**POST** `/api/admin/setting-get`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------ | -------- | :--: | -------------- |
| `id` | Number | 是 | 管理员用户 ID |
| `name` | String | 否 | 管理员用户昵称 |
| `url` | String | 否 | 管理员用户链接 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 设置获取成功 |
### 设置保存
**POST** `/api/admin/setting-save`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| ------ | -------- | :--: | -------------- |
| `id` | Number | 是 | 管理员用户 ID |
| `name` | String | 否 | 管理员用户昵称 |
| `url` | String | 否 | 管理员用户链接 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 设置保存成功 |
### 邮件发送
::: warning
页面收到评论、评论收到回复等满足需要发送邮件提醒条件时,后端将自动向目标地址发送邮件提醒,不需手动处理邮件发送。请勿滥用此接口。
:::
**POST** `/api/admin/send-mail`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| --------- | -------- | :--: | ---------- |
| `subject` | String | 是 | 邮件主题 |
| `body` | String | 是 | 邮件正文 |
| `to_addr` | String | 是 | 邮件收件人 |
**响应**
| 字段名 | 数据类型 | 默认 | 说明 |
| --------- | -------- | :----: | ------------ |
| `success` | Boolean | `true` | 邮件发送成功 |
### Artrans 接口
::: warning
此接口暂不稳定,请避免使用!
:::
**POST** `/api/admin/artransfer`
**参数**
| 字段名 | 数据类型 | 必需 | 说明 |
| --------- | -------- | :--: | ------------ |
| `type` | String | 是 | 导入数据类型 |
| `payload` | String | 否 | 导入数据 |
**响应** 无
-3
View File
@@ -1,3 +0,0 @@
# HTTP API
参考:<a href="/http-api.html" target="_blank">Artalk API 文档 (OpenAPI)</a>
-7
View File
@@ -1,7 +0,0 @@
# 插件开发
本页面内容已移动至 <https://artalk.js.org/develop/plugin.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/develop/plugin.html';
</script>
+18
View File
@@ -0,0 +1,18 @@
# Compatibility
## Browser Compatibility
The Artalk client production environment code is built using esbuild with a target of `es2015`. However, please note that the build process only handles syntax transpilation to comply with the `es2015` standard and does not address API compatibility (no polyfills are included).
If your project needs to support older browsers and devices, consider including global polyfills in your bundled application. We recommend using the [Polyfill.io](https://polyfill.io/) service, which dynamically returns the necessary polyfills based on the user's User-Agent. Alternatively, you can manually add polyfills using [core-js](https://github.com/zloirock/core-js) or [Babel](https://babeljs.io/).
Here is a list of modern features used by Artalk:
- [All ECMAScript 2015 (ES6) features](https://compat-table.github.io/compat-table/es6/)
- [Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API)
- [AbortController](https://developer.mozilla.org/en-US/docs/Web/API/AbortController)
- [Intersection Observer](https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API)
## Server Compatibility
The Artalk server program is developed in Golang and supports operating systems such as Linux, Windows, and macOS. The current Golang version for Artalk can be found in the [go.mod](https://github.com/ArtalkJS/Artalk/blob/master/go.mod#L3). For the minimum operating system requirements for Golang, refer to the [Go Wiki](https://go.dev/wiki/MinimumRequirements).
+3
View File
@@ -0,0 +1,3 @@
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md';
</script>
+50
View File
@@ -0,0 +1,50 @@
# Frontend Event
## Basic Events
| Event Name | Description |
| ------------------- | ------------------------------- |
| `created` | After initialization |
| `mounted` | After data loading |
| `updated` | After data update |
| `unmounted` | After destruction |
| `list-fetch` | During comment list request |
| `list-fetched` | After comment list request |
| `list-load` | Before comment loading |
| `list-loaded` | After comment loading |
| `list-failed` | When comment loading fails |
| `list-goto-first` | When comment list resets |
| `list-reach-bottom` | When comment list reaches bottom|
| `comment-inserted` | After comment insertion |
| `comment-updated` | After comment update |
| `comment-deleted` | After comment deletion |
| `comment-rendered` | After comment node rendering |
| `notifies-updated` | When unread messages change |
| `list-goto` | During comment jump |
| `page-loaded` | After page data update |
| `editor-submit` | When editor submits |
| `editor-submitted` | After editor submission |
| `user-changed` | When local user data changes |
| `sidebar-show` | When sidebar is shown |
| `sidebar-hide` | When sidebar is hidden |
Event declaration code: [@ArtalkJS/Artalk - src/types/event.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/types/event.ts)
## Adding Event Listeners
```js
artalk.on('list-loaded', () => {
alert('Comments have been loaded')
})
```
## Removing Event Listeners
```js
let foo = function () {
/* do something */
}
artalk.on('list-loaded', foo)
artalk.off('list-loaded', foo)
```
+199
View File
@@ -0,0 +1,199 @@
# Frontend API
Here are some of the main Artalk client APIs for operating the Artalk instance in frontend code.
For more detailed API information, you can browse the [TypeDoc documentation](https://artalk.js.org/typedoc/).
## Install Dependencies
Use your preferred package manager to install Artalk:
```bash
pnpm add artalk
# or using npm
npm install artalk
```
## Create Instance `init`
Calling this function creates and returns an instantiated Artalk object for subsequent operations.
<!-- prettier-ignore-start -->
```js
import Artalk from 'artalk'
const artalk = Artalk.init({
el: '#Comments',
pageKey: '/post/1',
pageTitle: 'About Introducing Artalk',
server: 'http://your_domain:8080',
site: 'Artalk Blog',
})
```
<!-- prettier-ignore-end -->
Calling this function will asynchronously send requests to the backend to:
1. Fetch frontend configuration
2. Fetch comment list
The `mounted` event is triggered after configuration and plugins are loaded.
The `list-loaded` event is triggered after the comment list is loaded.
> Note: The frontend UI configuration may be overridden. See: [UI Configuration](../guide/frontend/config.md).
## Release Resources `destroy`
Destroy the Artalk instance to release resources.
```js
const artalk = Artalk.init({ ... })
artalk.destroy()
```
Calling this function triggers the `unmounted` event. Releasing resources involves deleting DOM nodes mounted by Artalk and removing Artalk event listeners. After this function completes, the Artalk instance will no longer be usable.
In frameworks like Vue/React, make sure to call this function when the component is destroyed to prevent memory leaks:
```ts
import { onUnmounted } from 'vue'
onUnmounted(() => {
artalk.destroy()
})
```
## Update Configuration `update`
Modify the current Artalk configuration.
```js
const artalk = Artalk.init({ ... })
artalk.update({
// new configuration...
})
```
Calling this function will trigger the `updated` event.
Updating the configuration will not automatically refresh the comment list. You can continue to call the `artalk.reload()` function as needed.
Note that this function is a member method of an instantiated object, not a global function.
Frontend configuration reference: [Frontend Configuration](../guide/frontend/config.md)
## Reload `reload`
Reload the Artalk comment list data from the backend.
```js
const artalk = Artalk.init({ ... })
artalk.reload()
```
The `list-load` event is triggered before loading the list, and the `list-loaded` event is triggered after the loading is complete.
## Listen to Events `on`
Add Artalk event listeners.
```js
const artalk = Artalk.init({ ... })
artalk.on('list-loaded', (comments) => {
// 'comments' contains all comments on the current page (not just the comments fetched in this request)
console.log('Comments have been loaded: ', comments)
})
```
Refer to: [Frontend Event](./event.md).
## Remove Event Listeners `off`
Remove Artalk event listeners.
```js
const artalk = Artalk.init({ ... })
const handler = () => {
alert('Comments have been loaded')
}
artalk.on('list-loaded', handler)
artalk.off('list-loaded', handler)
```
## Trigger Events `trigger`
Trigger Artalk events.
```js
const artalk = Artalk.init({ ... })
artalk.trigger('list-loaded', [...])
```
## Load Plugins `use`
Load plugins using the `Artalk.use` function. Note that this function is a global function, not a method of an instantiated object. Plugins loaded through this function will be effective for all Artalk instances.
```js
import Artalk from 'artalk'
Artalk.use((ctx) => {
ctx.editor.setContent("Hello World")
})
const artalk = Artalk.init({ ... })
```
See: [Plugin Development](./plugin.md)
## Dark Mode `setDarkMode`
Toggle dark mode, which can be called in conjunction with the blog theme, such as when a user clicks a dark mode toggle button.
```js
const artalk = Artalk.init({ ... })
artalk.setDarkMode(true)
```
You can also set the initial dark mode by passing the `darkMode` parameter when calling `Artalk.init`.
```js
const artalk = Artalk.init({
// ...other configurations
darkMode: 'auto',
})
```
## View Count Widget `loadCountWidget`
See: [Page View Statistics](../guide/frontend/pv.md)
## Get Configuration `getConf`
Get the current Artalk configuration.
```js
const artalk = Artalk.init({ ... })
const conf = artalk.getConf()
```
## Get Mounted Element `getEl`
Get the DOM element that Artalk is currently mounted to.
```js
const artalk = Artalk.init({ ... })
const el = artalk.getEl()
```
+175
View File
@@ -0,0 +1,175 @@
# Import to Blog
## General Method
<<< @/code/quick-start/cdn.html
### When to execute `Artalk.init({})`?
- You can include JS and CSS resources anywhere, but ensure the JS is included before executing `Artalk.init({})`.
- Ensure `<div id="artalk"></div>` is present in the page before executing `Artalk.init({ el: '#artalk' })`.
## Hugo
Create the template file `/themes/YOUR_THEME/layouts/partials/comment/artalk.html`:
<!-- prettier-ignore-start -->
```html
<link href="/lib/artalk/Artalk.css" rel="stylesheet" />
<script src="/lib/artalk/Artalk.js"></script>
<!-- Artalk -->
<div id="Comments"></div>
<script>
Artalk.init({
el: '#Comments',
pageKey: '{{ .Permalink }}',
pageTitle: '{{ .Title }}',
server: '{{ $.Site.Params.artalk.server }}',
site: '{{ $.Site.Params.artalk.site }}',
// ...your additional configuration
})
</script>
```
<!-- prettier-ignore-end -->
Add the following to the appropriate place in your article template `/themes/YOUR_THEME/layouts/_default/single.html`:
```html
<div class="article-comments">{{- partial "comment/artalk" . -}}</div>
```
Modify the Hugo configuration file:
::: code-group
```toml [config.toml]
[params.artalk]
server = 'https://artalk.example.org'
site = 'Your Site Name'
```
```yaml [config.yaml]
params:
artalk:
server: 'https://artalk.example.org'
site: 'Your Site Name'
```
:::
## Hexo
Create `/themes/YOUR_THEME/layout/comment/artalk.ejs`:
```html
<link href="/lib/artalk/Artalk.css" rel="stylesheet" />
<script src="/lib/artalk/Artalk.js"></script>
<div id="Comments"></div>
<script>
var artalk = Artalk.init({
el: '#Comments',
pageKey: '<%= page.permalink %>',
pageTitle: '<%= page.title %>',
server: '<%= theme.comment.artalk.server %>',
site: '<%= theme.comment.artalk.site %>',
})
</script>
```
Modify the article template file, for example `/themes/YOUR_THEME/layout/post.ejs`:
```html
<div class="article-comments"><%- partial('comment/artalk') %></div>
```
Edit the theme configuration `/themes/YOUR_THEME/_config.yml`:
```yaml
comment:
artalk:
site: 'Your Site Name'
server: 'https://artalk.example.org'
```
::: tip
For NexT theme, you can install the [Artalk plugin for Hexo NexT theme](https://github.com/leirock/hexo-next-artalk)
:::
## VitePress
Refer to: [docs/.vitepress](https://github.com/ArtalkJS/Artalk/tree/master/docs/docs/.vitepress)
- Modify `config.ts` to include CSS resources
- Create `theme/Artalk.vue` component
- Register the component in `theme/index.ts`
- Use the component in `theme/Layout.vue`
Sample code: [docs/.vitepress/theme/Artalk.vue](https://github.com/ArtalkJS/Artalk/blob/master/docs/docs/.vitepress/theme/Artalk.vue)
## VuePress
(To be supplemented)
::: tip
Refer to: [Import to Frameworks](./import-framework.md)
:::
## Typecho
Modify the theme article template file, for example, `post.php`:
```php
<!-- CSS -->
<link href="/lib/artalk/Artalk.css" rel="stylesheet">
<!-- JS -->
<script src="/lib/artalk/Artalk.js"></script>
<!-- Artalk -->
<div id="Comments"></div>
<script>
Artalk.init({
el: '#Comments',
pageKey: '<?php $this->permalink() ?>',
pageTitle: '<?php $this->title() ?>',
server: '<Server Address>',
site: '<?php $this->options->title() ?>',
// ...your additional configuration
})
</script>
```
## WordPress
Modify the theme article template file, for example, `single.php`:
```php
<!-- CSS -->
<link href="/lib/artalk/Artalk.css" rel="stylesheet">
<!-- JS -->
<script src="/lib/artalk/Artalk.js"></script>
<!-- Artalk -->
<div id="Comments"></div>
<script>
Artalk.init({
el: '#Comments',
pageKey: '<?= addslashes(get_permalink()) ?>',
pageTitle: '<?= addslashes(get_the_title()) ?>',
server: '<Server Address>',
site: '<?= addslashes(get_bloginfo('name')) ?>',
// ...your additional configuration
})
</script>
```
+230
View File
@@ -0,0 +1,230 @@
# Import to Frameworks
## Install Artalk
Install Artalk using a package manager. It is recommended to use [pnpm](https://pnpm.io/zh/).
```bash
pnpm add artalk
```
## Vue
::: code-group
```vue [Vue 3]
<script lang="ts" setup>
import Artalk from 'artalk'
import { onMounted, onBeforeUnmount, ref } from 'vue'
import 'artalk/Artalk.css'
const el = ref<HTMLElement>()
let artalk: Artalk
onMounted(() => {
artalk = Artalk.init({
el: el.value,
pageKey: location.pathname,
pageTitle: `${document.title}`,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
})
onBeforeUnmount(() => {
artalk.destroy()
})
</script>
<template>
<div ref="el"></div>
</template>
```
```vue [Vue 3 + Vue Router]
<script lang="ts" setup>
import Artalk from 'artalk'
import { onMounted, onBeforeUnmount, ref, watch, nextTick } from 'vue'
import { useRouter } from 'vue-router'
import 'artalk/Artalk.css'
const el = ref<HTMLElement>()
const router = useRouter()
let artalk: Artalk
onMounted(() => {
artalk = Artalk.init({
el: el.value,
pageKey: router.currentRoute.value.path,
pageTitle: document.title,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
})
watch(
() => router.currentRoute.value.path,
(path) => {
nextTick(() => {
artalk.update({
pageKey: path,
pageTitle: document.title,
})
artalk.reload()
})
}
)
onBeforeUnmount(() => {
artalk.destroy()
})
</script>
<template>
<div ref="el"></div>
</template>
```
:::
## React
::: code-group
```tsx [React Hooks]
import { useCallback, useRef } from 'react'
import { useLocation } from 'react-router-dom'
import 'artalk/Artalk.css'
import Artalk from 'artalk'
const ArtalkComment = () => {
const { pathname } = useLocation()
const artalk = useRef<Artalk>()
const handleContainerInit = useCallback(
(node: HTMLDivElement | null) => {
if (!node) {
return
}
if (artalk.current) {
artalk.current.destroy()
artalk.current = undefined
}
artalk.current = Artalk.init({
el: node,
pageKey: pathname,
pageTitle: document.title,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
},
[pathname],
)
return <div ref={handleContainerInit}></div>
}
export default ArtalkComment
```
```jsx [React Class]
import React, { createRef } from 'react'
import 'artalk/Artalk.css'
import Artalk from 'artalk'
export default class ArtalkComponent extends React.Component {
el = createRef()
artalk = null
componentDidMount() {
this.artalk = Artalk.init({
el: this.el.current,
pageKey: location.pathname,
pageTitle: document.title,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
}
componentWillUnmount() {
this.artalk?.destroy()
}
render() {
return <div ref={this.el} />
}
}
```
:::
## SolidJS
```tsx
import { onCleanup, onMount } from 'solid-js'
import Artalk from 'artalk'
import 'artalk/Artalk.css'
const ArtalkComment = () => {
let el: HTMLDivElement
let artalk: Artalk
onMount(() => {
artalk = Artalk.init({
el: el,
pageKey: location.pathname,
pageTitle: document.title,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
onCleanup(() => {
artalk.destroy()
})
})
return <div ref={el} />
}
```
## Svelte
```html
<script>
import Artalk from 'artalk'
import { onMount, onDestroy } from 'svelte'
import 'artalk/Artalk.css'
let el
let artalk
onMount(() => {
artalk = Artalk.init({
el: el,
pageKey: location.pathname,
pageTitle: document.title,
server: 'http://localhost:8080',
site: 'Artalk Blog',
// ...
})
onDestroy(() => {
if (artalk) {
artalk.destroy()
}
})
})
</script>
<div bind:this="{el}"></div>
```
+40
View File
@@ -0,0 +1,40 @@
# Development Instructions
Welcome to the official Artalk development documentation, where you will find guidelines for building Artalk plugins and themes. Should you need to set up the Artalk development environment, please refer to the [Developer Contribution Guide](./contributing.md).
Thank you for your interest and support of Artalk. We deeply understand that the success of an open-source project relies on the contributions of every developer. Whether it is code, documentation, testing, or feedback, your participation is the driving force behind the project's continuous advancement. We sincerely invite you to join us in perfecting and enhancing Artalk.
## Index
- [Developer Contribution Guide](./contributing.md) ⭐️
**Frontend Interface**
- [Embed in Blog](./import-blog.md)
- [Embed in Framework](./import-framework.md)
- [Frontend API](./fe-api.md)
- [Frontend Events](./event.md)
- [Frontend Types](https://artalk.js.org/typedoc/)
- [Frontend Configuration](../guide/frontend/config.md)
**Plugin Development**
- [Plugin Development](./plugin.md)
- [Plugin Development Vite Integration](https://github.com/ArtalkJS/Artalk/blob/master/ui/plugin-kit/README.md)
**Backend Program**
- <a href="/http-api.html" target="_blank">HTTP API Documentation</a>
- [Environment Variables](../guide/env.md)
- [Configuration Files](../guide/backend/config.md)
**Other Content**
- [Compatibility](../develop/compatibility.md)
- [Changelog](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md)
- [i18n Multi-language Contribution Guide](../guide/frontend/i18n.md#贡献翻译)
- [Contributor Covenant Code of Conduct](https://github.com/ArtalkJS/Artalk/blob/master/CODE_OF_CONDUCT.md)
::: tip
Artalk is under active maintenance. Please be mindful of API version compatibility. Upgrades may include breaking changes, refer to the [Changelog](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md).
:::
+130
View File
@@ -0,0 +1,130 @@
# Plugin Development
## Developing with Vite
We provide an integrated Vite plugin, enabling you to effortlessly build Artalk plugins with out-of-the-box Vite configuration.
Reference Documentation: [@artalk/plugin-kit](https://github.com/ArtalkJS/Artalk/blob/master/ui/plugin-kit/README.md).
Additionally, we offer a template repository that you can fork to develop your plugins: [artalk-plugin-sample](https://github.com/ArtalkJS/artalk-plugin-sample).
Utilizing Vite in combination with the frontend ecosystem, you can develop Artalk plugins using any framework you prefer, such as Vue, React, Svelte, or SolidJS.
## `Artalk.use`
Extend Artalk's functionality using `Artalk.use`.
```js
import Artalk from 'artalk'
Artalk.use((ctx) => {
ctx.on('list-loaded', () => {
console.log('Comment list loaded')
ctx.getCommentNodes().forEach((node) => {
node.getEl().style.background = 'red'
})
})
})
Artalk.use((ctx) => {
let el = null
ctx.on('mounted', () => {
el = document.createElement('div')
document.body.appendChild(el)
console.log('Artalk instance mounted')
})
ctx.on('unmounted', () => {
el.remove()
console.log('Artalk instance unmounted')
})
})
const artalk = Artalk.init({ ... })
```
Please note:
- `Artalk.use` must be called before `Artalk.init` to take effect.
- Do not rely on the order of plugin loading; instead, listen for events to execute plugin logic.
- The `created` event is triggered once all plugins are loaded.
- The `mounted` event is triggered when the instance and configuration are fully loaded.
- The `unmounted` event is triggered when the Artalk instance is destroyed.
- The `updated` event is triggered when the configuration changes.
Within the use function, you can access Artalk's Context object via `ctx`.
### Configurable Plugin Options
In TypeScript, you can define a plugin with options using `ArtalkPlugin<T>`.
```ts
export interface DemoPluginOptions {
foo?: string
}
export const ArtalkDemoPlugin: ArtalkPlugin<DemoPluginOptions> = (ctx, options = {}) => {
console.log(options.foo)
}
```
Pass options when calling `Artalk.use`:
```ts
import { ArtalkDemoPlugin } from 'artalk-plugin-demo'
Artalk.use(ArtalkDemoPlugin, { foo: 'bar' })
```
## Context API
The Context object contains Artalk's contextual information.
| Member | Description |
| -------------------- | ----------------------- |
| `ctx.getEl` | Get container element |
| `ctx.getConf` | Get configuration |
| `ctx.updateConf` | Update configuration |
| `ctx.watchConf` | Watch configuration |
| `ctx.setDarkMode` | Set dark mode |
| `ctx.getApi` | Get API client object |
| -- | -- |
| `ctx.fetch` | Fetch comment data |
| `ctx.reload` | Reload comment list |
| `ctx.getComments` | Get all comment data |
| `ctx.getCommentNodes`| Get all comment nodes |
| -- | -- |
| `ctx.on` | Add event listener |
| `ctx.off` | Remove event listener |
| `ctx.trigger` | Trigger event |
| -- | -- |
| `ctx.get` | Get dependency |
| `ctx.inject` | Inject dependency |
::: warning
The Context API is currently unstable and subject to change. Please refer to the CHANGELOG when upgrading.
:::
Reference: [@artalk/src/types/context.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/types/context.ts)
Artalk includes comprehensive TypeScript type definitions, allowing you to explore the API through editor autocompletion.
## Sample Plugins
Below is a list of externally maintained Artalk plugins:
| Plugin | Description |
| -------------------------------------------------------------------------------------------- | ----------------------- |
| [artalk-plugin-sample](https://github.com/ArtalkJS/artalk-plugin-sample) | Sample Plugin |
| [@artalk/plugin-katex](https://github.com/ArtalkJS/Artalk/tree/master/ui/plugin-katex) | LaTeX Formula Plugin |
| [@artalk/plugin-auth](https://github.com/ArtalkJS/Artalk/tree/master/ui/plugin-auth) | Auth Plugin (SolidJS) |
| [@artalk/plugin-lightbox](https://github.com/ArtalkJS/Artalk/tree/master/ui/plugin-lightbox) | Basic Image Lightbox |
Additionally, many plugins are implemented within Artalk itself, which you can reference for developing your own plugins:
[@ArtalkJS/Artalk - src/plugins](https://github.com/ArtalkJS/Artalk/tree/master/ui/artalk/src/plugins)
## Backend Plugin Development
【TODO】
+3
View File
@@ -0,0 +1,3 @@
# About Us
【TODO】
+403
View File
@@ -0,0 +1,403 @@
# Multi-channel Notifications
Artalk supports sending administrator notifications through its multi-channel notification feature in various ways.
Supported platforms include **Telegram**, **Feishu**, **DingTalk**, **Bark**, **Slack**, and **LINE**, with the ability to enable multiple methods simultaneously.
You can modify these configurations in the settings interface of the [Dashboard](../frontend/sidebar.md#Settings) or via the [configuration file](../backend/config.md#multi-channel-notifications-admin-notify) or [environment variables](../env.md#multi-channel-notifications).
## Configuration File
The complete `admin_notify` configuration is as follows:
::: details Click to reveal
```yaml
# Multi-channel Notifications
admin_notify:
# Notification Template
notify_tpl: default
noise_mode: false
# Email notification for administrators
email:
enabled: true # Disable email notifications for administrators when using other push methods
mail_subject: '[{{site_name}}] Your article "{{page_title}}" has a new reply'
mail_tpl: ''
# Telegram
telegram:
enabled: false
api_token: ''
receivers:
- 7777777
# Feishu
lark:
enabled: false
webhook_url: ''
# DingTalk
ding_talk:
enabled: false
token: ''
secret: ''
# Bark
bark:
enabled: false
server: http://day.app/xxxxxxx/
# Slack
slack:
enabled: false
oauth_token: ''
receivers:
- CHANNEL_ID
# LINE
line:
enabled: false
channel_secret: ''
channel_access_token: ''
receivers:
- USER_ID_1
- GROUP_ID_1
# WebHook
webhook:
enabled: false
url: ''
```
:::
## Email Notifications
Send message notifications to administrators via email.
```yaml
admin_notify:
enabled: true # Disable email notifications for administrators when using other push methods
mail_subject: '[{{site_name}}] Your article "{{page_title}}" has a new reply'
mail_tpl: ''
```
You can disable email notifications when using other push methods.
Before doing this, you need to configure the global email sending functionality: [refer here](./email.md).
### Administrator Email Template
- The `mail_subject` configuration item is the email subject sent to the administrator.
- The `mail_tpl` configuration item specifies the email template for the administrator (fill in the email template file path).
(If this item is empty, it will inherit the `email.mail_tpl` configuration item).
## Telegram
```yaml
admin_notify:
# Telegram
telegram:
enabled: true
api_token: ''
receivers:
- 7777777
```
- `api_token`: The API token for the TG Bot.
- `receivers`: The numeric IDs of the message recipients, multiple recipients can be set.
### Creating a TG Bot
Search for `@BotFather`, reply with `/newbot`, and follow the prompts to create a new TG bot.
![](/images/notify/tg-1.png)
The red text is the `api_token` you need to fill in Artalk's configuration.
Fill in the `receivers` field with the numeric IDs of the accounts that need to receive messages. You can use `@RawDataBot` to get these IDs, as shown:
![](/images/notify/tg-2.png)
For more details, refer to: [Bots: An introduction for developers - Telegram](https://core.telegram.org/bots)
::: tip
Given the complex network environment, if you need to use a proxy, configure the environment variable before starting Artalk, for example:
```sh
export https_proxy=http://127.0.0.1:7890
```
:::
## Feishu
```yaml
admin_notify:
# Feishu
lark:
enabled: true
webhook_url: ''
```
- `webhook_url`: The WebHook address obtained when creating the group bot.
### Creating a Group Bot
Click the plus sign at the top to create a new group:
![](/images/notify/lark-1.png)
Find "Group Settings" on the right, select "Group Bot", click "Add Bot", choose "Custom Bot", and follow the prompts to create it.
<img src="/images/notify/lark-2.png" width="700px">
Copy the WebHook address as shown above and modify Artalk's `webhook_url` configuration.
<img src="/images/notify/lark-3.png" width="400px">
For more details, refer to: [Feishu Help Center Documentation](https://www.feishu.cn/hc/zh-CN/articles/360024984973)
## DingTalk
```yaml
admin_notify:
# DingTalk
ding_talk:
enabled: true
token: ''
secret: ''
```
Refer to: [DingTalk Open Documentation](https://open.dingtalk.com/document/robots/custom-robot-access)
## Bark
```yaml
admin_notify:
# Bark
bark:
enabled: true
server: http://day.app/xxxxxxx/
```
[Bark](https://github.com/Finb/Bark) is an open-source iOS app that [supports self-hosting](https://github.com/Finb/bark-server), allowing you to easily push messages to your iOS device.
You can search and download it from the App Store and get the `server` configuration item to fill in Artalk:
<img src="/images/notify/bark.png" width="700px">
## Slack
```yaml
admin_notify:
# Slack
slack:
enabled: true
oauth_token: ''
receivers:
- CHANNEL_ID
```
## LINE
```yaml
admin_notify:
# LINE
line:
enabled: true
channel_secret: ''
channel_access_token: ''
receivers:
- USER_ID_1
- GROUP_ID_1
```
## Notification Template
```yaml
admin_notify:
notify_tpl: default
```
The `admin_notify.notify_tpl` configuration item can be set to a custom notification template file path. The default notification template is:
```
@{{reply_nick}}:
{{reply_content}}
{{link_to_reply}}
```
The available variables are the same as in the email template, refer to: [Email Template](./email.md#邮件模板)
## Notify Pending Comments `notify_pending`
```yaml
admin_notify:
notify_pending: false
```
`notify_pending` is turned off by default. When set to `false`, pending comments will not send notifications. You can view all pending comments in the Dashboard.
## Noise Mode `noise_mode`
```yaml
admin_notify:
noise_mode: false
```
`noise_mode` is turned off by default. When set to `false`, only messages directed to the administrator will send notifications. For example, communication between "User A" and "User B" will not notify the administrator.
Note: When `moderator.pending_default` is set to `true`, noise_mode is always enabled.
## WebHook Callback
When WebHook is enabled, a new comment will send a **POST** request with `application/json` type Body data to the specified WebHook address.
You can write your own server-side code to handle requests from Artalk.
**Artalk Configuration File**
```yaml
admin_notify:
webhook:
enabled: true
url: http://localhost:8080/
```
**Body Data Content**
`application/json` type
| Key | Description | Type | Remarks |
| ---------------- | ----------------- | ------ | ----------------------------------------- |
| `notify_subject` | Notification Title | String | Corresponds to the admin_notify.notify_subject configuration item |
| `notify_body` | Notification Content | String | Rendered according to the admin_notify.notify_tpl template |
| `comment` | Comment Content | Object | New comment data object |
| `parent_comment` | Target of Comment Reply | Object | If it's a root comment, the value is null |
**Body Data Sample**
```js
{
"notify_subject": "",
"notify_body": "@TestUser:\n\nTestContent\n\nhttps://127.0.0.1/index.html?atk_comment=1057",
"comment": {
"id": 1057,
"content": "TestContent",
"user_id": 226,
"nick": "TestUser",
"email_encrypted": "654236c1e78i4c09a17c4869c9d43910",
"link": "https://qwqaq.com",
"ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 12_4_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.64 Safari/537.36",
"date": "2022-05-23 17:00:23",
"is_collapsed": false,
"is_pending": false,
"is_pinned": false,
"is_allow_reply": false,
"rid": 0,
"badge_name": "",
"badge_color": "",
"visible": true,
"vote_up": 0,
"vote_down": 0,
"page_key": "/index.html",
"page_url": "https://127.0.0.1/index.html",
"site_name": "ArtalkDocs"
},
"parent_comment": null
}
```
**Node.js Express Handling Example**
```js
const express = require('express')
const app = express()
app.use(express.json()) // Use JSON middleware
app.post('/', (request, response) => {
console.log(request.body)
const notifySubject = request.body.notify_subject
const notifyBody = request.body.notify_body
console.log(notifySubject, notifyBody)
response.send(request.body)
})
app.listen(8080)
```
**Node.js HTTP Handling Example**
```js
const http = require('http')
const requestListener = (req, res) => {
// receive json request
let body = ''
req.on('data', (data) => {
body += data
})
req.on('end', () => {
let json = ''
try {
json = JSON.parse(body)
} catch {}
// do something with json
console.log(json)
res.end()
})
res.writeHead(200)
res.end('Hello, World!')
}
const server = http.createServer(requestListener)
server.listen(8080)
```
**PHP Laravel Handling Example**
```php
Route::get('/', function (Request $request) {
$data = $request->json()->all();
$notify_subject = $data["notify_subject"];
$notify_body = $data["notify_body"];
});
```
**Golang net/http Handling Example**
```go
package main
import (
"encoding/json"
"log"
"net/http"
)
type ArtalkNotify struct {
NotifySubject string `json:"notify_subject"`
NotifyBody string `json:"notify_body"`
Comment interface{} `json:"comment"`
ParentComment interface{} `json:"parent_comment"`
}
func webhookHandler(rw http.ResponseWriter, req *http.Request) {
decoder := json.NewDecoder(req.Body)
var notify ArtalkNotify
err := decoder.Decode(&notify)
if err != nil {
panic(err)
}
log.Println(notify.NotifyBody)
}
func main() {
http.HandleFunc("/webhook", webhookHandler)
log.Fatal(http.ListenAndServe(":8080", nil))
}
```
+159
View File
@@ -0,0 +1,159 @@
# Captcha
Artalk comes with a built-in image captcha feature, allowing you to configure operation frequency limits that activate the captcha when exceeded.
Additionally, you can integrate various verification service providers to gain diversified verification functionality.
Currently, Artalk supports: Turnstile, reCAPTCHA, hCaptcha, and Geetest.
You can modify these settings in the [Dashboard](../frontend/sidebar.md#Settings) or via the [configuration file](./config.md#captcha) or [environment variables](../env.md#captcha).
## Configuration File
The full `captcha` configuration is as follows:
```yaml
# Captcha
captcha:
enabled: true # Master switch
always: false # Always require captcha
captcha_type: image # Type of captcha
action_limit: 3 # Number of actions required to activate captcha
action_reset: 60 # Timeout to reset action counter (unit: s, set to -1 to never reset)
# Turnstile
# (https://www.cloudflare.com/products/turnstile/)
turnstile:
site_key: ''
secret_key: ''
# reCAPTCHA
# (https://www.google.com/recaptcha/about/)
recaptcha:
site_key: ''
secret_key: ''
# hCaptcha (https://www.hcaptcha.com/)
hcaptcha:
site_key: ''
secret_key: ''
# Geetest (https://www.geetest.com)
geetest:
captcha_id: ''
captcha_key: ''
```
- **always**: When set to `true`, captcha is always required.
- **captcha_type**: Type of captcha, options include: `image`, `turnstile`, `recaptcha`, `hcaptcha`, `geetest`.
- **action_limit**: The number of actions required to activate the captcha.
- **action_reset**: When the time exceeds this value, the action counter resets. Unit is seconds; set to `-1` to never reset.
Note: When `always` is enabled, `action_limit` and `action_reset` configurations are ignored.
## Configuration Examples
### Example 1
Within a 60-second time frame, if the number of actions exceeds 3, captcha will be required:
```yaml
captcha:
action_limit: 3
action_reset: 60
```
The counter will automatically reset after 60 seconds, allowing for 3 more actions without requiring a captcha.
### Example 2
Regardless of the time frame, if the number of actions from an IP address exceeds 5, captcha will be required:
```yaml
captcha:
action_limit: 5
action_reset: -1
```
### Example 3
Always require captcha, regardless of the number of actions:
```yaml
captcha:
always: true
```
## Definition of Actions
Each "comment, vote, image upload, password verification" by an IP address counts as an "action."
## Turnstile
[Turnstile](https://www.cloudflare.com/zh-cn/products/turnstile/) is a verification service from Cloudflare. You can obtain the `site_key` and `secret_key` from the CF dashboard, then fill in these keys in the Artalk settings and change `captcha_type` to `turnstile`.
Illustrations:
<img src="/images/captcha/cf-turnstile-1.png" width="400px">
<img src="/images/captcha/cf-turnstile-2.png" width="400px">
Corresponding configuration file:
```yaml
captcha:
# Omit other configurations...
captcha_type: turnstile
turnstile:
site_key: ''
secret_key: ''
```
## reCAPTCHA
[reCAPTCHA](https://developers.google.com/recaptcha) is a verification service from Google, and Artalk supports reCAPTCHA v3. You can obtain the `site_key` and `secret_key` from the Google developer dashboard, then fill in these keys in the Artalk settings and change `captcha_type` to `recaptcha`.
Corresponding configuration file:
```yaml
captcha:
# Omit other configurations...
captcha_type: recaptcha
recaptcha:
site_key: ''
secret_key: ''
```
Note: Accessing Google APIs from within China may require configuring a system proxy.
Google provides test keys for reCAPTCHA: [see here](https://developers.google.com/recaptcha/docs/faq?hl=en#id-like-to-run-automated-tests-with-recaptcha.-what-should-i-do).
## hCaptcha
[hCaptcha](https://www.hcaptcha.com/) is a verification service. You can obtain the `site_key` and `secret_key` from its official website, then fill in these keys in the Artalk settings and change `captcha_type` to `hcaptcha`.
Corresponding configuration file:
```yaml
captcha:
# Omit other configurations...
captcha_type: hcaptcha
hcaptcha:
site_key: ''
secret_key: ''
```
hCaptcha provides test keys: [see here](https://docs.hcaptcha.com/#integration-testing-test-keys).
## Geetest
Artalk supports integrating [Geetest](https://www.geetest.com/adaptive-captcha) for advanced behavior verification.
First, register an account on the Geetest website to obtain the `captcha_id` and `captcha_key`, then modify the configuration in the Artalk settings and change `captcha_type` to `geetest`.
Corresponding configuration file:
```yaml
captcha:
# Omit other configurations...
captcha_type: geetest
geetest:
captcha_id: ''
captcha_key: ''
```
+360
View File
@@ -0,0 +1,360 @@
# Configuration File
## Easy Configuration
It is recommended to modify the configuration through the graphical interface in the sidebar "[Dashboard](../frontend/sidebar.md)" without manually editing the configuration file.
## Environment Variables
You can configure via environment variables, refer to the documentation: [Environment Variables](../env.md).
## Specifying the Configuration File Path
By default, Artalk uses `artalk.yml` in the working directory as the configuration file. You can specify a specific file using the `-c` parameter:
```bash
artalk -c ./conf.yml
```
## Obtaining a Template Configuration File
You can refer to a "complete configuration file": [artalk.example.zh-CN.yml](https://github.com/ArtalkJS/Artalk/blob/master/conf/artalk.example.zh-CN.yml)
### Generate Configuration File Using the `gen` Command
Artalk provides the `gen` command, allowing you to quickly generate a new configuration file:
```bash
artalk gen conf -lang zh-CN ./artalk.yml
```
### Download Configuration File via Command Line
```bash
wget -O artalk.yml https://raw.githubusercontent.com/ArtalkJS/Artalk/master/conf/artalk.example.zh-CN.yml
```
## Encryption Key `app_key`
Before starting Artalk, you need to configure an `app_key` for securely encrypting site content:
```yaml
app_key: <any random characters>
```
## Language `locale`
Set the language for Artalk. Follows the Unicode BCP 47 standard, with the default being "zh-CN" (Simplified Chinese).
```yaml
locale: zh-CN
```
For details, refer to: [Multilingual](../frontend/i18n.md)
## Database `db`
Artalk supports connecting to various databases, including SQLite, MySQL, PostgreSQL, and SQL Server. The configurations are as follows:
#### SQLite
SQLite is a lightweight database that stores data in a single file, requiring no additional running programs. It is especially suitable for small sites, such as personal blogs.
```yaml
db:
type: sqlite
file: ./data/artalk.db
```
#### MySQL / PostgreSQL / SQL Server
Modify `type` to your database type:
```yaml
db:
type: mysql # sqlite, mysql, pgsql, mssql
name: artalk # Database name
host: localhost # Address
port: 3306 # Port
user: root # Username
password: '' # Password
charset: utf8mb4 # Charset
table_prefix: '' # Table prefix (e.g., "atk_")
ssl: false # Enable SSL
prepare_stmt: true # Prepared statements
```
The data tables will be automatically created when Artalk starts, no additional operation is required.
#### Database Connection String (DSN)
If needed, you can manually configure `db.dsn` to specify the database connection string, for example:
```yaml
db:
type: mysql
dsn: mysql://myuser:mypassword@localhost:3306/mydatabase?tls=skip-verify
```
For more details, refer to: [@go-sql-driver/mysql:README.md](https://github.com/go-sql-driver/mysql)
## Server `http`
```yaml
http:
# Request body size limit (unit: MB)
body_limit: 100
# Proxy header name (when using CDN, fill in `X-Forwarded-For` to get the user's real IP)
proxy_header: ""
```
## Admin Users `admin_users`
You need to configure administrator accounts to manage site content through the "[Dashboard](../frontend/sidebar.md)".
Artalk supports multiple sites, allowing you to create multiple administrator accounts and assign sites to them, enabling your friends to share the same backend program.
For details, refer to: [Admin Users × Multi-site](./multi-site.md)
## Trusted Domains `trusted_domains`
```yaml
trusted_domains:
- https://frontend.domainA.com
- https://frontend.domainB.com
```
Only the domains in the list are allowed to access the backend API, restricting cross-domain requests from external domains.
::: tip
You need to add the URL address of the "frontend page" to the trusted domains list.
If it's not the default 80/443 port, include the port number, e.g., `https://example.com:8080`.
:::
In the sidebar [Dashboard](../frontend/sidebar.md#控制中心), under the "Site" tab - select the site and "Modify URL", fill in the site URL to achieve the same setting effect; to add multiple URLs, separate them with commas `,`. After modification, manually restart Artalk.
The default site address `ATK_SITE_URL` configuration item will also be automatically added to the trusted domains list.
Additionally, you can configure trusted domains via the environment variable `ATK_TRUSTED_DOMAINS` when starting, for example:
```bash
ATK_TRUSTED_DOMAINS="https://a.com https://b.org" artalk server
```
Note that environment variables will override the settings in the configuration file.
Technical details: `trusted_domains` configuration controls cross-origin requests by setting the HTTP response header `Access-Control-Allow-Origin` (refer to: [W3C Cross-Origin Resource Sharing](https://fetch.spec.whatwg.org/#http-cors-protocol) / [OWASP Security Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html)).
## Default Site `site_default`
If you think you won't use the multi-site feature of Artalk, you can directly set this item to your site name, for example:
```yaml
site_default: Artalk Official Website
```
Then use this site name in the frontend:
```js
Artalk.init({ site: 'Artalk Official Website' })
```
This way, you don't need to manually create the site in the sidebar [Dashboard](../frontend/sidebar.md#控制中心).
## Frontend Configuration `frontend`
In Artalk's configuration file `artalk.yml`, you can configure the `frontend` field to control the frontend interface, for example:
```yaml
frontend:
placeholder: Type content...
noComment: "Silence is golden"
sendBtn: Send Comment
emoticons: 'https://raw.githubusercontent.com/ArtalkJS/Emoticons/master/grps/default.json'
# ----- Omitted -------
# Keep the same as the frontend configuration item name
```
A complete backend `frontend` field configuration file can be referred to: [artalk.example.zh-CN.yml](https://github.com/ArtalkJS/Artalk/blob/master/conf/artalk.example.zh-CN.yml)
## Email Notifications `email`
Configure email notifications to notify the target user of replies via email. You can customize the sender name, title, template, etc.
For details, refer to: [Backend · Email Notifications](./email.md)
## Multi-channel Notifications `admin_notify`
You can configure various message sending methods, such as Feishu, Telegram, etc., to notify administrators when new comments are received.
For details, refer to: [Backend · Multi-channel Notifications](./admin_notify.md)
## Comment Moderation `moderator`
Configure comment moderation to automatically intercept spam comments.
For details, refer to: [Backend · Comment Moderation](./moderator.md)
## Captcha `captcha`
Supports image and slide captchas to limit request frequency.
For details, refer to: [Backend · Captcha](./captcha.md)
## Cache `cache`
To save memory resources, caching is disabled by default. If you have high performance requirements for your site, enable it manually. You can also connect to external cache servers, supporting Redis and Memcache.
```yaml
cache:
enabled: true # Enable cache (default is off)
type: builtin # Supports redis, memcache, builtin (built-in cache)
expires: 30 # Cache expiration time (unit: minutes)
warm_up: false # Warm up cache on program startup
server: '' # Connect to cache server (e.g., "localhost:6379")
```
- **warm_up**: Cache warm-up feature. Set to `true`, it will immediately cache all database content when Artalk starts. If you have a large number of comments, this may extend the startup time.
- **type**: Cache type, defaults to `builtin`. Options: `redis`, `memcache`, `builtin`.
Note: If you modify the database content outside the Artalk program, you need to refresh the Artalk cache to update it.
---
Redis authentication and database configuration:
```yaml
# Cache
cache:
# Omit other configurations...
redis:
network: tcp # Connection method (tcp or unix)
username: '' # Username
password: '' # Password
db: 0 # Use database 0
```
<!-- Technical details: [Artalk Cache Mechanism Sequence Diagram.png](/images/artalk/artalk-cache.png) -->
<!-- ![](/images/artalk/artalk-cache.png) -->
## Listening Address `host`
The default HTTP port for Artalk is 23366. You can specify it in the configuration file:
```yaml
host: '0.0.0.0'
port: 23366
```
Configuring the `host` listening address to `0.0.0.0` will expose the Artalk service to the entire network.
If you want Artalk to be accessible only locally, configure `host` to `127.0.0.1`.
When starting Artalk via the command line, you can specify the address and port using the `--host` and `--port` parameters, for example:
```bash
artalk server --host 127.0.0.1 --port 8080
```
## Encrypted Transmission `ssl`
```yaml
ssl:
enabled: true
cert_path: ''
key_path: ''
```
You can configure this item to upgrade HTTP to HTTPS, encrypting data transmission via SSL.
- `cert_path`: Path to the SSL certificate public key file.
- `key_path`: Path to the SSL certificate private key file.
You can also directly reverse proxy the Artalk local server and then enable HTTPS in, for example, Nginx.
## Time Zone Configuration `timezone`
```yaml
timezone: Asia/Shanghai
```
Fill in the time zone where you are located, corresponding to the IANA database time zone name, refer to: [Wikipedia](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) / [RFC-6557](https://www.rfc-editor.org/rfc/rfc6557.html).
```
UTC+08:00 Asia/Shanghai
UTC+09:00 Asia/Tokyo
UTC-07:00 America/Los_Angeles
UTC-04:00 America/New_York
```
## Login Timeout `login_timeout`
This value sets the validity period of the administrator account login JWT token, in seconds.
For example, valid for 3 days:
```yaml
login_timeout: 259200
```
## Log Configuration `log`
When logging is enabled, system errors and other information will be recorded in the specified file.
```yaml
log:
enabled: true # Master switch
filename: ./data/artalk.log # Log file path
```
Logs are in JSON format, which can be viewed using the `tail` command combined with the `jq` tool in Linux:
```bash
tail -f ./data/artalk.log | jq
```
If you are a Grafana user, you can use Loki and Promtail to collect and query logs.
## Debug Mode `debug`
Set `debug` to `true` to enable debug mode.
```yaml
debug: true
```
## Working Directory `-w` Parameter
If the working directory is not specified, Artalk will use the "directory where the program is started" as the working directory.
```bash
pwd # Display the current directory path
```
Use the `-w` parameter to specify the working directory, which is usually an "absolute path", for example:
```bash
artalk -w /root/artalk -c ./conf.yml
```
Note: The relative path of `-c` will be based on the path of `-w`, and Artalk will read `/root/artalk/conf.yml` as the configuration file.
Additionally, the "relative path" used in the "configuration file" will also be based on the "working directory".
For example, if the configuration in `conf.yml` is:
```yaml
test_file: ./data/artalk.log
```
It will read `/root/artalk/data/artalk.log`.
::: tip
Configuration file related code: [/internal/config/config.go](https://github.com/ArtalkJS/Artalk/blob/master/internal/config/config.go)
Go to: [Frontend Configuration](../frontend/config.md)
:::
+144
View File
@@ -0,0 +1,144 @@
# Daemon Process
## Systemd
Prerequisites:
- The Artalk binary file, which can be downloaded from [GitHub Release](https://github.com/ArtalkJS/Artalk/releases)
- `systemctl --version` 232 or later
- `sudo` administrator privileges
Move Artalk to `$PATH`, for example:
```bash
sudo mv artalk /usr/bin/
```
Test if it works:
```bash
artalk version
```
Create a user group named `artalk`:
```bash
sudo groupadd --system artalk
```
Create a user named `artalk` with a writable home directory:
```bash
sudo useradd --system \
--gid artalk \
--create-home \
--home-dir /var/lib/artalk \
--shell /usr/sbin/nologin \
--comment "Artalk server" \
artalk
```
If you have the Artalk configuration file, ensure that the newly created `artalk` user has read permissions.
Create the service file:
```bash
sudo vim /etc/systemd/system/artalk.service
```
```ini
[Unit]
Description=Artalk
Documentation=https://artalk.js.org
After=network.target network-online.target
Requires=network-online.target
[Service]
Type=simple
User=artalk
Group=artalk
ExecStart=/usr/bin/artalk server -w /var/lib/artalk -c /etc/artalk/artalk.yml
ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s QUIT $MAINPID
TimeoutStopSec=5s
LimitNOFILE=1048576
LimitNPROC=512
PrivateTmp=true
ProtectSystem=full
AmbientCapabilities=CAP_NET_ADMIN CAP_NET_BIND_SERVICE
[Install]
WantedBy=multi-user.target
```
Carefully check `ExecStart` and `ExecReload`. Ensure that the binary file location and program startup parameters are correct.
For example, change the path of the `-c` parameter to specify the configuration file and the `-w` parameter to change the working directory.
Note that all relative paths in the configuration file are based on the working directory. For example, the `./data/` folder in the configuration file, if the startup parameter is `-w /var/lib/artalk`, will read from the `/var/lib/artalk/data/` directory. Ensure the files in this directory are readable and writable by the created `artalk` account.
After saving the service file, you can set the service to start automatically:
```bash
sudo systemctl daemon-reload
sudo systemctl enable --now artalk
```
Verify that the service is running correctly:
```bash
systemctl status artalk
```
Some common commands:
- Start the service: `systemctl start artalk`
- Stop the service: `systemctl stop artalk`
- Check the status: `systemctl status artalk`
- View logs: `journalctl -u artalk --no-pager | less +G`
## Tmux
tmux will create a persistent command-line session that remains in the background after SSH or tty disconnection.
Note: tmux sessions will be cleared after the server shuts down or restarts, and you will need to manually rerun the program.
1. Create a session `tmux new -s artalk`
2. Run the program `./artalk server`
Reconnect to the session: `tmux attach -t artalk`
View all sessions: `tmux ls`
## Supervisor
Taking Baota Panel as an example: Open the "Software Store," search for and install the "Supervisor Manager":
![](/images/baota-supervisor/0.png)
After installation, open the plugin and click "Add Daemon":
![](/images/baota-supervisor/1.png)
> - Startup User: `root` or others
> - Working Directory: Click the icon on the right and select the Artalk directory
> - Startup Command: `./artalk server`
## Docker
Update the Docker container's [Restart Policy](https://docs.docker.com/config/containers/start-containers-automatically/#use-a-restart-policy) to achieve the effect of process daemonization.
```bash
docker update --restart=unless-stopped artalk
```
## Docker Compose
Add the `restart: unless-stopped` policy to the service in the `docker-compose.yml` file:
```diff
version: '3'
services:
artalk:
+ restart: unless-stopped
```
+101
View File
@@ -0,0 +1,101 @@
# Docker
Artalk provides Docker images for the backend program to accelerate the deployment process and offer a good deployment experience.
The [Docker Hub](https://hub.docker.com/r/artalk/artalk-go) image versions are kept in sync with the [Releases](https://github.com/ArtalkJS/Artalk/releases) in the code repository.
## Pulling the Image
```bash
docker pull artalk/artalk-go
```
## Creating the Container
::: tip
It is recommended to use Docker Compose. Refer to the steps on the [Program Deployment](../deploy) page.
:::
## Generating the Configuration File
```bash
docker run -it -v $(pwd)/data:/data --rm artalk/artalk-go gen config data/artalk.yml
```
## Restart
After modifying the configuration file, you need to restart to apply the changes.
```bash
# Docker Compose
docker-compose restart
# Docker
docker restart artalk
```
## Stop
```bash
# Docker Compose
docker-compose stop
# Docker
docker stop artalk
```
## Upgrade
Delete the existing container, pull the latest image, and then recreate the container.
### Docker Compose
```bash
docker-compose down
docker-compose pull
docker-compose up -d
```
### Docker
```bash
docker stop artalk
docker rm artalk
docker pull artalk/artalk-go
```
::: tip
For breaking changes, please refer to the update notes in the version changelog: [CHANGELOG.md](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md)
:::
## Testing Version
The nightly image is a testing version that is updated daily and automatically built from the latest code in the repository.
```bash
docker pull artalk/artalk-go:nightly
```
## Historical Versions
Images are automatically built and released with the repository tags. You can pull images of different versions.
```bash
docker pull artalk/artalk-go:<version>
```
## Entering the Container
```bash
# Docker Compose
docker-compose exec artalk bash
# Docker
docker exec -it artalk bash
```
## Multi-Platform Compatibility
The Docker image currently only provides builds for x86 and arm64 architectures. For more platform architectures, please download the binary build and deploy it using the [Binary Deployment](../deploy.md#binary) method.
+325
View File
@@ -0,0 +1,325 @@
# Email Notifications
Artalk supports sending email notifications to users through various methods such as SMTP protocol, Alibaba Cloud Email Service, and system Sendmail command invocation.
You can modify this configuration in the settings interface of the [Dashboard](../frontend/sidebar.md#settings), or configure it through [configuration files](./config.md#email-notifications-email) or [environment variables](../env.md#email-notifications).
## Configuration File
The complete `email` configuration is as follows:
```yaml
# Email Notifications
email:
enabled: false # Master Switch
send_type: smtp # Sending Method [smtp, ali_dm, sendmail]
send_name: '{{reply_nick}}' # Sender's Nickname
send_addr: example@qq.com # Sender's Address
mail_subject: '[{{site_name}}] You have received a reply from @{{reply_nick}}'
mail_tpl: default # Email Template File
smtp:
host: smtp.qq.com
port: 587
username: example@qq.com
password: ''
ali_dm: # https://help.aliyun.com/document_detail/29444.html
access_key_id: '' # Access Key ID issued by Alibaba Cloud
access_key_secret: '' # Secret key for encryption
account_name: example@example.com # Sending address configured in the management console
```
### Choosing a Sending Method
The configuration item `enabled` enables email notifications, and `send_type` is used to select the sending method. Options are: `smtp`, `ali_dm`, `sendmail`.
```yaml
email:
enabled: true
send_type: smtp # Sending Method
# Other configurations omitted...
smtp:
# SMTP Configuration...
ali_dm:
# Alibaba Cloud Push Configuration...
```
### SMTP Configuration
```yaml
# Email Notifications
email:
enabled: true
send_type: smtp # Selecting smtp
smtp:
host: smtp.qq.com
port: 587
username: example@qq.com
password: ''
```
### Alibaba Cloud Push Configuration
```yaml
email:
enabled: true
send_type: ali_dm # Selecting ali_dm
ali_dm:
access_key_id: '' # Access Key ID issued by Alibaba Cloud
access_key_secret: '' # Secret key for encryption
account_name: example@example.com # Sending address configured in the management console
```
Refer to: [Alibaba Cloud Official Documentation](https://help.aliyun.com/document_detail/29444.html)
## Comment Replies
The email will include a comment reply button, linking to the given PageKey on the frontend. If your `pageKey` configuration item is a "relative path" of the page, you need to set a URL for your site in the "[Dashboard](../frontend/sidebar.md#dashboard)" - "Site":
<img src="/images/sidebar/site_url.png" width="400px">
## Email Templates
### Template Variables
You can use template variables in `mail_subject` and `mail_subject_to_admin` as well as in the email template file:
```yaml
email:
# Other configurations omitted...
mail_subject: '[{{site_name}}] You have received a reply from @{{reply_nick}}'
mail_subject_to_admin: '[{{site_name}}] Your article "{{page_title}}" has a new reply'
mail_tpl: default # Email Template File
```
Variables follow the "Mustache" syntax, outputting a variable with `double braces` + `variable name`:
**Basic Content Variables**
```yaml
{{content}} # Comment content
{{link_to_reply}} # Reply link
{{nick}} # Commenter's nickname
{{page_title}} # Page title
{{page_url}} # Page PageKey (URL)
{{reply_content}} # Content of the reply
{{reply_nick}} # Nickname of the reply target
{{site_name}} # Site name
{{site_url}} # Site URL
```
::: details View Other Variables
```yaml
# Comment Creator
{{comment.badge_color}}
{{comment.badge_name}}
{{comment.content}}
{{comment.content_raw}}
{{comment.date}}
{{comment.datetime}}
{{comment.email}}
{{comment.email_encrypted}}
{{comment.id}}
{{comment.is_allow_reply}}
{{comment.is_collapsed}}
{{comment.is_pending}}
{{comment.link}}
{{comment.nick}}
{{comment.page.admin_only}}
{{comment.page.id}}
{{comment.page.key}}
{{comment.page.site_name}}
{{comment.page.title}}
{{comment.page.url}}
{{comment.page.vote_down}}
{{comment.page.vote_up}}
{{comment.page_key}}
{{comment.page_title}}
{{comment.rid}}
{{comment.site.first_url}}
{{comment.site.id}}
{{comment.site.name}}
{{comment.site.urls.0}}
{{comment.site.urls_raw}}
{{comment.site_name}}
{{comment.time}}
{{comment.ua}}
{{comment.visible}}
{{comment.vote_down}}
{{comment.vote_up}}
# Parent Comment (Comment that the creator is replying to)
{{parent_comment.badge_color}}
{{parent_comment.badge_name}}
{{parent_comment.content}}
{{parent_comment.content_raw}}
{{parent_comment.date}}
{{parent_comment.datetime}}
{{parent_comment.email}}
{{parent_comment.email_encrypted}}
{{parent_comment.id}}
{{parent_comment.is_allow_reply}}
{{parent_comment.is_collapsed}}
{{parent_comment.is_pending}}
{{parent_comment.link}}
{{parent_comment.nick}}
{{parent_comment.page.admin_only}}
{{parent_comment.page.id}}
{{parent_comment.page.key}}
{{parent_comment.page.site_name}}
{{parent_comment.page.title}}
{{parent_comment.page.url}}
{{parent_comment.page.vote_down}}
{{parent_comment.page.vote_up}}
{{parent_comment.page_key}}
{{parent_comment.page_title}}
{{parent_comment.rid}}
{{parent_comment.site.first_url}}
{{parent_comment.site.id}}
{{parent_comment.site.name}}
{{parent_comment.site.urls}}
{{parent_comment.site.urls_raw}}
{{parent_comment.site_name}}
{{parent_comment.time}}
{{parent_comment.ua}}
{{parent_comment.visible}}
{{parent_comment.vote_down}}
{{parent_comment.vote_up}}
```
:::
::: details View Data Sample
```json
{
"content": "<p>Test content</p>\n",
"link_to_reply": "https://artalk.js.org/?atk_comment=8100&atk_notify_key=44a9b2f08312565fba47c716df9d177f",
"nick": "Username",
"page_title": "Artalk",
"page_url": "https://artalk.js.org/",
"reply_content": "<p>Replier's content</p>\n",
"reply_nick": "Replier",
"site_name": "ArtalkDemo",
"site_url": "http://localhost:3000/",
"comment.badge_color": "",
"comment.badge_name": "",
"comment.content": "<p>Replier's content</p>\n",
"comment.content_raw": "Replier's content",
"comment.date": "2021-11-22",
"comment.datetime": "2021-11-22 22:22:42",
"comment.email": "replyer@example.com",
"comment.email_encrypted": "249898bd50e0febc5799485cf10b345a",
"comment.id": 8100,
"comment.is_allow_reply": true,
"comment.is_collapsed": false,
"comment.is_pending": false,
"comment.link": "",
"comment.nick": "Replier",
"comment.page.admin_only": false,
"comment.page.id": 75,
"comment.page.key": "https://artalk.js.org/",
"comment.page.site_name": "ArtalkDemo",
"comment.page.title": "Artalk",
"comment.page.url": "https://artalk.js.org/",
"comment.page.vote_down": 0,
"comment.page.vote_up": 0,
"comment.page_key": "https://artalk.js.org/",
"comment.page_title": "Artalk",
"comment.rid": 8099,
"comment.site.first_url": "http://localhost:3000/",
"comment.site.id": 2,
"comment.site.name": "ArtalkDemo",
"comment.site.urls.0": "http://localhost:3000/",
"comment.site.urls_raw": "http://localhost:3000/",
"comment.site_name": "ArtalkDemo",
"comment.time": "22:22:42",
"comment.ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 13_2_3 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Mobile/15E148 Safari/604.1",
"comment.visible": false,
"comment.vote_down": 0,
"comment.vote_up": 0,
"parent_comment.badge_color": "",
"parent_comment.badge_name": "",
"parent_comment.content": "<p>Test content</p>\n",
"parent_comment.content_raw": "Test content",
"parent_comment.date": "2021-11-22",
"parent_comment.datetime": "2021-11-22 22:21:17",
"parent_comment.email": "test@example.com",
"parent_comment.email_encrypted": "55502f40dc8b7c769880b10874abc9d0",
"parent_comment.id": 8099,
"parent_comment.is_allow_reply": true,
"parent_comment.is_collapsed": false,
"parent_comment.is_pending": false,
"parent_comment.link": "https://qwqaq.com",
"parent_comment.nick": "Username",
"parent_comment.page.admin_only": false,
"parent_comment.page.id": 75,
"parent_comment.page.key": "https://artalk.js.org/",
"parent_comment.page.site_name": "ArtalkDemo",
"parent_comment.page.title": "Artalk",
"parent_comment.page.url": "https://artalk.js.org/",
"parent_comment.page.vote_down": 0,
"parent_comment.page.vote_up": 0,
"parent_comment.page_key": "https://artalk.js.org/",
"parent_comment.page_title": "Artalk",
"parent_comment.rid": 0,
"parent_comment.site.first_url": "http://localhost:3000/",
"parent_comment.site.id": 2,
"parent_comment.site.name": "ArtalkDemo",
"parent_comment.site.urls.0": "http://localhost:3000/",
"parent_comment.site.urls_raw": "http://localhost:3000/",
"parent_comment.site_name": "ArtalkDemo",
"parent_comment.time": "22:21:17",
"parent_comment.ua": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/93.0.4577.82 Safari/537.36",
"parent_comment.visible": false,
"parent_comment.vote_down": 0,
"parent_comment.vote_up": 0
}
```
:::
### Custom Templates
You can set `mail_tpl` to a "specific file path" to use an external custom email template.
For example, set `mail_tpl` to `"/root/Artalk/data/mail_tpl/your_email_template.html"`
```yaml
email:
mail_tpl: /root/Artalk/data/mail_tpl/your_email_template.html
# Other configurations omitted...
```
Then, there should be a file at this path:
```html
<div>
<p>Hi, {{nick}}:</p>
<p>You have received a reply in “{{page_title}}”:</p>
<div>
<div>@{{reply_nick}}:</div>
<div>{{reply_content}}</div>
</div>
<p><a href="{{link_to_reply}}" target="_blank">Reply to the message »</a></p>
</div>
```
Artalk includes many preset email templates, such as `mail_tpl: "default"`, which uses: [@ArtalkJS/Artalk:/internal/template/email_tpl/default.html](https://github.com/ArtalkJS/Artalk/blob/master/internal/template/email_tpl/default.html)
## Emails to Administrators
Email notifications target both administrators and regular users. You can set different subjects for emails sent to administrators via the following configuration:
```yaml
admin_notify:
enabled: true
mail_subject: '[{{site_name}}] Your article "{{page_title}}" has a new reply'
```
Note: The old `email.mail_subject_to_admin` configuration item has been deprecated. Please use the above instead.
Artalk supports various methods to send notifications to administrators, not limited to emails. Refer to: [Diverse Push Notifications](./admin_notify.md#email-notifications).
+114
View File
@@ -0,0 +1,114 @@
# Image Upload
Artalk provides an image upload feature with options to limit image size, upload frequency, and more. You can also integrate with UpGit to upload images to image hosting services.
You can modify this configuration in the settings interface of the [Dashboard](../frontend/sidebar.md#settings), or configure it through [configuration files](./config.md#image-upload-img_upload) or [environment variables](../env.md#image-upload).
## Configuration File
The complete `img_upload` configuration is as follows:
```yaml
# Image Upload
img_upload:
enabled: true # Master Switch
path: ./data/artalk-img/ # Image storage path
max_size: 5 # Image size limit (Unit: MB)
public_path: null # Specify the base URL for image links (default is "/static/images/")
# Use UpGit to upload images to GitHub or image hosting services
upgit:
enabled: false # Enable UpGit
exec: upgit -c <upgit configuration file path> -t /artalk-img
del_local: true # Delete local images after uploading
```
## Using UpGit to Upload to Image Hosting Services
[UpGit](https://github.com/pluveto/upgit) supports uploading images to various image hosting services or code repositories such as GitHub, Gitee, Tencent Cloud COS, Qiniu Cloud, UpYun, SM.MS, and more.
First, download UpGit and complete the configuration for your target image hosting service according to the [README.md](https://github.com/pluveto/upgit).
Then, add UpGit to the system's environment variables by adding the following to `~/.bashrc`:
```bash
export PATH=$PATH:/path/to/upgit
```
(Or move it directly to `/usr/bin`)
Finally, fill in the UpGit startup parameters in Artalk's `img_upload.upgit` field:
```yaml
upgit:
enabled: true # Enable UpGit
exec: upgit -c <upgit configuration file path> -t /artalk-img
del_local: true # Delete local images after uploading
```
::: warning Update Notice
Starting from version `v2.8.4`, to enhance security, Artalk no longer allows specifying the UpGit executable file path. Please add it to the system's environment variables. :)
:::
### Mounting UpGit with Docker
If you are deploying Artalk with Docker, you can mount the UpGit executable to the container:
```bash
docker run -d --name artalk -v /path/to/upgit:/usr/bin/upgit -v /path/to/artalk:/app/data -p 8080:23366 artalk
```
## Upload Frequency Limit
The frequency limit follows the `captcha` configuration. When the limit is exceeded, a captcha will be prompted.
Refer to: [Backend · Captcha](./captcha.md)
## Path
`img_upload.path` is the "local storage directory" path for uploaded image files. This directory will be mapped by Artalk to be accessible at:
```
http://<backend address>/static/images/
```
## Public Path
The default value for `img.public_path` is: `/static/images/`
When this item is a "relative path", for example: `/static/images/`, the HTML tag for the uploaded image on the frontend will be:
```html
<img src="http://<backend address>/static/images/1.png" />
```
Note: The `<backend address>` is configured in the frontend `conf.server`.
When this item is a "complete URL path", for example: `https://cdn.github.com/img/`, the image tag will be:
```html
<img src="https://cdn.github.com/img/1.png" />
```
Tip: This configuration can be used in scenarios such as load balancing.
## Custom Upload API on the Frontend
The frontend provides the `imgUploader` configuration option, allowing you to customize the API for image upload requests, for example:
```js
Artalk.init({
imgUploader: async (file) => {
const form = new FormData()
form.set('file', file)
const imgUrl = await fetch('https://api.example.org/upload', {
method: 'POST',
body: form,
})
return imgUrl
},
})
```
Refer to: [Frontend Configuration Documentation](../frontend/config.md#imguploader)
+118
View File
@@ -0,0 +1,118 @@
# Comment Moderation
Artalk supports multiple comment filtering methods to intercept spam comments. It offers integration with online APIs like Akismet, Tencent Cloud Content Safety, Alibaba Cloud Content Safety, and local offline keyword libraries. You can further enhance comment moderation by combining it with the [captcha](./captcha.md) feature, making it hard for spam comments to get through.
You can modify this configuration in the settings interface of the [Dashboard](../frontend/sidebar.md#settings), or configure it through [configuration files](./config.md#comment-moderation-moderator) or [environment variables](../env.md#comment-moderation).
## Configuration File
The complete `moderator` configuration is as follows:
```yaml
# Comment Moderation
moderator:
pending_default: false # New comments default to "pending review" status
api_fail_block: false # Intercept comments even if the spam detection API request fails
# akismet.com anti-spam
akismet_key: ''
# Tencent Cloud Text Content Safety (tms)
tencent: # https://cloud.tencent.com/document/product/1124/64508
enabled: false
secret_id: ''
secret_key: ''
region: ap-guangzhou
# Alibaba Cloud Content Safety
aliyun: # https://help.aliyun.com/document_detail/28417.html
enabled: false
access_key_id: ''
access_key_secret: ''
region: cn-shanghai
# Keyword library filtering
keywords:
enabled: false
pending: false # Set to pending review if matched
files: # Support multiple keyword files
- './data/keyword_1.txt'
file_sep: "\n" # Keyword file content separator
replace_to: 'x' # Replacement character
```
## Default Pending Mode
Enable new comments to default to "pending review" status:
```yaml
moderator:
pending_default: true
```
## Akismet
[Akismet](https://akismet.com/) is a globally recognized anti-spam API provided by WordPress, particularly effective against English spam comments. Akismet offers a free Personal version suitable for personal blog sites.
![](/images/akismet/1.png)
You can easily apply for an `akismet_key` on the [Akismet official website](https://akismet.com/) and fill it in the configuration file to enable Akismet spam filtering.
![](/images/akismet/2.png)
```yaml
moderator:
akismet_key: your_key
```
## Tencent Cloud Text Content Safety
Refer to: [Tencent Cloud Documentation](https://cloud.tencent.com/document/product/1124/64508)
After enabling "Text Content Safety", add a Secret with permissions in "Access Management" - "API Key Management", and fill in the configuration:
```yaml
moderator:
tencent:
enabled: true
secret_id: ''
secret_key: ''
region: ap-guangzhou
```
## Alibaba Cloud Content Safety
Refer to: [Alibaba Cloud Documentation](https://help.aliyun.com/document_detail/28417.html)
After enabling "Alibaba Cloud Content Safety", create an Access Key in the Alibaba Cloud backend and fill in the configuration:
```yaml
moderator:
aliyun:
enabled: true
access_key_id: ''
access_key_secret: ''
region: cn-shanghai
```
## Keyword Library Filtering
If you prefer not to rely on remote APIs, you can configure and import keyword files locally to let Artalk detect spam comments based on keywords:
```yaml
moderator:
keywords:
enabled: true
pending: false # Set to pending review if matched
files: # Support multiple keyword files
- ./data/keyword_1.txt
file_sep: "\n" # Keyword file content separator
replace_to: 'x' # Replacement character
```
- **pending**: Whether to set the comment to pending review status upon successful match.
- **files**: Keyword files. Multiple files are allowed, and Artalk will merge the keyword libraries upon startup.
- **file_sep**: Keyword file content separator. For example, if each line in the file contains a keyword, set this item to `\n`.
- **replace_to**: Replacement character. For example, if this item is set to `x`, you can set `pending` to `false`, allowing the comment to pass review automatically, but the matched keywords will be replaced with `x`, resulting in `fxxk` or `xxxx`.
Note: It is recommended not to use `*` asterisk as `replace_to` because it conflicts with the Markdown bold syntax.
## Using Captcha
You can enable Artalk's captcha feature, supporting image and slider captchas, [refer here](./captcha.md).
+86
View File
@@ -0,0 +1,86 @@
# Admins and Multi-Site Support
Artalk supports multi-site management, allowing administrators to create and manage multiple sites and their respective comments and pages from a centralized interface.
## Creating an Administrator
Run the following command and follow the prompts to quickly create an administrator:
```sh
./artalk admin
```
If you are using Docker, you can run the following command:
```sh
docker exec -it artalk artalk admin
```
After creating the administrator account, you can log into the control panel to create additional accounts through the graphical user interface on the user management page, eliminating the need to manually edit configuration files.
## Creating and Managing Sites
You can create and manage multiple sites and switch between them quickly in the "Dashboard" accessible from the sidebar.
## Admin Configuration
You can set up multiple administrator accounts. When the input field matches an administrator's username and email, a password verification prompt will appear. Only administrators can access the "Dashboard" and manage comments from the frontend.
(Optional) Add administrators via the configuration file:
```yaml
admin_users:
- name: admin
email: admin@example.com
password: (bcrypt)$2y$10$ti4vZYIrxVN8rLcYXVgXCO.GJND0dyI49r7IoF3xqIx8bBRmIBZRm
badge_name: Administrator
badge_color: '#0083FF'
- name: admin2
email: admin2@example.com
password: (bcrypt)$2y$10$ti4vZYIrxVN8rLcYXVgXCO.GJND0dyI49r7IoF3xqIx8bBRmIBZRm
badge_name: Junior Admin
badge_color: '#0083FF'
```
Explanation of each configuration item:
- **name** & **email**: Username and email, **case-insensitive**.
- **password**: User password.
Supports bcrypt and md5 encryption. For example, you can specify: `"(md5)50c21190c6e4e5418c6a90d2b5031119"`.
**Using the more secure bcrypt encryption algorithm is recommended**. In a Linux environment, you can use the [htpasswd command](https://httpd.apache.org/docs/2.4/programs/htpasswd.html) to generate the encrypted password:
```bash
unset HISTFILE # Temporarily disable history to prevent the password from appearing in the history
htpasswd -bnBC 10 "" "your_password" | tr -d ':'
```
Then configure it as: `"(bcrypt)$2y$10$ti4vZYIrxVN8rLcY..."`, starting with `(bcrypt)`.
Command explanation reference: [Compute bcrypt hash from command line](https://unix.stackexchange.com/questions/307994/compute-bcrypt-hash-from-command-line#answer-419855)
- **badge_name**: The title badge text displayed for the user.
- **badge_color**: The background color of the title badge displayed for the user.
::: tip
You can also configure administrator accounts through environment variables. Refer to: [Environment Variable Configuration](../env.md)
:::
### Controlling Admin Email Notifications
By default, when there are new comments on a page, emails are sent to all administrators. However, you can configure `receive_email` to forcefully disable email notifications for specific administrators.
This is useful if you have multiple email addresses configured but do not want certain addresses to receive comment notifications.
- **receive_email**: When set to `false`, the system will not send email notifications to that user.
Note: Even if email notifications are disabled, the administrator will still receive @AT replies from others. The system will not send email notifications when the user comments on a page (creates a root comment).
```yaml
admin_users:
- name: admin
receive_email: false # ← Forcefully disable email notifications
```
@@ -0,0 +1,53 @@
# Resolve Relative Path
Artalk supports parsing relative paths, allowing you to configure it on the frontend as follows:
```js
Artalk.init({
site: 'Example Site', // Your site name
pageKey: '/relative-path/xx.html', // Using relative path
})
```
Using relative paths is recommended because it facilitates future "site migration" needs.
Next, in the sidebar, navigate to "Dashboard" - "Site", find "Example Site", and modify the site URL.
![](/images/relative-path/1.png)
Afterward, all relative paths will be "based on this site URL". For example:
```bash
"/relative-path/xx.html"
↓ resolves to
"https://set-example-site-url.xxx/relative-path/xx.html"
```
## Uses of Resolved URLs
The site URL + page relative path will be used for:
- **Email notifications** containing links to reply to comments
- **Sidebar** quick jumps to specific comments
- **Dashboard** page management to open pages
- **Fetching page titles** and other information
## Configuring Multiple Site URLs
You might need to configure multiple URLs for a site to allow referer and cross-origin requests.
In "Dashboard" - "Site", you can modify the site URL to support adding multiple URLs by separating each URL with a comma `,`.
**When a site has multiple URLs**, the "relative path" will be based on the "first" URL in the list.
## Using Absolute Paths
As opposed to using relative paths, you can use absolute paths. For example, configure the frontend like this:
```js
Artalk.init({
pageKey: 'https://your_domain.com/relative-path/xx.html', // Using absolute path
})
```
In this case, the backend will not resolve this address. The absolute path specified in `pageKey` will be directly used for locating the page in emails, sidebar, etc.
+123
View File
@@ -0,0 +1,123 @@
# Reverse Proxy
## Caddy
**/etc/caddy/Caddyfile**
```nginx
artalk.your_domain.com {
tls /etc/caddy/ssl/cert.pem /etc/caddy/ssl/cert.key
reverse_proxy http://localhost:23366 {
header_up X-Forwarded-For {header.X-Forwarded-For}
}
}
```
Reload the Caddy configuration:
```sh
sudo systemctl reload caddy
```
## Nginx
Assumptions:
- The domain you want to bind is: `artalk.your_domain.com`
- Artalk local address: `http://localhost:23366`
For Ubuntu 20.04:
Create the site configuration file:
```bash
sudo vim /etc/nginx/sites-available/artalk.your_domain.com
```
Edit the reverse proxy configuration file:
```nginx
server {
listen 80;
listen [::]:80;
server_name artalk.your_domain.com;
location / {
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://localhost:23366/;
}
}
```
Create a symbolic link to enable the site:
```bash
sudo ln -s /etc/nginx/sites-available/artalk.your_domain.com /etc/nginx/sites-enabled/
```
Check if the configuration file is valid:
```bash
sudo nginx -t
```
If the configuration is correct, restart Nginx:
```bash
sudo systemctl restart nginx
```
Configure the frontend:
```js
Artalk.init({ server: 'http://artalk.your_domain.com' })
```
::: tip
You can also add a layer of CDN and SSL.
Pay attention to the configuration file permissions and the accessibility of the reverse proxy target URL.
Especially if Artalk is running inside a Docker container, make sure the IP and port can be accessed by Nginx.
:::
## Apache
You need to enable the reverse proxy module `mod_proxy.c`
```apache
<VirtualHost *:80>
ServerName your_domain.xxx
ServerAlias
RewriteEngine On
RewriteCond %{QUERY_STRING} transport=polling [NC]
RewriteRule /(.*) http://localhost:23366/$1 [P]
<IfModule mod_proxy.c>
ProxyRequests Off
SSLProxyEngine on
ProxyPass / http://localhost:23366/
ProxyPassReverse / http://localhost:23366/
</IfModule>
</VirtualHost>
```
## BaoTa Panel (宝塔面板)
First, create a site (e.g., `artalk.your_domain.com`), then click the site "Settings":
![](/images/baota-proxy/1.png)
Open the "Reverse Proxy" tab, click "Add Reverse Proxy", fill in the "Target URL" with `http://localhost:port` (where the port corresponds to the Artalk port), and fill in the "Send Domain" with `$host`, as shown in the figure:
![](/images/baota-proxy/2.png)
## Getting the Accurate IP Address
When using a reverse proxy server, you need to configure the proxy headers to get the user's accurate IP address. Refer to the [IP Region](../frontend/ip-region.md#获取准确的-ip-地址) documentation for more details.
+25
View File
@@ -0,0 +1,25 @@
# Program Upgrade
## Update Changes
For significant changes, such as updates that require modifications to existing configurations, please refer to the version update log for relevant prompts: [CHANGELOG.md](https://github.com/ArtalkJS/Artalk/blob/master/CHANGELOG.md).
## One-Click Upgrade via Command Line
Execute `./artalk upgrade`
This operation will automatically download and upgrade the program from GitHub Release. Ensure to stop Artalk before executing this command.
::: tip
Execute `./artalk upgrade -f` with the `-f` parameter to force an update.
:::
## Docker Upgrade
Refer to: [Docker · Upgrade](./docker.md#升级)
## Manual Method
Go to [GitHub Release](https://github.com/ArtalkJS/Artalk/releases) to manually download the latest build.
Replace the old version files with the new ones.
+12
View File
@@ -0,0 +1,12 @@
# 🚀 Case Showcase
### Open Source Projects
- [Wiki.js](https://github.com/requarks/wiki/): A modern and powerful wiki app built on Node.js
- [vuepress-theme-hope](https://github.com/vuepress-theme-hope/vuepress-theme-hope): A vuepress theme with tons of features
- [hexo-theme-stellar](https://github.com/xaoxuu/hexo-theme-stellar): Elegant and powerful theme for Hexo
- [FixIt Theme | Hugo](https://github.com/Lruihao/FixIt): A clean, elegant but advanced blog theme for Hugo
- [hexo-theme-volantis](https://github.com/volantis-x/hexo-theme-volantis): A Wonderful Theme for Hexo
- [hexo-theme-cards](https://github.com/ChrAlpha/hexo-theme-cards): Another Simple & Swift theme for Hexo
- [hexo-theme-butterfly](https://github.com/jerryc127/hexo-theme-butterfly): A Hexo Theme: Butterfly
- [hexo-theme-solitude](https://github.com/valor-x/hexo-theme-solitude): A Hexo Theme: Solitude
+322
View File
@@ -0,0 +1,322 @@
# 📦 Getting Started
This guide will help you deploy Artalk on your server. Once deployed, you can integrate the Artalk client into your website or blog to enable comment functionality.
## Docker
Here is a simple guide for deploying the Artalk **Server** and **Client**.
### Launch Server
It is recommended to use Docker for deployment. Pre-install the [Docker Engine](https://docs.docker.com/engine/install/) and create a working directory, then run the command to launch a container in the background:
```bash
docker run -d \
--name artalk \
-p 8080:23366 \
-v $(pwd)/data:/data \
-e "TZ=America/New_York" \
-e "ATK_LOCALE=en" \
-e "ATK_SITE_DEFAULT=Artalk Blog" \
-e "ATK_SITE_URL=https://example.com" \
artalk/artalk-go
```
(Tip: We also provide a [Docker Compose](#docker-compose) configuration file).
Run the command to create an admin account:
```bash
docker exec -it artalk artalk admin
```
Enter `http://artalk.example.com:8080` in your browser to access the Artalk Dashboard.
### Integrate Client
Import the embedded client JS and CSS resources from the Artalk server to your webpage and initialize the Artalk client:
```html
<!-- CSS -->
<link href="http://artalk.example.com:8080/dist/Artalk.css" rel="stylesheet" />
<!-- JS -->
<script src="http://artalk.example.com:8080/dist/Artalk.js"></script>
<!-- Artalk -->
<div id="Comments"></div>
<script>
Artalk.init({
el: '#Comments', // Selector of the bound element
pageKey: '/post/1', // Permalink
pageTitle: 'About Introducing Artalk', // Page title (leave blank to auto-fetch)
server: 'http://artalk.example.com:8080', // Artalk server address
site: 'Artalk Blog', // Your site name
})
</script>
```
Enter the admin username and email in the comment box, and the "Dashboard" button will appear at the bottom right of the comment box.
In the Dashboard, you can [configure the comment system](./backend/config.md) to your liking or [migrate comments to Artalk](./transfer.md).
🥳 You have successfully deployed Artalk!
## Binary
1. Download the program package from [GitHub Release](https://github.com/ArtalkJS/Artalk/releases)
2. Extract it with `tar -zxvf artalk_version_system_architecture.tar.gz`
3. Run `./artalk server`
4. Configure and initialize the client on your webpage:
```js
Artalk.init({ server: 'http://artalk.example.com:23366' })
```
Advanced operations:
- [Daemon Process (Systemd, Supervisor)](./backend/daemon.md)
- [Reverse Proxy (Caddy, Nginx, Apache)](./backend/reverse-proxy.md)
- [Self-compile (Build from the latest code)](https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md)
## Go Install
If you have the Golang toolchain installed, you can run the following commands to compile and install the latest version of Artalk:
```bash
go install github.com/artalkjs/artalk/v2@latest
```
Then run the server:
```bash
artalk server
```
The client integration steps are [here](#integrate-client).
## Linux Distributions
**Fedora (Copr)**:
```bash
dnf install 'dnf-command(copr)'
dnf copr enable @artalk/artalk
dnf install artalk
```
**Arch Linux (AUR)**:
```bash
paru -S artalk
```
**NixOS**:
```bash
nix-env -iA nixpkgs.artalk
```
**Termux**:
```bash
pkg install artalk
```
[![Packaging status](https://repology.org/badge/vertical-allrepos/artalk.svg)](https://repology.org/project/artalk/versions)
[![Copr status](https://img.shields.io/badge/dynamic/json?color=blue&label=Fedora%20Copr&query=builds.latest.source_package.version&url=https%3A%2F%2Fcopr.fedorainfracloud.org%2Fapi_3%2Fpackage%3Fownername%3D%40artalk%26projectname%3Dartalk%26packagename%3Dartalk%26with_latest_build%3DTrue)](https://copr.fedorainfracloud.org/coprs/g/artalk/artalk/)
## Docker Compose
Create a working directory and edit the `docker-compose.yml` file:
```yaml
version: '3.8'
services:
artalk:
container_name: artalk
image: artalk/artalk-go
restart: unless-stopped
ports:
- 8080:23366
volumes:
- ./data:/data
environment:
- TZ=America/New_York
- ATK_LOCALE=en
- ATK_SITE_DEFAULT=Artalk Blog
- ATK_SITE_URL=https://your_domain
```
Start the container to launch Artalk server:
```bash
docker-compose up -d
```
The client integration steps are [here](#integrate-client).
::: details Common Compose Commands
```bash
docker-compose restart # Restart the container
docker-compose stop # Stop the container
docker-compose down # Remove the container
docker-compose pull # Update the image
docker-compose exec artalk bash # Enter the container
```
:::
More information: [Docker](./backend/docker.md) / [Environment Variables](./env.md)
## Client
If you have a frontend or Node.js web project, this following guide will help you integrate the Artalk **Client** into your web project.
### Client Installation
Install via npm:
::: code-group
```sh [npm]
npm install artalk
```
```sh [yarn]
yarn add artalk
```
```sh [pnpm]
pnpm add artalk
```
```sh [bun]
bun add artalk
```
:::
(or see [CDN Resources](#client-cdn-resources)).
### Client Usage
Import Artalk in your web project:
```js
import 'artalk/Artalk.css'
import Artalk from 'artalk'
const artalk = Artalk.init({
el: document.querySelector('#Comments'), // DOM element where you want to mount
pageKey: '/post/1', // Permalink
pageTitle: 'About Introducing Artalk', // Page title
server: 'http://artalk.example.com:8080', // Artalk server address
site: 'Artalk Blog', // Site name
})
```
For more references:
- [Import to Blog Documentation](../develop/import-blog.md)
- [Import to Frameworks Documentation](../develop/import-framework.md)
- [Client API Reference](../develop/fe-api.md)
- [UI (Client) Configuration](./frontend/config.md)
### Client CDN Resources
To use Artalk in the browser via CDN, for modern browsers (which support [ES modules](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules)), you can use [esm.sh](https://esm.sh) or [esm.run](https://esm.run):
::: code-group
```html [ES Module]
<body>
<div id="Comments"></div>
<script type="module">
import Artalk from 'https://esm.sh/artalk@:ArtalkVersion:'
Artalk.init({
el: '#Comments',
})
</script>
</body>
```
```html [Legacy]
<body>
<div id="Comments"></div>
<script src="https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.js"></script>
<script>
Artalk.init({
el: '#Comments',
})
</script>
</body>
```
:::
Don't forget to include the CSS file:
```html
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.css">
```
::: tip Latest Version of Artalk
The latest Artalk client version is: `:ArtalkVersion:`
To upgrade the client, replace the numeric part of the version number in the URL.
:::
Note: The Artalk server had embedded the client resources. Ensure version compatibility when using public CDN resources.
::: details Alternative CDNs
**CDNJS**
```
https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.js
```
```
https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.css
```
**JSDELIVR**
```
https://cdn.jsdelivr.net/npm/artalk@:ArtalkVersion:/dist/Artalk.js
```
```
https://cdn.jsdelivr.net/npm/artalk@:ArtalkVersion:/dist/Artalk.css
```
**UNPKG**
```
https://unpkg.com/artalk@:ArtalkVersion:/dist/Artalk.js
```
```
https://unpkg.com/artalk@:ArtalkVersion:/dist/Artalk.css
```
:::
## Data Migration
Import data from other comment systems: [Data Migration](./transfer.md).
## ArtalkLite
ArtalkLite is a lightweight version of the Artalk client. See: [ArtalkLite](./frontend/artalk-lite.md).
## Development Environment
Please refer to: [Developer Guide](https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md).
+350
View File
@@ -0,0 +1,350 @@
# Environment Variables
Artalk supports configuration changes via environment variables, simplifying containerized cloud deployments such as Docker.
Environment variable names start with `ATK_`, in all uppercase, corresponding to each node in the [configuration file](./backend/config.md).
Environment variables take precedence over configuration files. Verify if the configuration has taken effect using the following command:
```bash
artalk config
```
To deploy Artalk using Docker Compose, add environment variables in the `compose.yml` file, for instance:
```yaml
version: '3.8'
services:
artalk:
container_name: artalk
image: artalk/artalk-go
restart: unless-stopped
ports:
- 8080:23366
volumes:
- ./data:/data
environment:
- TZ=America/New_York
- ATK_LOCALE=en
- ATK_SITE_DEFAULT=Artalk's Blog
- ATK_SITE_URL=https://example.com
- ATK_TRUSTED_DOMAINS=https://dev.example.com https://localhost:8080
- ATK_ADMIN_USERS_0_NAME=admin
- ATK_ADMIN_USERS_0_EMAIL=admin@example.org
- ATK_ADMIN_USERS_0_PASSWORD=(bcrypt)$2y$10$ti4vZYIrxVN8rLcYXVgXCO.GJND0dyI49r7IoF3xqIx8bBRmIBZRm
- ATK_ADMIN_USERS_0_BADGE_NAME=Administrator
- ATK_ADMIN_USERS_0_BADGE_COLOR=#0083FF
```
When the variable is an array, set array values using space-separated strings or numerical indices, for example:
```
ATK_TRUSTED_DOMAINS="https://a.com https://b.com"
ATK_TRUSTED_DOMAINS_0="https://a.com"
```
<style>
.env-table table {
table-layout: fixed;
word-break: break-word;
th:first-of-type, td:first-of-type {
width: 30%;
}
th:nth-of-type(2), td:nth-of-type(2) {
width: 20%;
}
th:nth-of-type(3), td:nth-of-type(3) {
width: 20%;
}
th:nth-of-type(4), td:nth-of-type(4) {
width: 30%;
}
}
</style>
<div class="env-table">
<!-- env-variables -->
## 通用配置
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_APP_KEY** | `""` | App Key (for generation of JWT) | app_key (App Key) |
| **ATK_DEBUG** | `false` | Debug mode | debug (Debug mode) |
| **ATK_HOST** | `"0.0.0.0"` | Listen host | host (Listen host) |
| **ATK_LOCALE** | `"en"` | Language (follow Unicode BCP 47) (可选:`["en", "zh-CN", "zh-TW", "ja", "fr", "ko", "ru"]`) | locale (Language) |
| **ATK_LOGIN_TIMEOUT** | `259200` | Login timeout (in seconds) | login_timeout (Login timeout) |
| **ATK_PORT** | `23366` | Listen port | port (Listen port) |
| **ATK_SITE_DEFAULT** | `"Default Site"` | Default site name (create when app is first launched) | site_default (Default site name) |
| **ATK_SITE_URL** | `""` | Default site url | site_url (Default site url) |
| **ATK_TIMEZONE** | `"Asia/Shanghai"` | Timezone (follow IANA Time Zone Database) | timezone (Timezone) |
| **ATK_TRUSTED_DOMAINS** | `[]` | Trusted domains | trusted_domains (Trusted domains) |
## Multi-Push
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_ADMIN_NOTIFY_BARK_ENABLED** | `false` | 启用 | admin_notify.bark.enabled (Multi-Push > Bark > Enabled) |
| **ATK_ADMIN_NOTIFY_BARK_SERVER** | `"http://day.app/xxxxxxx/"` | Server | admin_notify.bark.server (Multi-Push > Bark > Server) |
| **ATK_ADMIN_NOTIFY_DING_TALK_ENABLED** | `false` | 启用 | admin_notify.ding_talk.enabled (Multi-Push > DingTalk > Enabled) |
| **ATK_ADMIN_NOTIFY_DING_TALK_SECRET** | `""` | Secret | admin_notify.ding_talk.secret (Multi-Push > DingTalk > Secret) |
| **ATK_ADMIN_NOTIFY_DING_TALK_TOKEN** | `""` | Token | admin_notify.ding_talk.token (Multi-Push > DingTalk > Token) |
| **ATK_ADMIN_NOTIFY_EMAIL_ENABLED** | `true` | Enable (can be disabled when using other push methods) | admin_notify.email.enabled (Multi-Push > Notify admin > Enable) |
| **ATK_ADMIN_NOTIFY_EMAIL_MAIL_SUBJECT** | `"[{{site_name}}] Post \"{{page_title}}\" has new a comment"` | Email subject (email subject sent to admin) | admin_notify.email.mail_subject (Multi-Push > Notify admin > Email subject) |
| **ATK_ADMIN_NOTIFY_EMAIL_MAIL_TPL** | `""` | Admin email template file (set to file path to use custom template) | admin_notify.email.mail_tpl (Multi-Push > Notify admin > Admin email template file) |
| **ATK_ADMIN_NOTIFY_LARK_ENABLED** | `false` | 启用 | admin_notify.lark.enabled (Multi-Push > Lark > Enabled) |
| **ATK_ADMIN_NOTIFY_LARK_MSG_TYPE** | `"text"` | Message type (可选:`["text", "card"]`) | admin_notify.lark.msg_type (Multi-Push > Lark > Message type) |
| **ATK_ADMIN_NOTIFY_LARK_WEBHOOK_URL** | `""` | WebhookUrl | admin_notify.lark.webhook_url (Multi-Push > Lark > WebhookUrl) |
| **ATK_ADMIN_NOTIFY_LINE_CHANNEL_ACCESS_TOKEN** | `""` | ChannelAccessToken | admin_notify.line.channel_access_token (Multi-Push > LINE > ChannelAccessToken) |
| **ATK_ADMIN_NOTIFY_LINE_CHANNEL_SECRET** | `""` | ChannelSecret | admin_notify.line.channel_secret (Multi-Push > LINE > ChannelSecret) |
| **ATK_ADMIN_NOTIFY_LINE_ENABLED** | `false` | 启用 | admin_notify.line.enabled (Multi-Push > LINE > Enabled) |
| **ATK_ADMIN_NOTIFY_LINE_RECEIVERS** | `[USER_ID_1 GROUP_ID_1]` | Receivers | admin_notify.line.receivers (Multi-Push > LINE > Receivers) |
| **ATK_ADMIN_NOTIFY_NOISE_MODE** | `false` | Noise mode | admin_notify.noise_mode (Multi-Push > Noise mode) |
| **ATK_ADMIN_NOTIFY_NOTIFY_PENDING** | `false` | Pending comment still send notification (notifications are still sent when comments are intercepted) | admin_notify.notify_pending (Multi-Push > Pending comment still send notification) |
| **ATK_ADMIN_NOTIFY_NOTIFY_TPL** | `"default"` | Notification template (set to file path to use custom template) | admin_notify.notify_tpl (Multi-Push > Notification template) |
| **ATK_ADMIN_NOTIFY_SLACK_ENABLED** | `false` | 启用 | admin_notify.slack.enabled (Multi-Push > Slack > Enabled) |
| **ATK_ADMIN_NOTIFY_SLACK_OAUTH_TOKEN** | `""` | OauthToken | admin_notify.slack.oauth_token (Multi-Push > Slack > OauthToken) |
| **ATK_ADMIN_NOTIFY_SLACK_RECEIVERS** | `[CHANNEL_ID]` | Receivers | admin_notify.slack.receivers (Multi-Push > Slack > Receivers) |
| **ATK_ADMIN_NOTIFY_TELEGRAM_API_TOKEN** | `""` | ApiToken | admin_notify.telegram.api_token (Multi-Push > Telegram > ApiToken) |
| **ATK_ADMIN_NOTIFY_TELEGRAM_ENABLED** | `false` | 启用 | admin_notify.telegram.enabled (Multi-Push > Telegram > Enabled) |
| **ATK_ADMIN_NOTIFY_TELEGRAM_RECEIVERS** | `[7777777]` | Receivers | admin_notify.telegram.receivers (Multi-Push > Telegram > Receivers) |
| **ATK_ADMIN_NOTIFY_WEBHOOK_ENABLED** | `false` | 启用 | admin_notify.webhook.enabled (Multi-Push > WebHook > Enabled) |
| **ATK_ADMIN_NOTIFY_WEBHOOK_URL** | `""` | Url | admin_notify.webhook.url (Multi-Push > WebHook > Url) |
## Social Login
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_AUTH_ANONYMOUS** | `false` | Allow anonymous commenting (Allow skipping verification, only fill in an anonymous nickname and email) | auth.anonymous (Social Login > Allow anonymous commenting) |
| **ATK_AUTH_APPLE_CLIENT_ID** | `""` | ClientId | auth.apple.client_id (Social Login > Apple > ClientId) |
| **ATK_AUTH_APPLE_CLIENT_SECRET** | `""` | ClientSecret | auth.apple.client_secret (Social Login > Apple > ClientSecret) |
| **ATK_AUTH_APPLE_ENABLED** | `false` | 启用 | auth.apple.enabled (Social Login > Apple > Enabled) |
| **ATK_AUTH_AUTH0_CLIENT_ID** | `""` | ClientId | auth.auth0.client_id (Social Login > Auth0 > ClientId) |
| **ATK_AUTH_AUTH0_CLIENT_SECRET** | `""` | ClientSecret | auth.auth0.client_secret (Social Login > Auth0 > ClientSecret) |
| **ATK_AUTH_AUTH0_DOMAIN** | `""` | Domain | auth.auth0.domain (Social Login > Auth0 > Domain) |
| **ATK_AUTH_AUTH0_ENABLED** | `false` | 启用 | auth.auth0.enabled (Social Login > Auth0 > Enabled) |
| **ATK_AUTH_CALLBACK** | `"http://localhost:23366/api/v2/auth/{provider}/callback"` | Callback URL (https://example.com/api/v2/auth/{provider}/callback) | auth.callback (Social Login > Callback URL) |
| **ATK_AUTH_DISCORD_CLIENT_ID** | `""` | ClientId | auth.discord.client_id (Social Login > Discord > ClientId) |
| **ATK_AUTH_DISCORD_CLIENT_SECRET** | `""` | ClientSecret | auth.discord.client_secret (Social Login > Discord > ClientSecret) |
| **ATK_AUTH_DISCORD_ENABLED** | `false` | 启用 | auth.discord.enabled (Social Login > Discord > Enabled) |
| **ATK_AUTH_EMAIL_ENABLED** | `true` | Enable email password login | auth.email.enabled (Social Login > Email > Enable email password login) |
| **ATK_AUTH_EMAIL_VERIFY_SUBJECT** | `"Your Code - {{code}}"` | Verification email subject | auth.email.verify_subject (Social Login > Email > Verification email subject) |
| **ATK_AUTH_EMAIL_VERIFY_TPL** | `"default"` | Verification email template (set to file path to use custom template) | auth.email.verify_tpl (Social Login > Email > Verification email template) |
| **ATK_AUTH_ENABLED** | `false` | Enable Social Login | auth.enabled (Social Login > Enable Social Login) |
| **ATK_AUTH_FACEBOOK_CLIENT_ID** | `""` | ClientId | auth.facebook.client_id (Social Login > Facebook > ClientId) |
| **ATK_AUTH_FACEBOOK_CLIENT_SECRET** | `""` | ClientSecret | auth.facebook.client_secret (Social Login > Facebook > ClientSecret) |
| **ATK_AUTH_FACEBOOK_ENABLED** | `false` | 启用 | auth.facebook.enabled (Social Login > Facebook > Enabled) |
| **ATK_AUTH_GITEA_CLIENT_ID** | `""` | ClientId | auth.gitea.client_id (Social Login > Gitea > ClientId) |
| **ATK_AUTH_GITEA_CLIENT_SECRET** | `""` | ClientSecret | auth.gitea.client_secret (Social Login > Gitea > ClientSecret) |
| **ATK_AUTH_GITEA_ENABLED** | `false` | 启用 | auth.gitea.enabled (Social Login > Gitea > Enabled) |
| **ATK_AUTH_GITHUB_CLIENT_ID** | `""` | ClientId | auth.github.client_id (Social Login > GitHub > ClientId) |
| **ATK_AUTH_GITHUB_CLIENT_SECRET** | `""` | ClientSecret | auth.github.client_secret (Social Login > GitHub > ClientSecret) |
| **ATK_AUTH_GITHUB_ENABLED** | `false` | 启用 | auth.github.enabled (Social Login > GitHub > Enabled) |
| **ATK_AUTH_GITLAB_CLIENT_ID** | `""` | ClientId | auth.gitlab.client_id (Social Login > GitLab > ClientId) |
| **ATK_AUTH_GITLAB_CLIENT_SECRET** | `""` | ClientSecret | auth.gitlab.client_secret (Social Login > GitLab > ClientSecret) |
| **ATK_AUTH_GITLAB_ENABLED** | `false` | 启用 | auth.gitlab.enabled (Social Login > GitLab > Enabled) |
| **ATK_AUTH_GOOGLE_CLIENT_ID** | `""` | ClientId | auth.google.client_id (Social Login > Google > ClientId) |
| **ATK_AUTH_GOOGLE_CLIENT_SECRET** | `""` | ClientSecret | auth.google.client_secret (Social Login > Google > ClientSecret) |
| **ATK_AUTH_GOOGLE_ENABLED** | `false` | 启用 | auth.google.enabled (Social Login > Google > Enabled) |
| **ATK_AUTH_LINE_CLIENT_ID** | `""` | ClientId | auth.line.client_id (Social Login > Line > ClientId) |
| **ATK_AUTH_LINE_CLIENT_SECRET** | `""` | ClientSecret | auth.line.client_secret (Social Login > Line > ClientSecret) |
| **ATK_AUTH_LINE_ENABLED** | `false` | 启用 | auth.line.enabled (Social Login > Line > Enabled) |
| **ATK_AUTH_MASTODON_CLIENT_ID** | `""` | ClientId | auth.mastodon.client_id (Social Login > Mastodon > ClientId) |
| **ATK_AUTH_MASTODON_CLIENT_SECRET** | `""` | ClientSecret | auth.mastodon.client_secret (Social Login > Mastodon > ClientSecret) |
| **ATK_AUTH_MASTODON_ENABLED** | `false` | 启用 | auth.mastodon.enabled (Social Login > Mastodon > Enabled) |
| **ATK_AUTH_MICROSOFT_CLIENT_ID** | `""` | ClientId | auth.microsoft.client_id (Social Login > Microsoft > ClientId) |
| **ATK_AUTH_MICROSOFT_CLIENT_SECRET** | `""` | ClientSecret | auth.microsoft.client_secret (Social Login > Microsoft > ClientSecret) |
| **ATK_AUTH_MICROSOFT_ENABLED** | `false` | 启用 | auth.microsoft.enabled (Social Login > Microsoft > Enabled) |
| **ATK_AUTH_PATREON_CLIENT_ID** | `""` | ClientId | auth.patreon.client_id (Social Login > Patreon > ClientId) |
| **ATK_AUTH_PATREON_CLIENT_SECRET** | `""` | ClientSecret | auth.patreon.client_secret (Social Login > Patreon > ClientSecret) |
| **ATK_AUTH_PATREON_ENABLED** | `false` | 启用 | auth.patreon.enabled (Social Login > Patreon > Enabled) |
| **ATK_AUTH_SLACK_CLIENT_ID** | `""` | ClientId | auth.slack.client_id (Social Login > Slack > ClientId) |
| **ATK_AUTH_SLACK_CLIENT_SECRET** | `""` | ClientSecret | auth.slack.client_secret (Social Login > Slack > ClientSecret) |
| **ATK_AUTH_SLACK_ENABLED** | `false` | 启用 | auth.slack.enabled (Social Login > Slack > Enabled) |
| **ATK_AUTH_STEAM_API_KEY** | `""` | ApiKey | auth.steam.api_key (Social Login > Steam > ApiKey) |
| **ATK_AUTH_STEAM_ENABLED** | `false` | 启用 | auth.steam.enabled (Social Login > Steam > Enabled) |
| **ATK_AUTH_TIKTOK_CLIENT_ID** | `""` | ClientId | auth.tiktok.client_id (Social Login > Tiktok > ClientId) |
| **ATK_AUTH_TIKTOK_CLIENT_SECRET** | `""` | ClientSecret | auth.tiktok.client_secret (Social Login > Tiktok > ClientSecret) |
| **ATK_AUTH_TIKTOK_ENABLED** | `false` | 启用 | auth.tiktok.enabled (Social Login > Tiktok > Enabled) |
| **ATK_AUTH_TWITTER_CLIENT_ID** | `""` | ClientId | auth.twitter.client_id (Social Login > Twitter > ClientId) |
| **ATK_AUTH_TWITTER_CLIENT_SECRET** | `""` | ClientSecret | auth.twitter.client_secret (Social Login > Twitter > ClientSecret) |
| **ATK_AUTH_TWITTER_ENABLED** | `false` | 启用 | auth.twitter.enabled (Social Login > Twitter > Enabled) |
| **ATK_AUTH_WECHAT_CLIENT_ID** | `""` | ClientId | auth.wechat.client_id (Social Login > WeChat > ClientId) |
| **ATK_AUTH_WECHAT_CLIENT_SECRET** | `""` | ClientSecret | auth.wechat.client_secret (Social Login > WeChat > ClientSecret) |
| **ATK_AUTH_WECHAT_ENABLED** | `false` | 启用 | auth.wechat.enabled (Social Login > WeChat > Enabled) |
## Cache
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_CACHE_ENABLED** | `false` | Enable cache | cache.enabled (Cache > Enable cache) |
| **ATK_CACHE_EXPIRES** | `30` | Cache expiration time (in minutes) | cache.expires (Cache > Cache expiration time) |
| **ATK_CACHE_REDIS_DB** | `0` | Redis database number (e.g. 0) | cache.redis.db (Cache > Redis config > Redis database number) |
| **ATK_CACHE_REDIS_NETWORK** | `"tcp"` | Connection type (可选:`["tcp", "unix"]`) | cache.redis.network (Cache > Redis config > Connection type) |
| **ATK_CACHE_REDIS_PASSWORD** | `""` | Redis password | cache.redis.password (Cache > Redis config > Redis password) |
| **ATK_CACHE_REDIS_USERNAME** | `""` | Redis username | cache.redis.username (Cache > Redis config > Redis username) |
| **ATK_CACHE_SERVER** | `""` | Cache server address (e.g. "localhost:6379") | cache.server (Cache > Cache server address) |
| **ATK_CACHE_TYPE** | `"builtin"` | Cache type (可选:`["redis", "memcache", "builtin"]`) | cache.type (Cache > Cache type) |
| **ATK_CACHE_WARM_UP** | `false` | Cache warm up (warm up cache when program starts) | cache.warm_up (Cache > Cache warm up) |
## Captcha
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_CAPTCHA_ACTION_LIMIT** | `3` | Action limit (the number of actions required to activate captcha) | captcha.action_limit (Captcha > Action limit) |
| **ATK_CAPTCHA_ACTION_RESET** | `60` | Reset Timeout (timeout to reset action counter. unit: s, set to -1 to disable) | captcha.action_reset (Captcha > Reset Timeout) |
| **ATK_CAPTCHA_ALWAYS** | `false` | Captcha is required always | captcha.always (Captcha > Captcha is required always) |
| **ATK_CAPTCHA_CAPTCHA_TYPE** | `"image"` | Captcha type (可选:`["image", "turnstile", "recaptcha", "hcaptcha", "geetest"]`) | captcha.captcha_type (Captcha > Captcha type) |
| **ATK_CAPTCHA_ENABLED** | `true` | Enable captcha | captcha.enabled (Captcha > Enable captcha) |
| **ATK_CAPTCHA_GEETEST_CAPTCHA_ID** | `""` | CaptchaId | captcha.geetest.captcha_id (Captcha > Geetest > CaptchaId) |
| **ATK_CAPTCHA_GEETEST_CAPTCHA_KEY** | `""` | CaptchaKey | captcha.geetest.captcha_key (Captcha > Geetest > CaptchaKey) |
| **ATK_CAPTCHA_HCAPTCHA_SECRET_KEY** | `""` | SecretKey | captcha.hcaptcha.secret_key (Captcha > hCaptcha > SecretKey) |
| **ATK_CAPTCHA_HCAPTCHA_SITE_KEY** | `""` | SiteKey | captcha.hcaptcha.site_key (Captcha > hCaptcha > SiteKey) |
| **ATK_CAPTCHA_RECAPTCHA_SECRET_KEY** | `""` | SecretKey | captcha.recaptcha.secret_key (Captcha > reCaptcha > SecretKey) |
| **ATK_CAPTCHA_RECAPTCHA_SITE_KEY** | `""` | SiteKey | captcha.recaptcha.site_key (Captcha > reCaptcha > SiteKey) |
| **ATK_CAPTCHA_TURNSTILE_SECRET_KEY** | `""` | SecretKey | captcha.turnstile.secret_key (Captcha > Turnstile > SecretKey) |
| **ATK_CAPTCHA_TURNSTILE_SITE_KEY** | `""` | SiteKey | captcha.turnstile.site_key (Captcha > Turnstile > SiteKey) |
## Database
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_DB_CHARSET** | `"utf8mb4"` | Database charset | db.charset (Database > Database charset) |
| **ATK_DB_FILE** | `"./data/artalk.db"` | Database file (only for SQLite) | db.file (Database > Database file) |
| **ATK_DB_HOST** | `"localhost"` | Host address | db.host (Database > Host address) |
| **ATK_DB_NAME** | `"artalk"` | Database name | db.name (Database > Database name) |
| **ATK_DB_PASSWORD** | `""` | Database password | db.password (Database > Database password) |
| **ATK_DB_PORT** | `3306` | Host port | db.port (Database > Host port) |
| **ATK_DB_PREPARE_STMT** | `true` | Prepared Statement | db.prepare_stmt (Database > Prepared Statement) |
| **ATK_DB_SSL** | `false` | Enable SSL mode | db.ssl (Database > Enable SSL mode) |
| **ATK_DB_TABLE_PREFIX** | `""` | Table prefix (e.g. "atk_") | db.table_prefix (Database > Table prefix) |
| **ATK_DB_TYPE** | `"sqlite"` | Database type (可选:`["sqlite", "mysql", "pgsql", "mssql"]`) | db.type (Database > Database type) |
| **ATK_DB_USER** | `"root"` | Database user | db.user (Database > Database user) |
## Email
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_EMAIL_ALI_DM_ACCESS_KEY_ID** | `""` | AccessKeyId | email.ali_dm.access_key_id (Email > Aliyun mail push > AccessKeyId) |
| **ATK_EMAIL_ALI_DM_ACCESS_KEY_SECRET** | `""` | AccessKeySecret | email.ali_dm.access_key_secret (Email > Aliyun mail push > AccessKeySecret) |
| **ATK_EMAIL_ALI_DM_ACCOUNT_NAME** | `"noreply@example.com"` | AccountName | email.ali_dm.account_name (Email > Aliyun mail push > AccountName) |
| **ATK_EMAIL_ENABLED** | `false` | Enable email notification | email.enabled (Email > Enable email notification) |
| **ATK_EMAIL_MAIL_SUBJECT** | `"[{{site_name}}] You got a reply from @{{reply_nick}}"` | Email subject | email.mail_subject (Email > Email subject) |
| **ATK_EMAIL_MAIL_TPL** | `"default"` | Email template file (set to file path to use custom template) | email.mail_tpl (Email > Email template file) |
| **ATK_EMAIL_SEND_ADDR** | `"noreply@example.com"` | Email address of sender | email.send_addr (Email > Email address of sender) |
| **ATK_EMAIL_SEND_NAME** | `"{{reply_nick}}"` | Nick name of sender | email.send_name (Email > Nick name of sender) |
| **ATK_EMAIL_SEND_TYPE** | `"smtp"` | Send method (可选:`["smtp", "ali_dm", "sendmail"]`) | email.send_type (Email > Send method) |
| **ATK_EMAIL_SMTP_HOST** | `"smtp.qq.com"` | Email address of sender | email.smtp.host (Email > SMTP send > Email address of sender) |
| **ATK_EMAIL_SMTP_PASSWORD** | `""` | Password | email.smtp.password (Email > SMTP send > Password) |
| **ATK_EMAIL_SMTP_PORT** | `587` | Email port | email.smtp.port (Email > SMTP send > Email port) |
| **ATK_EMAIL_SMTP_USERNAME** | `"example@qq.com"` | Email address of sender | email.smtp.username (Email > SMTP send > Email address of sender) |
## UI Settings
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_FRONTEND_DARKMODE** | `"inherit"` | Dark mode (可选:`["inherit", "auto"]`) | frontend.darkMode (UI Settings > Dark mode) |
| **ATK_FRONTEND_EDITORTRAVEL** | `true` | Movable comment box | frontend.editorTravel (UI Settings > Movable comment box) |
| **ATK_FRONTEND_EMOTICONS** | `"https://cdn.jsdelivr.net/gh/ArtalkJS/Emoticons/grps/default.json"` | Emoticons | frontend.emoticons (UI Settings > Emoticons) |
| **ATK_FRONTEND_FLATMODE** | `"auto"` | Flatten mode (可选:`["auto", "true", "false"]`) | frontend.flatMode (UI Settings > Flatten mode) |
| **ATK_FRONTEND_GRAVATAR_MIRROR** | `"https://www.gravatar.com/avatar/"` | API URL | frontend.gravatar.mirror (UI Settings > Gravatar > API URL) |
| **ATK_FRONTEND_GRAVATAR_PARAMS** | `"sha256=1&d=mp&s=240"` | API parameters | frontend.gravatar.params (UI Settings > Gravatar > API parameters) |
| **ATK_FRONTEND_HEIGHTLIMIT_CHILDREN** | `400` | Sub-comment area height limit (unit: px) | frontend.heightLimit.children (UI Settings > Content height limit > Sub-comment area height limit) |
| **ATK_FRONTEND_HEIGHTLIMIT_CONTENT** | `300` | Comment content height limit (unit: px) | frontend.heightLimit.content (UI Settings > Content height limit > Comment content height limit) |
| **ATK_FRONTEND_HEIGHTLIMIT_SCROLLABLE** | `false` | Scrollable (scrollable height limit area) | frontend.heightLimit.scrollable (UI Settings > Content height limit > Scrollable) |
| **ATK_FRONTEND_IMGLAZYLOAD** | `false` | Image lazy load (可选:`["false", "native", "data-src"]`) | frontend.imgLazyLoad (UI Settings > Image lazy load) |
| **ATK_FRONTEND_LISTSORT** | `true` | Comment sorting | frontend.listSort (UI Settings > Comment sorting) |
| **ATK_FRONTEND_NESTMAX** | `2` | Maximum nesting level | frontend.nestMax (UI Settings > Maximum nesting level) |
| **ATK_FRONTEND_NESTSORT** | `"DATE_ASC"` | Nesting comment sorting rules (可选:`["DATE_ASC", "DATE_DESC", "VOTE_UP_DESC"]`) | frontend.nestSort (UI Settings > Nesting comment sorting rules) |
| **ATK_FRONTEND_NOCOMMENT** | `""` | Text to display when there is | frontend.noComment (UI Settings > Text to display when there is) |
| **ATK_FRONTEND_PAGINATION_AUTOLOAD** | `true` | Scroll loading | frontend.pagination.autoLoad (UI Settings > Comment pagination > Scroll loading) |
| **ATK_FRONTEND_PAGINATION_PAGESIZE** | `20` | Number of comments per page | frontend.pagination.pageSize (UI Settings > Comment pagination > Number of comments per page) |
| **ATK_FRONTEND_PAGINATION_READMORE** | `true` | Load more mode (disabled to use pagination bar) | frontend.pagination.readMore (UI Settings > Comment pagination > Load more mode) |
| **ATK_FRONTEND_PLACEHOLDER** | `""` | Comment box placeholder | frontend.placeholder (UI Settings > Comment box placeholder) |
| **ATK_FRONTEND_PLUGINURLS** | `[]` | Plugins | frontend.pluginURLs (UI Settings > Plugins) |
| **ATK_FRONTEND_PREVIEW** | `true` | Editor real-time preview | frontend.preview (UI Settings > Editor real-time preview) |
| **ATK_FRONTEND_REQTIMEOUT** | `15000` | Request timeout (unit: ms) | frontend.reqTimeout (UI Settings > Request timeout) |
| **ATK_FRONTEND_SENDBTN** | `""` | Text of the send button | frontend.sendBtn (UI Settings > Text of the send button) |
| **ATK_FRONTEND_UABADGE** | `false` | User UA badge | frontend.uaBadge (UI Settings > User UA badge) |
| **ATK_FRONTEND_VERSIONCHECK** | `true` | Version check | frontend.versionCheck (UI Settings > Version check) |
| **ATK_FRONTEND_VOTE** | `true` | Vote button | frontend.vote (UI Settings > Vote button) |
| **ATK_FRONTEND_VOTEDOWN** | `false` | Vote down button | frontend.voteDown (UI Settings > Vote down button) |
## Web server
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_HTTP_BODY_LIMIT** | `100` | Body size limit (unit: MB) | http.body_limit (Web server > Body size limit) |
| **ATK_HTTP_PROXY_HEADER** | `""` | Proxy Header (fill `X-Forwarded-For` to get user real IP if behind a trusted reverse proxy or CDN) | http.proxy_header (Web server > Proxy Header) |
## Upload
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_IMG_UPLOAD_ENABLED** | `true` | Enable image upload | img_upload.enabled (Upload > Enable image upload) |
| **ATK_IMG_UPLOAD_MAX_SIZE** | `5` | Image size limit (unit: MB) | img_upload.max_size (Upload > Image size limit) |
| **ATK_IMG_UPLOAD_PATH** | `"./data/artalk-img/"` | Image storage | img_upload.path (Upload > Image storage) |
| **ATK_IMG_UPLOAD_PUBLIC_PATH** | `<nil>` | Image link base path (default: "/static/images/") | img_upload.public_path (Upload > Image link base path) |
| **ATK_IMG_UPLOAD_UPGIT_DEL_LOCAL** | `true` | Delete local image after upload success | img_upload.upgit.del_local (Upload > Upgit config > Delete local image after upload success) |
| **ATK_IMG_UPLOAD_UPGIT_ENABLED** | `false` | Enable Upgit | img_upload.upgit.enabled (Upload > Upgit config > Enable Upgit) |
| **ATK_IMG_UPLOAD_UPGIT_EXEC** | `"upgit -c UPGIT_CONF_FILE_PATH -t /artalk-img"` | Command line arguments | img_upload.upgit.exec (Upload > Upgit config > Command line arguments) |
## Logging
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_LOG_ENABLED** | `true` | Enable logging | log.enabled (Logging > Enable logging) |
| **ATK_LOG_FILENAME** | `"./data/artalk.log"` | Log file path | log.filename (Logging > Log file path) |
## Moderator
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_MODERATOR_AKISMET_KEY** | `""` | Akismet Key (Akismet anti-spam service, https://akismet.com) | moderator.akismet_key (Moderator > Akismet Key) |
| **ATK_MODERATOR_ALIYUN_ACCESS_KEY_ID** | `""` | AccessKeyId | moderator.aliyun.access_key_id (Moderator > Aliyun Content Security > AccessKeyId) |
| **ATK_MODERATOR_ALIYUN_ACCESS_KEY_SECRET** | `""` | AccessKeySecret | moderator.aliyun.access_key_secret (Moderator > Aliyun Content Security > AccessKeySecret) |
| **ATK_MODERATOR_ALIYUN_ENABLED** | `false` | 启用 | moderator.aliyun.enabled (Moderator > Aliyun Content Security > Enabled) |
| **ATK_MODERATOR_ALIYUN_REGION** | `"cn-shanghai"` | Region | moderator.aliyun.region (Moderator > Aliyun Content Security > Region) |
| **ATK_MODERATOR_API_FAIL_BLOCK** | `false` | Block when API request fails (set to false to let comments pass when API request fails) | moderator.api_fail_block (Moderator > Block when API request fails) |
| **ATK_MODERATOR_KEYWORDS_ENABLED** | `false` | Enable keyword filter | moderator.keywords.enabled (Moderator > Keyword filter > Enable keyword filter) |
| **ATK_MODERATOR_KEYWORDS_FILE_SEP** | `"\n"` | FileSep | moderator.keywords.file_sep (Moderator > Keyword filter > FileSep) |
| **ATK_MODERATOR_KEYWORDS_FILES** | `[./data/keywords_1.txt]` | Dictionary file (support multiple dictionary files) | moderator.keywords.files (Moderator > Keyword filter > Dictionary file) |
| **ATK_MODERATOR_KEYWORDS_PENDING** | `false` | Set to pending when match | moderator.keywords.pending (Moderator > Keyword filter > Set to pending when match) |
| **ATK_MODERATOR_KEYWORDS_REPLACE_TO** | `"x"` | ReplaceTo | moderator.keywords.replace_to (Moderator > Keyword filter > ReplaceTo) |
| **ATK_MODERATOR_PENDING_DEFAULT** | `false` | Default pending (new comments need to be approved by admin) | moderator.pending_default (Moderator > Default pending) |
| **ATK_MODERATOR_TENCENT_ENABLED** | `false` | 启用 | moderator.tencent.enabled (Moderator > Tencent Cloud Content Security > Enabled) |
| **ATK_MODERATOR_TENCENT_REGION** | `"ap-guangzhou"` | Region | moderator.tencent.region (Moderator > Tencent Cloud Content Security > Region) |
| **ATK_MODERATOR_TENCENT_SECRET_ID** | `""` | SecretId | moderator.tencent.secret_id (Moderator > Tencent Cloud Content Security > SecretId) |
| **ATK_MODERATOR_TENCENT_SECRET_KEY** | `""` | SecretKey | moderator.tencent.secret_key (Moderator > Tencent Cloud Content Security > SecretKey) |
## SSL
| 环境变量 | 默认值 | 描述 | 路径 |
| --- | --- | --- | --- |
| **ATK_SSL_CERT_PATH** | `""` | Certificate file path (e.g. "/etc/letsencrypt/live/example.com/fullchain.pem") | ssl.cert_path (SSL > Certificate file path) |
| **ATK_SSL_ENABLED** | `false` | Enable SSL | ssl.enabled (SSL > Enable SSL) |
| **ATK_SSL_KEY_PATH** | `""` | Key file path (e.g. "/etc/letsencrypt/live/example.com/privkey.pem") | ssl.key_path (SSL > Key file path) |
<!-- /env-variables -->
</div>
## Developers
Enable developer mode by setting `ATK_DEBUG=1`.
This document is auto-generated by the Artalk developer tool. Run `make update-conf-docs` to update this page's content based on the template configuration file ([conf/artalk.example.zh-CN.yml](https://github.com/ArtalkJS/Artalk/tree/master/conf/artalk.example.zh-CN.yml)).
Related code can be found in the [@ArtalkJS/Artalk:/internal/config/](https://github.com/ArtalkJS/Artalk/tree/master/internal/config/) directory.
+3
View File
@@ -0,0 +1,3 @@
# 📚 Further reading
【TODO】
@@ -0,0 +1,17 @@
# ArtalkLite Overview
ArtalkLite is a simplified version of Artalk, with the following differences compared to the standard version:
- Smaller size and more streamlined.
- Emojis, voting, and UA badges are disabled by default.
- Removed the dependency on marked, but supports basic Markdown syntax.
ArtalkLite is released alongside the standard version. You can obtain it by modifying the file name in the CDN address to ArtalkLite:
```
https://unpkg.com/artalk@:ArtalkVersion:/dist/ArtalkLite.js
```
```
https://unpkg.com/artalk@:ArtalkVersion:/dist/ArtalkLite.css
```
+75
View File
@@ -0,0 +1,75 @@
# Social Login
By default, Artalk allows users to post comments by simply filling in their nickname and email without email verification.
However, sometimes we want users to log in with their social accounts to reduce the time spent filling in information or to increase the authenticity of user information. This can be achieved by enabling social login.
Currently, the following social login methods are supported:
| Login Method | Integration Docs | Login Method | Integration Docs | Login Method | Integration Docs |
| ------------ | ---------------- | ------------ | ---------------- | ------------ | ---------------- |
| Google | [View](https://developers.google.com/identity/protocols/oauth2) | Microsoft | [View](https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow) | Apple | [View](https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/configuring_your_webpage_for_sign_in_with_apple) |
| Facebook | [View](https://developers.facebook.com/docs/facebook-login/) | Twitter | [View](https://developer.twitter.com/en/docs/basics/authentication/overview) | Discord | [View](https://discord.com/developers/docs/topics/oauth2) |
| Slack | [View](https://api.slack.com/authentication/oauth-v2) | GitHub | [View](https://developer.github.com/apps/building-oauth-apps/authorizing-oauth-apps/) | TikTok | [View](https://developers.tiktok.com/doc/login) |
| Steam | [View](https://partner.steamgames.com/doc/webapi_overview/auth) | WeChat | [View](https://developers.weixin.qq.com/doc/oplatform/Website_App/WeChat_Login/Wechat_Login.html) | Line | [View](https://developers.line.biz/en/docs/line-login/integrate-line-login/) |
| GitLab | [View](https://docs.gitlab.com/ee/api/oauth2.html) | Gitea | [View](https://docs.gitea.io/en-us/oauth2-provider/) | Mastodon | [View](https://docs.joinmastodon.org/api/authentication/) |
| Patreon | [View](https://docs.patreon.com/#oauth) | Auth0 | [View](https://auth0.com/docs/connections/social/) | Email & Password | [View](#email-password-login) |
To enable social login, simply find the "Social Login" option in the [Dashboard](./sidebar.md#settings), enable it, and fill in the corresponding configuration information. Alternatively, you can configure it through the [configuration file](../backend/config.md) or [environment variables](../env.md#social-login).
## Email & Password Login
![Email Login](/images/auth/email_login.png)
After enabling email and password login, the nickname and email input fields at the top of the comment box will be hidden, and the send button will change to a login button. When the user clicks the login button, a login box will pop up, allowing the user to log in with their email and password. Once logged in, the user can post comments. Comments posted by the user will display a "Email Verified" badge.
<img src="/images/auth/email_verified.png" width="550" alt="Email Verified Badge">
Users can register an account via email, and Artalk will send a verification code to their email. The verification code is valid for 10 minutes, and the frequency of sending verification codes is limited to once per minute.
![Email Registration](/images/auth/email_register.png)
You can customize the verification email template and subject. In the settings page of the Artalk Dashboard under social login, you can find options for "Email Verification Subject" and "Email Verification Template". In the configuration file, you can set them using `auth.email.verify_subject` and `auth.email.verify_tpl`:
```yaml
auth:
enabled: true
email:
enabled: true
verify_subject: "Your verification code is - {{code}}"
verify_tpl: default
```
The default template is as follows:
```html
Your verification code is: {{code}}. Please use it to verify your email and log in to Artalk. If you did not request this, please ignore this message.
```
![Skip Login](/images/auth/login_skip.png)
After enabling email and password login, users can still skip email verification: the login popup will show a "Skip, do not verify" button at the bottom, which, when clicked, restores the original nickname, email, and website input fields at the top of the comment box. You can change this by selecting "Allow Anonymous Comments" in the settings.
## Account Merging Tool
If multiple accounts with different usernames but the same email are detected after logging in, an account merging tool will pop up. Users can choose to keep one username, and all comments and data associated with that email will be merged into the retained account. The original accounts will be deleted, and the displayed username on comments will change to the retained username.
![Account Merging Tool](/images/auth/merge_accounts.png)
## Multiple Login Methods
Artalk supports enabling multiple login methods simultaneously, allowing users to choose any method to log in.
![Multiple Login Methods](/images/auth/multi_login.png)
If only one login method is enabled, such as GitHub login, the GitHub authorization login page will pop up directly.
![GitHub Authorization Popup](/images/auth/github_login.png)
For integrating GitHub login, refer to the documentation: [About Creating GitHub Apps](https://docs.github.com/en/developers/apps/building-oauth-apps/creating-an-oauth-app). After obtaining the Client ID and Client Secret, fill them in the "GitHub" option in the social login settings page of the Artalk Dashboard.
## Plugin Development
The social login feature of Artalk is implemented through an independent plugin developed using Solid.js. The code can be found in [@ArtalkJS/Artalk:ui/plugin-auth](https://github.com/ArtalkJS/Artalk/tree/master/ui/plugin-auth).
After enabling the social login feature in the Dashboard, the plugin will be automatically loaded on the front end.
+541
View File
@@ -0,0 +1,541 @@
# UI Configuration
UI configuration also known as Client (Frontend) configuration, is the configuration of the Artalk interface.
You can modify the UI configuration in the "[Dashboard](./sidebar.md#dashboard)" without changing the frontend code. Additionally, [Configuration files](../backend/config.md#frontend-configuration-frontend) and [Environment variables](../env.md#ui-settings) are also supported.
The priority of UI configuration is as follows:
```
Frontend Code > Environment Variables > Dashboard = Configuration File
```
If you have modified the UI configuration through environment variables, configuration files, or the Dashboard, but the changes are not taking effect, please consider the issue of UI configuration priority.
## Configuring the Interface via `Artalk.init`
When initializing with `Artalk.init` on the frontend page, pass parameters to configure the interface. Below are all the available configuration options.
```js
const artalk = Artalk.init({
el: '#Comments',
pageKey: '/post/1',
pageTitle: 'Page Title',
server: 'http://your_domain:8080',
site: 'Artalk Blog',
})
// Update configuration
artalk.update({ ... })
```
- Default Configuration: [defaults.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/defaults.ts)
- Declaration File: [config.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/types/config.ts)
## Basic Configuration (Required)
### el
**Mount Element** (Specify the element selector to bind)
- Type: `String|HTMLElement`
- Default: `undefined`
> Example: `#Comments` corresponds to the element `<div id="Comments"></div>`
### pageKey
**Page Address** (Relative path / full URL)
- Type: `String`
- Default: `location.pathname`
Leave empty to automatically get the relative path of the page.
You can fill in the `permalink` generated by the blog system, but it is recommended to use the relative path for easier domain switching in the future.
Reference: [Using Relative / Absolute Paths](../backend/relative-path.md)
### pageTitle
**Page Title** (Used for management list display, email notifications, etc.)
- Type: `String`
- Default: `document.title`
Leave empty to automatically get the value of the `<title>` tag of the page.
### server
**Backend Program API Address**
- Type: `String`
- Default: `undefined`
Deploy the backend and ensure that the backend address is accessible from the front end.
> Example: http://yourdomain.xxx
### site
**Site Name**
- Type: `String`
- Default: `undefined`
Artalk supports unified management of multiple sites, this item is used for site isolation.
### preferRemoteConf
**Prefer Remote Configuration**
- Type: `Boolean`
- Default: `false` (disabled by default)
This config option is disabled by default, meaning Artalk will prioritize using local config. Local config refers to the settings passed through `Artalk.init` in the frontend code.
When enabled, Artalk will prioritize using remote config. If the remote config does not exist, it will resort to using the local config. Remote config refers to the settings returned by the backend server program, allowing for dynamic config of the Artalk client. You can modify the user interface config in the "[Dashboard](./sidebar.md#dashboard)".
::: warning Update Notice
As of version v2.10.0, the `useBackendConf` configuration option has been deprecated and is always `true`. Please use `preferRemoteConf` instead.
:::
## Internationalization (i18n)
### locale
**Language**
- Type: `String|Object|"auto"`
- Default: `"zh-CN"`
Following the Unicode BCP 47 standard, the default is "zh-CN" (Simplified Chinese).
Feel free to submit a PR to help translate Artalk into multiple languages and contribute to the community!
For details, see: [Localization](./i18n.md)
### dateFormatter
**Date Formatting Function**
- Type: `(date: Date) => string`
- Default: `undefined`
By default, it shows a few seconds ago, a few minutes ago, a few hours ago, a few days ago, and if it exceeds 7 days, it shows the specific date in the format `YYYY-MM-DD`.
You can also customize the date formatting function. Below is an example using [toLocaleString](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleString) and [dayjs](https://day.js.org/) to format dates.
```js
import dayjs from 'dayjs'
Artalk.init({
dateFormatter: (date) => {
// return date.toLocaleString() // '2024/8/28 17:51:31'
return dayjs(date).fromNow("MMMM D, YYYY h:mm A") // 'August 28, 2024 5:51 PM'
},
})
```
## Requests
### reqTimeout
**Request Timeout**
- Type: `Number`
- Default: `15000`
Automatically disconnects the request and reports an error if the request time exceeds this value (unit: milliseconds).
## Emoticons
### emoticons
**Emoticons**
- Type: `Object|Array|String|Boolean`
- Default: "[https://cdn.jsdelivr.net/gh/ArtalkJS/Emoticons/grps/default.json](https://cdn.jsdelivr.net/gh/ArtalkJS/Emoticons/grps/default.json)"
For details: [Frontend · Emoticons](./emoticons.md)
Now compatible with [OwO format](https://github.com/DIYgod/OwO), supports dynamic loading by URL.
Set to `false` to disable the emoticon feature.
## Interface
### placeholder
**Comment Box Placeholder Text**
- Type: `String`
- Default: `"Type something..."`
### noComment
**Text Displayed When There Are No Comments**
- Type: `String`
- Default: `"「Silence is golden」"`
### sendBtn
**Send Button Text**
- Type: `String`
- Default: `"Post Comment"`
### editorTravel
**Comment Box Travel**
- Type: `Boolean`
- Default: `true`
Set to `true` to move the comment box to the position of the comment being replied to, instead of keeping it fixed.
### darkMode
**Dark Mode**
- Type: `Boolean|"auto"`
- Default: `false`
When Artalk is instantiated, it reads this value and chooses whether to enable dark mode (can be used with the blog theme).
To dynamically modify darkMode:
```js
artalk.setDarkMode(true)
```
> Reference code: “[index.html](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/index.html#L97-L150)”
Set to `"auto"`, Artalk will listen to `(prefers-color-scheme: dark)` and automatically switch to dark mode based on the user's operating system settings.
### flatMode
**Flat Mode**
- Type: `Boolean|"auto"`
- Default: `"auto"`
By default, `"auto"` automatically enables "flat mode" on small screen devices (screen width < 768px).
Set to `true` to display comments in "flat mode".
Set to `false` to display comments in "nested mode".
### nestMax
**Maximum Nested Levels**
- Type: `Number`
- Default: `2`
Maximum nested levels for comments in "nested mode".
### nestSort
**Sorting Rules for Nested Comments**
- Type: `"DATE_ASC"|"DATE_DESC"|"VOTE_UP_DESC"`
- Default: `"DATE_ASC"`
By default, nested comments are sorted in ascending order by date (new comments at the end).
## Features
### pvEl
**Page Views (PV) Binding Element**
- Type: `String`
- Default: `".artalk-pv-count"`
You can place an HTML tag anywhere on the page: `<span class="artalk-pv-count"></span>`
When Artalk finishes loading, it displays the page views.
This item specifies the selector of the binding element, defaulting to `.artalk-pv-count`.
### countEl
**Comment Count Binding Element**
- Type: `String`
- Default: `".artalk-comment-count"`
You can place an HTML tag anywhere on the page: `<span class="artalk-comment-count"></span>` to display the current page's comment count.
::: tip
Both pvEl and countEl element tags can set the `data-page-key` attribute to specify the statistics of a particular page, for example: `<span class="artalk-comment-count" data-page-key="/t/1.html"></span>`
For details, see: [PV Statistics](./pv.md#Loading statistics for multiple pages simultaneously)
:::
### statPageKeyAttr
**Statistical Component PageKey Attribute Name**
- Type: `String`
- Default: `"data-page-key"`
When querying comment counts and page views, Artalk's statistical component uses this attribute name to query the specified page, for example: `<span data-page-key="/t/1.html"></span>`.
To facilitate theme adaptation, you can customize the attribute name as needed, for example, replacing it with `data-path`, the HTML tag would be `<span data-path="/t/1.html"></span>`.
### pageVote
**Page Voting Buttons**
- Type: `Boolean | { upBtnEl: string; downBtnEl: string; upCountEl: string; downCountEl: string; activeClass: string }`
- Default: `true`
Enable the page voting feature (upvote / downvote).
For details, see: [Page Voting](./voting.md#page-voting)
### vote
**Voting Buttons**
- Type: `Boolean`
- Default: `true`
Enable the comment voting feature (upvote / downvote).
### voteDown
**Downvote Button**
- Type: `Boolean`
- Default: `false`
Downvote button (hidden by default).
### uaBadge
**Display User's UserAgent Information Badge**
- Type: `Boolean`
- Default: `false`
### listSort
**Comment Sorting Feature**
- Type: `Boolean`
- Default: `true`
Hover over the "n comments" in the top left of the comment list to display a floating dropdown, allowing the comment list to be sorted and filtered according to "latest / hottest / earliest / author".
### imgUpload
**Image Upload Feature**
- Type: `Boolean`
- Default: `true`
This configuration item automatically follows the backend. When the backend image upload feature is disabled, only administrators will see the image upload button.
### imgUploader
**Image Uploader**
- Type: `(file: File) => Promise<string>`
- Default: `undefined`
Custom image uploader, for example:
```js
Artalk.init({
imgUploader: async (file) => {
const form = new FormData()
form.set('file', file)
const imgUrl = await fetch('https://api.example.org/upload', {
method: 'POST',
body: form,
})
return imgUrl
},
})
```
### imgLazyLoad
**Lazy Load Images**
- Type: `"native"|"data-src"|Boolean`
- Default: `false`
Enable lazy loading of images in comments.
For details, see: [Lazy Load Images](./img-lazy-load.md)
### preview
**Editor Real-Time Preview Feature**
- Type: `Boolean`
- Default: `true`
Display the "Preview" button in the editor.
## Avatars
```js
gravatar: {
mirror: '<Gravatar Mirror URL>',
default: 'mp',
}
```
### gravatar.mirror
**Gravatar Mirror URL**
- Type: `String`
- Default: `"https://www.gravatar.com/avatar/"`
If you find Gravatar avatar loading speed unsatisfactory, you can try replacing it.
For example:
> WeAvatar: https://weavatar.com/avatar/
>
> Cravatar: https://cravatar.cn/avatar/
>
> V2EX: https://cdn.v2ex.com/gravatar/
>
> Geekzu: https://sdn.geekzu.org/avatar/
>
> Loli: https://gravatar.loli.net/avatar/
### gravatar.params
**Gravatar API Parameters**
- Type: `String`
- Default: `"sha256=1&d=mp&s=240"`
For example, you can set the default avatar (`d=mp`) and avatar size (`s=240`) through this configuration item.
Reference: [Gravatar API Documentation](http://cn.gravatar.org/site/implement/images/)
This configuration item is in HTTP Query format.
::: warning Update Notice
v2.8.7 supports generating Gravatar avatar links using the SHA256 encryption algorithm to enhance user privacy protection. Please include `sha256=1` in `params` to enable this encryption ([#874](https://github.com/ArtalkJS/Artalk/issues/874)).
v2.5.5 deprecated the `gravatar.default` configuration item; please use `gravatar.params` instead.
:::
### avatarURLBuilder
**Avatar URL Builder**
- Type: `(comment: CommentData) => string`
- Default: `undefined`
Custom user avatar image URL generator, for example:
```js
Artalk.init({
avatarURLBuilder: (comment) => {
return `/api/avatar?email=${comment.email_encrypted}`
},
})
```
## Comment Pagination
```js
pagination: {
pageSize: 20, // Number of comments per page
readMore: true, // Load more or pagination
autoLoad: true, // Auto-load (load more)
}
```
### pagination.readMore
**Load More Mode**
- Type: `Boolean`
- Default: `true`
Set to `true` for "Load More" mode.
Set to `false` for "Pagination" mode.
### pagination.autoLoad
**Auto-Load on Scroll**
- Type: `Boolean`
- Default: `true`
(Must enable "Load More" mode by setting `readMore` to `true`)
### pagination.pageSize
**Number of Comments Per Request**
- Type: `Number`
- Default: `20`
## Content Height Limit
Content exceeding the set height will be hidden, and a "Read More" button will be displayed.
```js
heightLimit: {
content: 300, // Comment content height limit
children: 400, // Child comment area height limit
scrollable: false, // Height limit scrolling
}
```
### heightLimit.content
**Comment Content Height Limit**
- Type: `Number`
- Default: `300`
> Set to 0 to disable height limit.
### heightLimit.children
**Child Comment Area Height Limit**
- Type: `Number`
- Default: `400`
### heightLimit.scrollable
**Scrollable Height Limit Area**
- Type: `Boolean`
- Default: `false`
Allow height limit area to scroll.
## Version Check
### versionCheck
**Version Check**
- Type: `Boolean`
- Default: `true`
Display a warning prompt when the frontend and backend versions are incompatible.
+180
View File
@@ -0,0 +1,180 @@
# Emoticons
You can modify this configuration in the settings interface of the [Dashboard](./sidebar.md#设置), or through [configuration files](../backend/config.md#界面配置-frontend) and [environment variables](../env.md#界面配置).
In the configuration file, you can fill in the URL of the emoticon list under `frontend.emoticons`:
```yaml
frontend:
emoticons: https://raw.githubusercontent.com/ArtalkJS/Emoticons/master/grps/default.json
```
## Emoticon Presets
The Artalk community offers many emoticon presets. You can choose a few favorite sets and easily add them to your comment system with simple configurations. Visit the repository: [@ArtalkJS/Emoticons](https://github.com/ArtalkJS/Emoticons).
## Supported Formats
### OwO Format
[OwO](https://github.com/DIYgod/OwO) is an open-source JS plugin developed by [@DIYgod](https://github.com/DIYgod) that allows quick insertion of emoticons into the input box.
Artalk's emoticon feature draws inspiration from its excellent design and natively supports and is compatible with OwO format emoticon data files, as shown below:
```yaml
frontend:
emoticons: https://raw.githubusercontent.com/DIYgod/OwO/master/demo/OwO.json
# Directly use OwO format emoticons ↑↑
```
The community also has many OwO format emoticon resources that can be used directly, for example: [@2X-ercha/Twikoo-Magic](https://github.com/2X-ercha/Twikoo-Magic).
### Artalk Emoticon List File Standard Format
In addition to supporting the OwO format, Artalk also natively supports a standard format for emoticon list files:
```js
[
{
name: 'Emoji',
type: 'emoticon', // Text type
items: [
{ key: 'Hi', val: '|´・ω・)ノ' },
{ key: 'Happy', val: 'ヾ(≧∇≦*)ゝ' },
//...
],
},
{
name: 'Funny',
type: 'image', // Image type
items: [
{
key: 'Original Funny',
val: '<Image URL>',
},
//...
],
},
]
```
## Front-end Configuration
To configure emoticon lists on the front end, for example:
```js
Artalk.init({
// Default emoticon list, dynamically imported ↓↓
emoticons:
'https://raw.githubusercontent.com/ArtalkJS/Emoticons/master/grps/default.json',
})
```
::: tip
Configuration file and dashboard emoticon settings have a higher priority than front-end configuration.
:::
## Disabling Emoticons
You can disable the emoticon feature by setting `emoticons` to `false`:
```js
Artalk.init({
emoticons: false,
})
```
## Loading Methods
### Dynamic Loading
Set the `emoticons` attribute to the URL of the emoticon data file. When the emoticon list is opened, Artalk will dynamically import it.
```js
Artalk.init({
emoticons: '<Emoticon Data File URL>',
})
```
Remote emoticon files support both Artalk and OwO formats, and support nested and mixed loading.
### Static Loading
Compared to dynamic importing, you can statically save the emoticon list object in the JS code of the page to avoid dynamic loading:
```js
Artalk.init({
emoticons: [
{
name: 'Emoji',
type: 'emoticon', // Text type
items: [
{ key: 'Hi', val: '|´・ω・)ノ' },
{ key: 'Happy', val: 'ヾ(≧∇≦*)ゝ' },
//...
],
},
{
name: 'Funny',
type: 'image', // Image type
items: [
{
key: 'Original Funny',
val: '<Image URL>',
},
//...
],
},
],
})
```
### Mixed Loading
Artalk supports a mix of **dynamic** and **static** loading, for example:
```js
Artalk.init({
emoticons: [
// Dynamic loading
'https://raw.githubusercontent.com/DIYgod/OwO/master/demo/OwO.json', // OwO format emoticons
'https://raw.githubusercontent.com/qwqcode/huaji/master/huaji.json',
// Static loading
{
name: 'Emoticon Name',
type: 'emoticon', // Text type
items: [
{ key: 'Go Master Ball', val: '(╯°A°)╯︵○○○' },
//...
],
},
],
})
```
### Nested Import
Artalk supports **nested import** of other emoticon resources within remote emoticon resources, for example:
```js
Artalk.init({
emoticons: ['https://example.org/emoticons.json'],
})
```
Data in `emoticons.json`:
```json
[
"https://example.org/other-emoticons.json",
//...
{
// Artalk format, OwO format
//...
}
]
```
This allows you to efficiently manage and load multiple emoticon sets with minimal configuration.
+73
View File
@@ -0,0 +1,73 @@
# Localization
You can select the language in the settings page of the Artalk Dashboard, or set the language of Artalk through the environment variable `ATK_LOCALE` and the `locale` configuration item in the `artalk.yml` configuration file.
```yml
locale: en-US
```
The `locale` configuration item follows the [Unicode BCP 47](https://www.techonthenet.com/js/language_tags.php) standard and defaults to "en-US" (English).
---
Currently, Artalk supports the following languages:
- "en" (English)
- "zh-CN" (简体中文)
- "zh-TW" (繁体中文)
- "ja" (日本語)
- "ko" (한국어)
- "fr" (Français)
- "ru" (Русский)
## Contributing to Translations
We welcome PRs to help translate Artalk into multiple languages and contribute to the community!
| Translation Content | Language File Directory | Template File |
| ------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Backend Program | [/i18n/[LANG].yml](https://github.com/ArtalkJS/Artalk/tree/master/i18n) | [en.yml](https://github.com/ArtalkJS/Artalk/blob/master/i18n/en.yml) |
| Frontend Interface | [/ui/artalk/src/i18n/[LANG].ts](https://github.com/ArtalkJS/Artalk/tree/master/ui/artalk/src/i18n) | [en.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/i18n/en.ts) |
| Backend Interface | [/ui/artalk-sidebar/src/i18n/[LANG].ts](https://github.com/ArtalkJS/Artalk/tree/master/ui/artalk-sidebar/src/i18n) | [i18n-en.ts](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk-sidebar/src/i18n-en.ts) |
| Configuration Files | [/conf/artalk.example.[LANG].yml](https://github.com/ArtalkJS/Artalk/tree/master/conf) | [artalk.example.yml](https://github.com/ArtalkJS/Artalk/blob/master/conf/artalk.example.yml) |
| Documentation | [/docs/docs/[LANG]/\*\*/\*.md](https://github.com/ArtalkJS/Artalk/tree/master/docs/docs) | [en/\*\*/\*.md](https://github.com/ArtalkJS/Artalk/tree/master/docs/docs/en) |
| Official website home page | [/docs/landing/src/i18n/[LANG].ts](https://github.com/ArtalkJS/Artalk/tree/master/docs/landing/src/i18n) | [en.ts](https://github.com/ArtalkJS/Artalk/blob/master/docs/landing/src/i18n/en.ts) |
For more details, refer to: [Development Documentation](../../develop/index.md) / [CONTRIBUTING.md](https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md#translation)
## Advanced Configuration
### Temporarily Changing Language on the Frontend
The frontend will use the backend's language configuration by default, but you can also set the language through the `locale` configuration item on the frontend:
```js
Artalk.init({
locale: 'en-US',
})
```
### Automatically Switching Language on the Frontend
You can set the front-end locale to `"auto"` to automatically switch the language based on the user's browser settings. If the language does not exist, it will default to "en-US".
```js
Artalk.init({
locale: 'auto',
})
```
### Custom Frontend Locale Content
You can pass an Object type to the frontend and customize the locale content according to the keys in the [template file](https://github.com/ArtalkJS/Artalk/blob/master/ui/artalk/src/i18n/en.ts).
```js
Artalk.init({
locale: {
email: 'Eメール',
//...
},
})
```
By following these steps, you can easily configure and customize the language settings for Artalk to better suit your audience.
@@ -0,0 +1,55 @@
# Image Lazy Loading
Artalk supports adding lazy loading functionality to images within comments to reduce page load times. This feature is disabled by default. You can find the "Image Lazy Load" configuration item (frontend.imgLazyLoad) in the Dashboard under "Settings - UI Configuration":
| Configuration Value | Description |
| --- | --- |
| `native` | Use the browser's native image lazy loading |
| `data-src` | Use a lazy loading library for image lazy loading |
| `false` | Disable image lazy loading |
## Native Browser Support
When the image lazy loading is set to `native`, Artalk will use the browser's native image lazy loading feature, which adds the `loading="lazy"` attribute to the image tag. For example:
```html
<img src="1.png" loading="lazy" />
```
This method does not require additional libraries or code and is the simplest approach. However, some browsers may not support this attribute, or their lazy loading strategies may vary. For more details, refer to: [MDN - Lazy Loading](https://developer.mozilla.org/zh-CN/docs/Web/Performance/Lazy_loading).
## Lazy Loading Library
Using a lazy loading library ensures consistent behavior across different browsers and can offer additional features, such as image loading animations. If your blog theme comes with a lazy loading library, you can leverage it to enable lazy loading in Artalk as well.
When the image lazy loading is set to `data-src`, Artalk will add the `class="lazyload"` and `data-src` attributes to the image tag. For example:
```html
<img data-src="1.png" class="lazyload" />
```
In this case, you need to include an additional image lazy loading library, such as [vanilla-lazyload](https://github.com/verlok/vanilla-lazyload). Add the following code to the `<head>` of your page:
```html
<script src="https://unpkg.com/vanilla-lazyload/dist/lazyload.iife.min.js"></script>
```
Then, write the code to add an event listener before initializing Artalk. This listener will call the `update` method of the lazy loading library when the comment list is updated:
```js
// Initialize the image lazy loading library
const lazyLoadInstance = new LazyLoad({
elements_selector: '.lazyload',
threshold: 0,
})
// Listen to Artalk events
Artalk.use((ctx) => {
ctx.on('list-loaded', () => lazyLoadInstance.update())
})
// Initialize Artalk
const artalk = Artalk.init({ /* ... */ })
```
By following these steps, you can ensure that images within Artalk comments are efficiently lazy-loaded, improving the overall performance and user experience of your site.
+46
View File
@@ -0,0 +1,46 @@
# IP Region
Artalk has a built-in feature to display the geolocation of user IPs, with adjustable precision levels: city or province.
This feature is disabled by default. You can enable the IP region display feature in the Artalk Dashboard settings.
## IP Region Database
Before enabling the IP region display feature, you need to download a database file:
- [GitHub Download](https://github.com/lionsoul2014/ip2region/raw/master/data/ip2region.xdb) / [Mirror Download](https://gh-proxy.com/?q=https%3A%2F%2Fgithub.com%2Flionsoul2014%2Fip2region%2Fblob%2Fmaster%2Fdata%2Fip2region.xdb) (recommended within China)
After downloading, manually place it in the `./data/` directory, and name the file: `ip2region.xdb`.
## Precision Settings
You can find this configuration item in the settings.
| Precision Level | Description | Example |
| --------------- | ----------------- | ------------- |
| `province` | Province (default) | `Sichuan` |
| `city` | City | `Sichuan Chengdu` |
| `country` | Country/Region | `China` |
Configuration file:
```yaml
# IP Region
ip_region:
# Enable IP region display
enabled: false
# Data file path (.xdb format)
db_path: ./data/ip2region.xdb
# Display precision ["province", "city", "country"]
precision: province
```
## Obtaining the Correct IP Address
If you are using a CDN or a trusted reverse proxy server like Nginx, you need to specify the request header field containing the user's real IP in the "Settings" - "Server" option - "Proxy Header Name (`http.proxy_header`)", such as `X-Real-IP` (for security, this field is empty by default). After modification, please manually restart the Artalk service to take effect.
Otherwise, Artalk will not be able to obtain the user's real IP address (if using Docker, the IP obtained may always be 172.17.0.X, which is the IP of the Docker virtual network card).
## Privacy Policy
Artalk comments will record users' `IP` and `User-Agent` data. Since such data pertains to user privacy, please declare this in your website's privacy policy and inform users that privacy data will be collected when they comment.
+41
View File
@@ -0,0 +1,41 @@
# LaTeX
For academic websites, LaTeX support is essential. You can use [Katex](https://katex.org/), a widely-used LaTeX syntax parser in the frontend, to implement this functionality. To maintain simplicity, Artalk does not natively include LaTeX syntax parsing capabilities. However, you can manually incorporate Katex and the Artalk Katex plugin into your page to enable LaTeX syntax support in the comment system.
::: code-group
```html [Browser Inclusion]
<!-- 1. Include Katex -->
<link rel="stylesheet" href="https://unpkg.com/katex@0.16.7/dist/katex.min.css" />
<script src="https://unpkg.com/katex@0.16.7/dist/katex.min.js"></script>
<!-- 2. Include Artalk -->
<link href="/lib/artalk/Artalk.css" rel="stylesheet" />
<script src="/lib/artalk/Artalk.js"></script>
<!-- 3. Include Artalk Katex Plugin -->
<script src="https://unpkg.com/@artalk/plugin-katex/dist/artalk-plugin-katex.js"></script>
```
```ts [Node Inclusion]
// pnpm add katex @artalk/plugin-katex
import Artalk from 'artalk'
import { ArtalkKatexPlugin } from '@artalk/plugin-katex'
import 'katex/dist/katex.min.css'
Artalk.use(ArtalkKatexPlugin)
```
:::
You can post a comment:
```md
$$
P(A|B_1, B_2, \ldots, B_n) = \frac{P(B_1, B_2, \ldots, B_n|A) \cdot P(A)}{P(B_1, B_2, \ldots, B_n)}
$$
```
Check the result:
![](/images/latex-support/1.png)
+121
View File
@@ -0,0 +1,121 @@
# Image Lightbox
The Artalk Image Lightbox plugin seamlessly integrates your website's **existing image lightbox** functionality into Artalk.
## Browser Environment
In a browser environment, blog themes typically come with an image lightbox. The plugin will automatically detect the lightbox library in the `window` global object and integrate it into Artalk without additional configuration.
```html
<!-- 1. Include the image lightbox dependency, such as LightGallery (usually provided by the blog theme, no need to re-include) -->
<script src="lightgallery.js"></script>
<!-- 2. Include Artalk -->
<link href="/lib/artalk/Artalk.css" rel="stylesheet" />
<script src="/lib/artalk/Artalk.js"></script>
<!-- 3. Include the Artalk LightBox plugin -->
<script src="https://unpkg.com/@artalk/plugin-lightbox/dist/artalk-plugin-lightbox.js"></script>
```
If necessary, you can configure the lightbox library with the global variable `ATK_LIGHTBOX_CONF`:
```html
<script>
// Config for LightGallery
window.ATK_LIGHTBOX_CONF = {
plugins: [lgZoom, lgThumbnail],
speed: 500,
licenseKey: 'your_license_key'
}
</script>
```
## Node Environment
Install the image lightbox plugin:
```bash
pnpm add @artalk/plugin-lightbox
```
Configure the plugin and dynamically import the lightbox library using `import`:
::: code-group
```ts [LightGallery]
import Artalk from 'artalk'
import { ArtalkLightboxPlugin } from '@artalk/plugin-lightbox'
import 'lightgallery/css/lightgallery.css'
Artalk.use(ArtalkLightboxPlugin, {
lightGallery: {
lib: () => import('lightgallery'),
},
})
```
```ts [PhotoSwipe]
import Artalk from 'artalk'
import { ArtalkLightboxPlugin } from '@artalk/plugin-lightbox'
import 'photoswipe/style.css'
Artalk.use(ArtalkLightboxPlugin, {
photoSwipe: {
lib: () => import('photoswipe/lightbox'),
pswpModule: () => import('photoswipe'),
},
})
```
```ts [LightBox]
import Artalk from 'artalk'
import { ArtalkLightboxPlugin } from '@artalk/plugin-lightbox'
import 'lightbox2/dist/css/lightbox.min.css'
import jQuery from 'jquery'
window.$ = jQuery
Artalk.use(ArtalkLightboxPlugin, {
lightBox: {
// @ts-ignore
lib: () => import('lightbox2'),
},
})
```
```ts [FancyBox]
import Artalk from 'artalk'
import { ArtalkLightboxPlugin } from '@artalk/plugin-lightbox'
import 'fancybox/dist/css/jquery.fancybox.css'
import jQuery from 'jquery'
window.$ = jQuery
Artalk.use(ArtalkLightboxPlugin, {
fancyBox: {
// @ts-ignore
lib: () => import('fancybox'),
},
})
```
:::
In a Node environment, if additional configuration for the lightbox library is required, it can be done through the `config` option:
```ts
Artalk.use(ArtalkLightboxPlugin, {
// ...
// Config for LightGallery
config: {
speed: 500,
},
})
```
---
Currently, the following libraries are supported for automatic integration: [LightGallery](https://github.com/sachinchoolur/lightGallery) • [FancyBox](https://github.com/fancyapps/fancybox) • [lightbox2](https://github.com/lokesh/lightbox2) • [PhotoSwipe](https://photoswipe.com/)
Some lightbox libraries are not yet supported. Contributions are welcome 😉: [@artalk/plugin-lightbox](https://github.com/ArtalkJS/Artalk/blob/master/ui/plugin-lightbox/src/main.ts).
+81
View File
@@ -0,0 +1,81 @@
# Page View Statistics
Artalk integrates built-in page view and comment count statistics, allowing you to display the page's view count and comment count within the page.
```html
Views: <span class="artalk-pv-count"></span>
Comments: <span class="artalk-comment-count"></span>
```
## Loading Placeholder
Artalk requires some time to load. You can add a placeholder within the elements displaying the statistics:
```html
<span class="artalk-pv-count">Loading...</span>
```
## Loading Statistics for Multiple Pages Simultaneously
For instance, on an article list page, you can display the view count and comment count for each article.
When on the article list page, simply call the `Artalk.loadCountWidget` function without `Artalk.init` (loading the comment list will increment the page view count by 1).
<!-- prettier-ignore-start -->
```js
Artalk.loadCountWidget({
server: 'server address',
site: 'site name',
pvEl: '.artalk-pv-count',
countEl: '.artalk-comment-count',
statPageKeyAttr: 'data-page-key',
})
```
<!-- prettier-ignore-end -->
Then place multiple elements with the class `artalk-pv-count`, using the attribute `data-page-key` to specify the page to query:
```html
<span class="artalk-pv-count" data-page-key="/test/1.html"></span>
<span class="artalk-pv-count" data-page-key="/test/2.html"></span>
<span class="artalk-pv-count" data-page-key="/test/3.html"></span>
```
The same applies for comment count queries:
```html
<span class="artalk-comment-count" data-page-key="/test/1.html"></span>
<span class="artalk-comment-count" data-page-key="/test/2.html"></span>
<span class="artalk-comment-count" data-page-key="/test/3.html"></span>
```
## Custom Element Selectors
You can specify element selectors for displaying page views and comment counts through the `pvEl` and `countEl` configuration options:
```js
Artalk.init({
pvEl: '.your_pv_count_element', // Selector for page view elements
countEl: '.your_comment_count_element', // Selector for comment count elements
})
```
## Custom `data-page-key` Attribute Name
The default value for the `statPageKeyAttr` configuration option is `data-page-key`. Artalk uses this attribute name to query the specified page. To facilitate adaptation with blog themes, you can customize the attribute name, for example, replacing it with `data-path`:
```js
Artalk.loadCountWidget({
statPageKeyAttr: 'data-path',
})
```
In this case, the corresponding HTML code should be as follows:
```html
<span class="artalk-pv-count" data-path="/test/1.html"></span>
```
Thus, the value of the `data-path` attribute will be used to query the specified page.
+45
View File
@@ -0,0 +1,45 @@
# Sidebar
The sidebar serves a dual purpose as both a **Notification Center** and a **Dashboard**. Once users fill in the "Nickname" and "Email" fields in the comment box, they can find the sidebar entry button at the bottom right corner of the comment box.
<img src="/images/sidebar/1.png" width="650">
## Notification Center
Artalk features an on-site messaging system. In addition to receiving email notifications, users can also view messages in the sidebar.
The sidebar allows users to view comments related to them, categorized into: Mentions, All, Mine, and Pending Review.
You can quickly locate comments and jump to the corresponding page.
<img src="/images/sidebar/2.png" width="430">
When a user receives a message, a red dot indicator will appear.
<img src="/images/sidebar/3.png" width="350">
Additionally, you can swiftly reply to messages in the sidebar without needing to switch to the comment page.
<img src="/images/sidebar/4.png" width="400">
## Dashboard
For administrator accounts, the sidebar will automatically upgrade from the "Notification Center" to the "Dashboard."
After an administrator enters their "Nickname" and "Email," a password verification prompt will appear:
<img src="/images/sidebar/5.png" width="600">
Once in the sidebar, you can manage comments, pages, sites, and other content.
<img src="/images/sidebar/6.png" width="800">
By clicking the site icon in the top left corner, you can quickly switch between multiple sites.
<img src="/images/sidebar/7.png" width="400">
## Settings
Log into the administrator account to access the settings interface in the "Dashboard," where you can modify [Configuration](../backend/config.md) and [Appearance](./config.md) without editing complex configuration files.
<img src="/images/sidebar/settings.png" width="700">
+123
View File
@@ -0,0 +1,123 @@
# Voting Feature
Artalk supports voting on comments and pages, allowing users to click the "Up" or "Down" buttons to cast their votes. The comment list can be sorted based on the number of votes, which helps users better assess the quality of the comments.
## Comment Voting
The comment voting feature is enabled by default, allowing users to vote on comments.
You can find the "UI Settings" in the Dashboard to modify the "Vote Button" option to enable or disable comment voting.
Environment variable for the vote button:
```
ATK_FRONTEND_VOTE=1
```
Configuration file for the vote button:
```yaml
frontend:
vote: true
```
### Down Button
By default, Artalk does not display the Down button. You can find the "UI Settings" in the Dashboard to modify the "Vote Down Button" option to enable it.
Environment variable for the Down button:
```
ATK_FRONTEND_VOTE_DOWN=1
```
Configuration file for the Down button:
```yaml
frontend:
voteDown: true
```
## Page Voting
Artalk supports voting on pages. To enable page voting, you need to add elements in the page to display the voting buttons, which Artalk will automatically initialize on load:
```html
<div>
<span class="artalk-page-vote-up"></span>
<span class="artalk-page-vote-down"></span>
</div>
```
### Voted Status Styling
When users click the page voting button, the element will be given an `active` class to indicate that the user has voted. For example:
```html
<span class="artalk-page-vote-up active"></span>
```
You can customize the voted button style using CSS:
```css
.artalk-page-vote-up.active {
color: #0083ff;
}
```
The default added class name is `active`, but it can be changed using `pageVote.activeClass` in the client configuration:
```js
Artalk.init({
pageVote: {
activeClass: 'active',
},
})
```
### Custom Element Selectors
By default, Artalk searches for `.artalk-page-vote-up` and `.artalk-page-vote-down` as the voting button elements.
You can customize the voting button selectors by modifying the `pageVote.upBtnEl` and `pageVote.downBtnEl` configuration in the client:
```js
Artalk.init({
pageVote: {
upBtnEl: '.artalk-page-vote-up',
downBtnEl: '.artalk-page-vote-down',
},
})
```
### Further Customizing Page Voting Buttons
If the voting buttons do not contain any child elements, Artalk will output the text "Up (n)" into the element.
If you want to output the vote count into a separate element, you can add a tag inside the button, for example:
```html
<div class="artalk-page-vote">
<span class="artalk-page-vote-up">
👍 (<span class="artalk-page-vote-up-count"></span>)
</span>
<span class="artalk-page-vote-down">
👎 (<span class="artalk-page-vote-down-count"></span>)
</span>
</div>
```
To further customize, you can replace the text with icons or add other styles.
The default selectors for vote counts are `.artalk-page-vote-up-count` and `.artalk-page-vote-down-count`.
You can modify `pageVote.upCountEl` and `pageVote.downCountEl` to customize the vote count output elements:
```js
Artalk.init({
pageVote: {
upCountEl: '.artalk-page-vote-up-count',
downCountEl: '.artalk-page-vote-down-count',
},
})
```
+109
View File
@@ -0,0 +1,109 @@
# <span class="wave">👋</span> Hello Friend
Artalk is a simple yet feature-rich commenting system that you can effortlessly deploy and integrate into any blog, website, or web application.
![](https://user-images.githubusercontent.com/22412567/141147152-df30a0ff-bf41-42ee-9958-4722206a7a90.png)
## Key Features
**Lightweight Design**
The front end uses TypeScript (Vanilla JS), lightweight and free of redundant dependencies, only ~40KB (gzipped).
The back end, rewritten in Golang (Artalk v2), is cross-platform, compact, and fully featured, allowing for rapid deployment.
**“Small but Complete”**
Artalk's features include but are not limited to:
<!-- features -->
* [Sidebar](https://artalk.js.org/guide/frontend/sidebar.html): Quick management, intuitive browsing
* [Social Login](https://artalk.js.org/guide/frontend/auth.html): Fast login via social accounts
* [Email Notification](https://artalk.js.org/guide/backend/email.html): Various sending methods, email templates
* [Diverse Push](https://artalk.js.org/guide/backend/admin_notify.html): Multiple push methods, notification templates
* [Site Notification](https://artalk.js.org/guide/frontend/sidebar.html): Red dot marks, mention list
* [Captcha](https://artalk.js.org/guide/backend/captcha.html): Various verification types, frequency limits
* [Comment Moderation](https://artalk.js.org/guide/backend/moderator.html): Content detection, spam interception
* [Image Upload](https://artalk.js.org/guide/backend/img-upload.html): Custom upload, supports image hosting
* [Markdown](https://artalk.js.org/guide/intro.html): Supports Markdown syntax
* [Emoji Pack](https://artalk.js.org/guide/frontend/emoticons.html): Compatible with OwO, quick integration
* [Multi-Site](https://artalk.js.org/guide/backend/multi-site.html): Site isolation, centralized management
* [Admin](https://artalk.js.org/guide/backend/multi-site.html): Password verification, badge identification
* [Page Management](https://artalk.js.org/guide/frontend/sidebar.html): Quick view, one-click title navigation
* [Page View Statistics](https://artalk.js.org/guide/frontend/pv.html): Easily track page views
* [Hierarchical Structure](https://artalk.js.org/guide/frontend/config.html#nestmax): Nested paginated list, infinite scroll
* [Comment Voting](https://artalk.js.org/guide/frontend/config.html#vote): Upvote or downvote comments
* [Comment Sorting](https://artalk.js.org/guide/frontend/config.html#listsort): Various sorting options, freely selectable
* [Comment Search](https://artalk.js.org/guide/frontend/sidebar.html): Quick comment content search
* [Comment Pinning](https://artalk.js.org/guide/frontend/sidebar.html): Pin important messages
* [View Author Only](https://artalk.js.org/guide/frontend/config.html): Show only the author's comments
* [Comment Jump](https://artalk.js.org/guide/intro.html): Quickly jump to quoted comment
* [Auto Save](https://artalk.js.org/guide/frontend/config.html): Content loss prevention
* [IP Region](https://artalk.js.org/guide/frontend/ip-region.html): Display user's IP region
* [Data Migration](https://artalk.js.org/guide/transfer.html): Free migration, quick backup
* [Image Lightbox](https://artalk.js.org/guide/frontend/lightbox.html): Quick integration of image lightbox
* [Image Lazy Load](https://artalk.js.org/guide/frontend/img-lazy-load.html): Lazy load images, optimize experience
* [Latex](https://artalk.js.org/guide/frontend/latex.html): Integrate Latex formula parsing
* [Night Mode](https://artalk.js.org/guide/frontend/config.html#darkmode): Switch to night mode
* [Extension Plugin](https://artalk.js.org/develop/plugin.html): Create more possibilities
* [Multi-Language](https://artalk.js.org/guide/frontend/i18n.html): Switch between multiple languages
* [Command Line](https://artalk.js.org/guide/backend/config.html): Command line operation management
* [API Documentation](https://artalk.js.org/http-api.html): Provides OpenAPI format documentation
* [Program Upgrade](https://artalk.js.org/guide/backend/update.html): Version check, one-click upgrade
<!-- /features -->
We are not exhaustive; more exciting features await your discovery!
**“Unlimited Blade Works”**
Artalk is continually growing; your creativity drives its evolution, and your contributions add value!
Whether it's a front-end project using Vue, React, Svelte, or a blog system like WordPress, Typecho, Hexo, Artalk can be quickly integrated. With everyone's ingenuity, we believe Artalk can adapt to various business scenarios.
## User Experience
We believe elegant design brings excellent user experience, which helps projects go further.
"Ordinary but not mediocre design" - The design tool Figma, favored by professional UI designers, played a significant role in Artalk's redesign. We pre-designed user-friendly, modern interfaces with Figma, then wrote front-end styles to seamlessly blend them into modern websites. This resulted in a simple and fresh interface. Additionally, we designed user identity badges, comment tile/infinite nesting modes, comment pagination, and ensured compatibility with various screen sizes, offering unlimited content in limited space.
"Collapse in an instant" - For unoptimized commenting systems, users might need to repeatedly enter personal information, and their painstakingly typed insights could be lost due to unexpected situations. Knowing that an adult's collapse can happen in an instant, Artalk uses browser caching to auto-fill user information and auto-save comment data, allowing users to express their thoughts with minimal effort.
"Rich site expressions to rekindle comment enthusiasm" - Monotonous emoticons might dampen visitor enthusiasm for commenting. Hence, Artalk comes with a carefully selected humorous emoticon set. Additionally, Artalk supports custom image emoticons.
"Is what you love your life?" - User experience isn't just about visitors; it's also about site admins. Artalk features user-friendly design for site admins, integrating management tools into the [dashboard](./frontend/sidebar.md#控制中心) in the sidebar. Admin users can easily manage multiple sites, with all data exchanged through standardized APIs and processed asynchronously, reducing data processing blockages and service resource usage. For potential spam, Artalk supports automatic filtering, reducing admin workload and keeping the site clean.
We hope Artalk not only fulfills the basic functions of a commenting system but also becomes a bridge for **knowledge sharers and learners to exchange ideas**, helping knowledge creators realize their value.
## Community Philosophy
“**Simplify Complexity, Remarkable Simplicity**”
Artalk aims to achieve **rich** functionality while being as **simple** as possible.
On October 2, 2018, Artalk's [first line of code](https://github.com/ArtalkJS/Artalk/commit/66128e2c8d9a8ac00a8d1498ff0ec035a7727daf) was pushed to GitHub. It wasn't until October 20, 2021, that version v2 was released. Due to a small team and limited developer time, the project's overall progress has been slow. We greatly need the power of the community, whether it's reporting bugs or providing new feature ideas, we eagerly anticipate your contributions.
The Artalk community is an inclusive and open community. We welcome people of all skill levels to help/participate in project development. If you are a beginner, besides actively learning project-related knowledge, you can also try deploying and using Artalk, finding and confirming its shortcomings during use, and then posting relevant discussions in the project's [Issues](https://github.com/ArtalkJS/Artalk/issues) or [Discussions](https://github.com/ArtalkJS/Artalk/discussions) to help developers better locate issues and make optimizations faster. If you are a skilled developer, you can find all the project source code at [@ArtalkJS](https://github.com/ArtalkJS). Combined with this documentation, we believe it shouldn't be difficult to understand. Whether it's optimizing the front-end and back-end structure, implementing new features, or writing community projects, we look forward to Artalk being invigorated with fresh blood.
“More action, less talk” - The Artalk community does not welcome meaningless disputes. We hope community members coexist harmoniously and contribute ideas for community development. Before raising a question, you should read "[How to Ask Questions the Smart Way](https://lug.ustc.edu.cn/wiki/doc/smart-questions/)", as this may determine whether you get a useful answer. Before expressing an opinion, you should maintain basic etiquette, such as keeping a calm attitude, using appropriate language, and avoiding abusive language, sarcasm, or disrespecting others' beliefs and positions.
As advocates and practitioners of open-source spirit, we believe the free software we create should be freely used, studied, modified, and shared. This project's main program is open-sourced under the [MIT](https://github.com/ArtalkJS/Artalk/blob/master/LICENSE) license, and the documentation is under the [CC](https://creativecommons.org/licenses/by-nc-sa/4.0/deed.zh) license.
::: tip Want to Contribute to the Community?
- Browse developer resources ([Developer Documentation](../develop/index.md) / [CONTRIBUTING.md](https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md))
- Maintain Artalk backend (code repository [@ArtalkJS/Artalk:/](https://github.com/ArtalkJS/Artalk))
- Maintain Artalk frontend (code repository [@ArtalkJS/Artalk:/ui](https://github.com/ArtalkJS/Artalk/tree/master/ui))
- Improve Artalk documentation (code repository [@ArtalkJS/Artalk:/docs](https://github.com/ArtalkJS/Artalk/tree/master/docs))
- Translate multi-language i18n (see [Multi-language Guide](./frontend/i18n.html))
- Enhance data migration tools (code repository [@ArtalkJS/Artransfer](https://github.com/ArtalkJS/Artransfer))
- Share your ideas (leave a comment below / [Discussions](https://github.com/ArtalkJS/Artalk/discussions))
- Write related community projects (plugins, deployment tutorials, etc.)
:::
## In Conclusion
By now, you should have a basic understanding of Artalk. Whether you choose to use Artalk or not, we greatly appreciate your attention. If Artalk does not yet meet your needs, we hope you can offer sharp suggestions to help it grow.
Welcome to Artalk,
Take off! 🛫️
+3
View File
@@ -0,0 +1,3 @@
# Security
【TODO】
+214
View File
@@ -0,0 +1,214 @@
# 🛬 Data Migration
## Data Bundle
The data bundle (Artrans = Art + Ran) is the Artalk persistent data storage standard format.
::: details Artran Format Definition
We define it as follows: each comment data (Object) is called an Artran, and multiple comment data together form Artrans (Array type).
```json
{
"id": "123",
"rid": "233",
"content": "Hello Artalk",
"ua": "Artalk/6.6",
"ip": "233.233.233.233",
"created_at": "2021-10-28 20:50:15 +0800",
"updated_at": "2021-10-28 20:50:15 +0800",
"is_collapsed": "false",
"is_pending": "false",
"vote_up": "666",
"vote_down": "0",
"nick": "qwqcode",
"email": "qwqcode@github.com",
"link": "https://qwqaq.com",
"password": "",
"badge_name": "Administrator",
"badge_color": "#FF716D",
"page_key": "https://artalk.js.org/guide/transfer.html",
"page_title": "Data Migration",
"page_admin_only": "false",
"site_name": "Artalk",
"site_urls": "http://localhost:3000/demo/,https://artalk.js.org"
}
```
We call a JSON array Artrans, and each Object item within the array is an Artran (without the s).
:::
## Conversion Tool
Use the following tool to convert comment data from other formats to Artrans, and then import them into Artalk. [Open in a new window](https://artransfer.netlify.app)
<Artransfer />
::: tip
The following text provides various methods to obtain source data for reference; if you encounter any issues, please submit feedback via [issue](https://github.com/ArtalkJS/Artransfer/issues).
:::
## Data Import
Data files converted to the `.artrans` format can be imported into Artalk:
- **Dashboard Import**: You can find the "Migration" tab in the "[Dashboard](./frontend/sidebar.md#control-center)" and follow the prompts to import Artrans.
- **Command Line Import**: Refer to [Command Line Import](#command-line-import).
## Obtaining Source Data
### Typecho
**Install Plugin to Obtain Artrans**
We provide an Artrans export plugin:
1. Click "[here](https://github.com/ArtalkJS/Artrans-Typecho/releases/download/v1.0.0/ArtransExporter.zip)" to download the plugin and "unzip" it into the Typecho directory `/usr/plugins/`.
2. Go to the Typecho backend "Console - Plugins" to enable the "ArtransExporter" plugin.
3. Go to "Console - Export Comments (Artrans)" to export all Typecho comments in Artrans format.
**Direct Database Connection to Obtain Artrans**
If your blog is no longer active but the database still exists, you can use our command line tool that supports direct connection to the Typecho database.
[Download Artransfer-CLI](https://github.com/ArtalkJS/Artransfer-CLI/releases), unzip the package, and execute:
```sh
./artransfer typecho \
--db="mysql" \
--host="localhost" \
--port="3306" \
--user="root" \
--password="123456" \
--name="typecho_database_name"
```
After execution, you will get a file in Artrans format:
```sh
> ls
typecho-20220424-202246.artrans
```
Note: It supports connecting to various databases. For more details, refer to [here](https://github.com/ArtalkJS/Artransfer-CLI).
### WordPress
Go to the WordPress backend "Tools - Export", check "All Content", and export the file. You can then use the [conversion tool](#conversion-tool) for conversion.
![](/images/transfer/wordpress.png)
### Valine
Go to the [LeanCloud backend](https://console.leancloud.cn/) to export the comment data file in JSON format, then use the [conversion tool](#conversion-tool) for conversion.
![](/images/transfer/leancloud.png)
### Waline
Using the LeanCloud database, Waline can refer to the above method for Valine as their formats are similar.
For independently deployed Waline, download [Artransfer-CLI](https://github.com/ArtalkJS/Artransfer-CLI/releases) to connect to the local database for export. Execute the command line:
```bash
./artransfer waline \
--db="mysql" \
--host="localhost" \
--port="3306" \
--user="root" \
--password="123456" \
--name="waline_database_name" \
--table-prefix="wl_"
```
You will obtain a data file in Artrans format, then [import into Artalk](#how-to-import-artrans).
Note: It supports connecting to various databases. For more details, refer to [here](https://github.com/ArtalkJS/Artransfer-CLI).
### Disqus
Go to the [Disqus backend](https://disqus.com/admin), find "Moderation - Export" and click to export. Disqus will send a `.gz` compressed package to your email. After extracting, you will get a `.xml` data file, which you can then use the [conversion tool](#conversion-tool) to convert to Artrans.
![](/images/transfer/disqus.png)
### Commento
You can export the data file in JSON format from the Commento backend, then use the [conversion tool](#conversion-tool) for conversion.
[Image, to be supplemented...]
### Twikoo
[Twikoo](https://twikoo.js.org/) is a comment system developed based on Tencent Cloud. Go to the [Tencent Cloud backend](https://console.cloud.tencent.com/tcb) to export the comment data file in JSON format, then use the [conversion tool](#conversion-tool) for conversion.
<img src="/images/transfer/tencent-tcb.png" style="max-width: 480px;">
### Artalk v1 (Old PHP Backend)
[Artalk v1](https://github.com/ArtalkJS/ArtalkPHP) is the old backend of Artalk, written in PHP. The new backend has fully transitioned to Golang with a redesigned data table structure. Upgrading to the new version requires using the [conversion tool](#conversion-tool) for conversion.
Old version data path: `/data/comments.data.json`
## Command Line Import
Execute `artalk import -h` to view the help documentation.
```bash
./artalk import [parameters...] [filename]
```
Set import parameters via the `-p` flag on the command line:
```bash
./artalk import -p '{ "target_site_name": "Site", "target_site_url": "https://xx.com", "json_file": "", "url_resolver": true }' ./artrans.json
```
If importing via the web backend, you can fill the JSON in the text box:
```json
{
"target_site_name": "Site",
"target_site_url": "https://xx.com",
"json_file": "path on the server",
"url_resolver": true
}
```
Artalk import parameters:
| Parameter | Type | Description |
| :---------------------: | ------- | ---------------------------------------------------------------------------------------------------- |
| `target_site_name` | String | Name of the import site |
| `target_site_url` | String | URL of the import site |
| `url_resolver` | Boolean | URL resolver, default is off. Re-generates the `page_key` based on the `target_site_url` as the new `page_key` for comments |
| `url_keep_domain` | Boolean | Default is off. Whether to keep the original domain part of the URL. If off, removes the domain part of `pageKey`. When `url_resolver` is on, `url_keep_domain` is also enabled |
| `json_file` | String | Path to the JSON data file |
| `json_data` | String | Content of the JSON data string |
| `assumeyes` | Boolean | Execute directly without confirmation `y/n` |
## Data Backup
You can find the "Migration" tab in the "[Dashboard](./frontend/sidebar.md#dashboard)" on the front end, and export comment data in Artrans format.
### Command Line Backup
Export: `artalk export ./artrans`
Import: `artalk import ./artrans`
### Advanced Usage
Execute `artalk export` to directly "standard output", and perform "pipe" or "output redirection" operations, for example:
```bash
artalk export | gzip -9 | ssh username@remote_ip "cat > ~/backup/artrans.gz"
```
## Conclusion
We currently support converting data from Typecho, WordPress, Valine, Waline, Disqus, Commento, Twikoo, etc., to Artrans. However, considering the diversity of comment systems, although we have adapted the above types of data, many are still not compatible. If you happen to be using an unsupported comment system, besides waiting for official Artalk support, you can also try to understand the Artrans data format and write your own tools for importing and exporting comment data. If you think your tool is well-written, we would be happy to include it, allowing us to create a tool that can freely switch between different comment systems together.
Visit: [Artransfer Migration Tool Code Repository](https://github.com/ArtalkJS/Artransfer)
+3 -32
View File
@@ -1,32 +1,3 @@
---
layout: home
title: Artalk
titleTemplate: A Self-hosted Comment System
hero:
name: Artalk
text: A Self-hosted Comment System
tagline: Elevate your online conversations with a comment system that embodies the trifecta of lightness, security, and refinement.
actions:
- theme: brand
text: Get Started
link: /guide/intro
- theme: alt
text: View on GitHub
link: https://github.com/ArtalkJS/Artalk
features:
- icon: 🍃
title: Lightweight
details: Lightweight and responsive to every interaction
- icon: 🔒
title: Safety
details: Everything is under control as the data is completely self-hosted
- icon: 🐳
title: Turbo
details: Easy to deploy, quick to set up commenting interface
- icon: 🍱
title: Flexible
details: Use Golang to interpret the excellence of multiple platforms
---
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/?lng=en';
</script>
-7
View File
@@ -1,7 +0,0 @@
# 后端构建
本页面内容已移动至 <https://artalk.js.org/develop/contributing.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/develop/contributing.html';
</script>
-7
View File
@@ -1,7 +0,0 @@
# 数据
本页面内容已移动至 <https://artalk.js.org/guide/transfer.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/guide/transfer.html';
</script>
-7
View File
@@ -1,7 +0,0 @@
# 如何配置界面
本页面内容已移动至 <https://artalk.js.org/guide/frontend/config.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/guide/frontend/config.html';
</script>
-7
View File
@@ -1,7 +0,0 @@
# 后端部署
本页面内容已移动至 <https://artalk.js.org/guide/deploy.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/guide/deploy.html';
</script>
-227
View File
@@ -1,227 +0,0 @@
# 📦 程序部署
## Docker 部署
推荐使用 Docker 部署,需预先安装 [Docker 引擎](https://docs.docker.com/engine/install/),执行命令创建容器:
```bash
docker run -d \
--name artalk \
-p 8080:23366 \
-v $(pwd)/data:/data \
-e "TZ=Asia/Shanghai" \
-e "ATK_LOCALE=zh-CN" \
-e "ATK_SITE_DEFAULT=Artalk 的博客" \
-e "ATK_SITE_URL=https://example.com" \
artalk/artalk-go
```
执行命令创建管理员账户:
```bash
docker exec -it artalk artalk admin
```
浏览器输入 `http://artalk.example.com:8080` 进入 Artalk 后台登录界面。
在网页中引入 Artalk 程序内嵌的的前端 JS 和 CSS 资源并初始化 Artalk:
<!-- prettier-ignore-start -->
```html
<!-- CSS -->
<link href="http://artalk.example.com:8080/dist/Artalk.css" rel="stylesheet" />
<!-- JS -->
<script src="http://artalk.example.com:8080/dist/Artalk.js"></script>
<!-- Artalk -->
<div id="Comments"></div>
<script>
Artalk.init({
el: '#Comments', // 绑定元素的 Selector
pageKey: '/post/1', // 固定链接
pageTitle: '关于引入 Artalk 的这档子事', // 页面标题 (留空自动获取)
server: 'http://artalk.example.com:8080', // 后端地址
site: 'Artalk 的博客', // 你的站点名
})
</script>
```
<!-- prettier-ignore-end -->
评论框输入管理员用户名和邮箱,「控制台」按钮将出现在评论框右下角。
在控制台,你可以根据喜好[配置评论系统](./backend/config.md)、[将评论迁移到 Artalk](./transfer.md)。
🥳 你已成功完成 Artalk 部署!
## 普通方式部署
1. [GitHub Release](https://github.com/ArtalkJS/Artalk/releases) 下载程序压缩包
2. 解压 `tar -zxvf artalk_版本号_系统_架构.tar.gz`
3. 运行 `./artalk server`
4. 配置
```js
Artalk.init({ server: 'http://artalk.example.com:23366' })
```
进阶操作:
- [守护进程 (Systemd, Supervisor)](./backend/daemon.md)
- [反向代理 (Caddy, Nginx, Apache)](./backend/reverse-proxy.md)
- [自编译 (通过最新代码构建)](../develop/contributing.md)
## Compose 部署
**compose.yaml**
```yaml
version: '3.8'
services:
artalk:
container_name: artalk
image: artalk/artalk-go
restart: unless-stopped
ports:
- 8080:23366
volumes:
- ./data:/data
environment:
- TZ=Asia/Shanghai
- ATK_LOCALE=zh-CN
- ATK_SITE_DEFAULT=Artalk 的博客
- ATK_SITE_URL=https://your_domain
```
创建容器:
```bash
docker-compose up -d
```
::: details Compose 常用命令
```bash
docker-compose restart # 重启容器
docker-compose stop # 暂停容器
docker-compose down # 删除容器
docker-compose pull # 更新镜像
docker-compose exec artalk bash # 进入容器
```
:::
参考文档:[Docker](./backend/docker.md) / [环境变量](./env.md)
::: warning
自 2024-06-06 开始,境内的 Docker Hub 镜像相继停止服务,可选择配置代理或自建镜像。
详见:[Docker 镜像加速](https://gist.github.com/y0ngb1n/7e8f16af3242c7815e7ca2f0833d3ea6)。
:::
## Linux 发行版
**Arch Linux (AUR)**:
```bash
paru -S artalk
```
**NixOS**:
```bash
nix-env -iA nixpkgs.artalk
```
**Termux**:
```bash
pkg install artalk
```
[![Packaging status](https://repology.org/badge/vertical-allrepos/artalk.svg)](https://repology.org/project/artalk/versions)
## CDN 资源
::: tip Artalk 最新版本
当前 Artalk 前端最新版本号为: **:ArtalkVersion:**
若需升级前端将 URL 中的版本号数字部分替换即可。
:::
Artalk 后端程序内嵌了前端 JS、CSS 文件,使用公共 CDN 资源请注意版本兼容性。
**CDNJS**
> <https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.js>
>
> <https://cdnjs.cloudflare.com/ajax/libs/artalk/:ArtalkVersion:/Artalk.css>
::: details 查看更多
**SUSTech Mirrors (境内)**
> <https://mirrors.sustech.edu.cn/cdnjs/ajax/libs/artalk/:ArtalkVersion:/Artalk.js>
>
> <https://mirrors.sustech.edu.cn/cdnjs/ajax/libs/artalk/:ArtalkVersion:/Artalk.css>
**Staticfile CDN (境内)**
> <https://cdn.staticfile.org/artalk/:ArtalkVersion:/Artalk.js>
>
> <https://cdn.staticfile.org/artalk/:ArtalkVersion:/Artalk.css>
**UNPKG**
> <https://unpkg.com/artalk@:ArtalkVersion:/dist/Artalk.js>
>
> <https://unpkg.com/artalk@:ArtalkVersion:/dist/Artalk.css>
**JS DELIVR**
> <https://cdn.jsdelivr.net/npm/artalk@:ArtalkVersion:/dist/Artalk.js>
>
> <https://cdn.jsdelivr.net/npm/artalk@:ArtalkVersion:/dist/Artalk.css>
:::
## Node 项目
安装 Artalk:
```bash
npm install artalk
```
引入 Artalk:
```js
import 'artalk/dist/Artalk.css'
import Artalk from 'artalk'
Artalk.init({
// ...
})
```
更多参考:
- [置入博客文档](../develop/import-blog.md)
- [置入框架文档](../develop/import-framework.md)
- [前端配置](./frontend/config.md)
- [前端 API](../develop/fe-api.md)
## 数据导入
从其他评论系统导入数据:[数据迁移](./transfer.md)
## ArtalkLite
可选择精简版 [ArtalkLite](./frontend/artalk-lite.md):体积更小、更简约。
## 开发环境
可参考:[开发者指南](https://github.com/ArtalkJS/Artalk/blob/master/CONTRIBUTING.md)
-48
View File
@@ -1,48 +0,0 @@
# 📚 扩展阅读
“我们仰望同一片天空,却看着不同的地方。”
Artalk 离不开社区的支持与帮助,**是你们让 Artalk 走得更远!**
非常感谢对 Artalk 提供支持与帮助的朋友们!😘
## Artalk v2
- [Artalk 评论系统推荐 (By @inkss)](https://inkss.cn/blog/8f37d8c3/)
- [Nuxt.js如何部署Artalk和遇到的问题 (By @子舒)](https://imhan.cn/posts/20220218/)
- [宝塔安装过程大概记录 (By @xiamuguizhi)](https://github.com/ArtalkJS/Artalk/discussions/46)
- [Vuepress配置评论插件为Artalk](https://wiki.eryajf.net/pages/b74c2b/)
- [Fly.io 部署 Artalk 评论系统](https://wayjam.me/posts/artalk-deploy-on-flyio/)
- [Railway.app 部署 Artalk 评论系统](https://blog.moraxyc.com/post/eidb8276/)
- [Render.com 部署Artalk自托管评论系统](https://www.leenhawk.com/posts/3932123804/)
- [在 Valaxy 中使用 Artalk 作为评论系统](https://www.lihaoyu.cn/posts/use-artalk-in-valaxy)
更多新版读物正在撰写当中...
## Artalk v1
::: warning
Artalk v1 版本基于 [PHP 后端](https://github.com/ArtalkJS/ArtalkPHP),部分内容可能不适用于 Go 后端,但仍具有参考价值。
:::
- [[!!!] 一个 Artalk 的非官方文档 (By @thun888)](https://blog.hzchu.top/wiki/Artalk-doc/)
- [为 Gridsome 添加 Artalk 自托管评论系统 - Monstx's Blog](https://blog.monsterx.cn/code/use-self-hosted-comment-system-in-gridsome/)
- [Artalk 自托管评论系统的后端部署 - Jalen's Blog](https://blog.jalenchuh.cn/posts/artalk-api-php/)
- [无服务器搭建 Artalk 评论系统后端 - 陈YFの博客](https://blog.cyfan.top/p/480ab6ed.html)
- [Hexo Next 主题添加 Artalk 评论系统 - 心底的河流](https://lhy.life/20201126-artalk-next/)
- [Hexo 添加 Artalk 评论教程 - 我相信我可以](https://butterfly.imlete.cn/article/Hexo-Artalk.html)
- [基于 Butterfly 主题添加 Artalk 评论系统 - 卓越科技的 Blog](https://blog.imzykj.cn/posts/93afb348/)
## 衍生品
- [Artalk:一款 ~~简洁~~ 有趣的自托管评论系统 (By monsterxcn)](https://github.com/monsterxcn/Artalk)
## 终于更新了!
在 Artalk v1 向 v2 的跨越期间,我经历了高考,这真是一段超级漫长的时间呢。
高考后,时间变得相对充裕,Artalk 后端采用 Golang 完成了重置,同时 Artalk 的功能也在不断完善当中。 🥳
<p style="text-align: right;">@qwqcode</p>
-7
View File
@@ -1,7 +0,0 @@
# 置入博客
本页面内容已移动至 <https://artalk.js.org/develop/import-blog.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/develop/import-blog.html';
</script>
@@ -1,7 +0,0 @@
# 置入框架
本页面内容已移动至 <https://artalk.js.org/develop/import-framework.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/develop/import-framework.html';
</script>
-7
View File
@@ -1,7 +0,0 @@
# 前端部署
本页面内容已移动至 <https://artalk.js.org/guide/deploy.html>。
<script setup lang="ts">
if (!import.meta.env.SSR) window.location = 'https://artalk.js.org/guide/deploy.html';
</script>
+5 -7
View File
@@ -15,15 +15,13 @@
"serve:docs": "vitepress serve"
},
"devDependencies": {
"@artalk/plugin-katex": "^0.2.4",
"@artalk/plugin-lightbox": "^0.2.4",
"@nolebase/vitepress-plugin-git-changelog": "^2.6.1",
"artalk": "workspace:^",
"markdown-it-for-inline": "^2.0.1",
"vitepress": "1.3.4"
},
"dependencies": {
"@artalk/plugin-katex": "^0.2.1",
"@artalk/plugin-lightbox": "^0.2.2",
"katex": "^0.16.11",
"lightgallery": "^2.7.2",
"vue": "^3.4.38"
"vitepress": "1.4.1",
"vue": "^3.5.12"
}
}
+3
View File
@@ -0,0 +1,3 @@
/assets/*
cache-control: max-age=31536000
cache-control: immutable
+17
View File
@@ -0,0 +1,17 @@
/guide/frontend/import-blog.html /develop/import-blog.html 301
/guide/frontend/import-framework.html /develop/import-framework.html 301
/guide/frontend/install.html /guide/deploy.html 301
/guide/backend/data.html /guide/transfer.html 301
/guide/backend/build.html /develop/contributing.html 301
/guide/backend/fe-control.html /guide/frontend/config.html 301
/guide/backend/install.html /guide/deploy.html 301
/develop/api.html /http-api.html 301
/develop/plugs.md /develop/plugin.html 301
# Language redirect
/guide/* /zh/guide/:splat 302 Language=zh
/guide/* /en/guide/:splat 302 Language=en
/guide/* /en/guide/:splat 302
/develop/* /zh/develop/:splat 302 Language=zh
/develop/* /en/develop/:splat 302 Language=en
/develop/* /en/develop/:splat 302
File renamed without changes.
Loaded 100 of 647 files, more files were not shown because too many files have changed in this diff. Show more