Improve environment variable usage documentation

Open
#273 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker, postgresql
Domain
databases, documentation

Research direction

Start with the Chinese installation document's environment variables section and review the AUTO_INSTALL guidance alongside the container and PostgreSQL behavior described in the issue. Done means the documentation explains the configuration and restart scenario clearly, including the need to account for existing database content when no Docker volume is mapped.

Written by the indexing model from the issue text.

Description

bug

Describe the error

I have completely read the Chinese installation document of Answer. I need to add a more complete description of the AUTO_INSTALL setting in environment variables. If there is no docker volumes mapping, when using environment variables for Answer installation, delete the Answer to run the container. And run the Answer container again, Answer will populate the database again, but the database already has content, Answer will prompt an error (the config.yaml file is missing, and the database uses postgresql).

Reappear

Set AUTO_INSTALL to true according to the document, and the installation will be automatically successful. The data has been written to the database. At this time, Answer can be accessed normally. After deleting the running container and using the same parameters, Answer will write the configuration to the database again. information, but the same configuration information already exists in postgresql.

Expected behavior

AnswerYou can use environment variables for parameter configuration and run, no configuration file is required.

Dominant language
TypeScript
Stars
47
Forks
70
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/answer-website

All issues in apache/answer-website

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.