aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoralyx <alyx@aleteoryx.me>2024-06-01 11:39:17 -0400
committeralyx <alyx@aleteoryx.me>2024-06-01 11:39:17 -0400
commit14e8b1d3f2ce600e6cb5d39c8e503a11494aa757 (patch)
tree78b08334a1742ed5f725fbb19d47ca44056f6fd7
parentb5f931b9c9344e9db07abfe9de1e1ca5e64342bb (diff)
downloadvisitors_dot_php-14e8b1d3f2ce600e6cb5d39c8e503a11494aa757.tar.gz
visitors_dot_php-14e8b1d3f2ce600e6cb5d39c8e503a11494aa757.tar.bz2
visitors_dot_php-14e8b1d3f2ce600e6cb5d39c8e503a11494aa757.zip
mention file ownership in readme
-rw-r--r--README.md1
1 files changed, 1 insertions, 0 deletions
diff --git a/README.md b/README.md
index 533b0c9..37f19ee 100644
--- a/README.md
+++ b/README.md
@@ -12,6 +12,7 @@ The third number is the non-database revision.
To deploy, edit the top of `visitors.php` with your desired configuration, and then upload it to your webserver or hosting provider.
It must support client-side scripting, so Github Pages, Neocities, etc. are all out of the question.
+Additionally, your webserver must have write access to the database, otherwise the script will fail to save stuff.
There are no security risks to your database file being publically accessible, as it only contains the same info the page will display.
This may change in a future release.