You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/requirements.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,16 +30,16 @@ One of the first steps in the installer is to check your server for the proper r
30
30
31
31
### Shared Hosting
32
32
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.*
35
37
36
38
---
37
39
38
40
### VPS/Dedicated Hosts
39
41
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.
42
43
It will also be much more secure, seeing that only the `/public` directory is exposed.
43
44
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