[PR #116] [MERGED] README: use absolute path for sqlite DB in example config #305

New issue

Closed

opened 2026-03-13 16:16:35 +03:00 by kerem · 0 comments

kerem commented

2026-03-13 16:16:35 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/acme-dns/acme-dns/pull/116
Author: @julienschmidt
Created: 9/28/2018
Status: ✅ Merged
Merged: 9/28/2018
Merged by: @joohoi

Base: master ← Head: sqlite_path

📝 Commits (2)

6a93ba9 README: use absolute path for sqlite DB in example config
1d485b4 Merge branch 'master' into sqlite_path

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 README.md (+1 -1)

📄 Description

This PR changes the example config in the README to use an absolute path for the sqlite DB, like in the config.cfg.

Currently the example config would create a new DB in the current working directory. This might be intended (for testing purposes), but then should be documented accordingly so that the user changes the current working directory accordingly first.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/acme-dns/acme-dns/pull/116 **Author:** [@julienschmidt](https://github.com/julienschmidt) **Created:** 9/28/2018 **Status:** ✅ Merged **Merged:** 9/28/2018 **Merged by:** [@joohoi](https://github.com/joohoi) **Base:** `master` ← **Head:** `sqlite_path` --- ### 📝 Commits (2) - [`6a93ba9`](https://github.com/acme-dns/acme-dns/commit/6a93ba9a497c7771ab85da4ffbfb044a0a107946) README: use absolute path for sqlite DB in example config - [`1d485b4`](https://github.com/acme-dns/acme-dns/commit/1d485b45784bbcdfcd4dfbb5e298a0e2754b1ad3) Merge branch 'master' into sqlite_path ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -1) </details> ### 📄 Description This PR changes the example config in the README to use an absolute path for the sqlite DB, like in the `config.cfg`. Currently the example config would create a new DB in the current working directory. This might be intended (for testing purposes), but then should be documented accordingly so that the user changes the current working directory accordingly first. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>