Skip to content

Commit 49248ee

Browse files
authored
Update requirements.md (#27)
Improve shared hosting section
1 parent e377829 commit 49248ee

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/requirements.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,16 +30,16 @@ One of the first steps in the installer is to check your server for the proper r
3030

3131
### Shared Hosting
3232

33-
While shared hosts are not ideal for numerous reasons (don't use free hosts, you'll have
34-
a really bad time), it's still possible to run phpVMS. Read the
33+
While shared hosts are not ideal for numerous reasons, it's still possible to run phpVMS.
34+
Check especially CRON features/capabilities and hidden limits the provider applies while advertising the service as "limitless". Ram or resource usage limits (like I/O) may directly affect phpVMS and your operations.
35+
36+
*Don't use free hosts, you'll have a really bad time and they can not be supported.*
3537

3638
---
3739

3840
### VPS/Dedicated Hosts
3941

40-
If you have control over your server, the combination of nginx/php-fpm will offer you
41-
the best performance, over using Apache. It's the combination that I test with.
42+
If you have control over your server, the combination of nginx/php-fpm will offer you the best performance, over using Apache. It's the combination that I test with.
4243
It will also be much more secure, seeing that only the `/public` directory is exposed.
4344

44-
Pointing the vhost to the `/public` directory is the best way to run on a host that you
45-
control.
45+
Pointing the vhost to the `/public` directory is the best way to run on a host that you control.

0 commit comments

Comments
 (0)