Update README.md

This commit is contained in:
ThatGuy 2019-07-04 09:34:44 +00:00
parent 0abb8d70d0
commit 530972a2db

View File

@ -32,4 +32,27 @@ In order:
* Configures PHP.ini upload_max_filesize to 200M * Configures PHP.ini upload_max_filesize to 200M
* Restarts Apache2 * Restarts Apache2
* Pauses to let the web configuration be entered manually * Pauses to let the web configuration be entered manually
* Updates the Nextcloud config to include Redis and APCu memcaching * Updates the Nextcloud config to include Redis and APCu memcaching
## Questions
**What's the purpose of this script?**
To get people with minimal experience, up and running quickly with the minimum of effort. To remove the possibility of failure. To get Nextcloud working in an environment that will be fast, and efficient for the average home user. This is NOT intended to be used by veteran admins.
When a newbie sets up a server, invariably they forget things like memcaching, or AllowOverride All etc. This idea is to remove the guesswork.
**Why didnt you use MySQL or PostgreSQL?**
Good question. Two reasons. The first is that both MySQL and PostgreSQL use running services which consume memory even when not in use. PostgreSQL is particularly bad, using a minimum of 10Mb per open database. Ideally, this is supposed to be a small footprint installation, using minimal resources, but getting the best performance possible from those resources used.
The second reason, is that I'm lazy. It's much easier to script SQLite, with no permissions, than a bigger bulkier service.
**It's INSECURE!!!**
What did you expect? It's not so much "insecure", as it is "not hardened". There is only so much I am capable of doing in a script. I cant configure firewalls etc. I just don't have the knowledge.
**Why did you limit the uploads to 200M?**
Mostly because this is intended for small installations, with only a couple of users. Most people don't need anything more than a couple of hundred Mb per upload. Think pictures, the occasional MP3, maybe a few documents.