-
Prasi was designed to use its own folder-based database. The reason behind this was to ensure that Prasi could run under the most restrictive and cheapest of web hosting companies -- these often provide no access to proper databases.
We have no plans to integrate hooks to database systems in Prasi, mainly due to lack of time. If a volunteer wants to implement this, they are welcome to do so.
2009-07-09 20:51:01 UTC in Prasi
-
ab384 committed revision 166 to the Prasi SVN repository, changing 8 files.
2009-04-14 11:07:44 UTC in Prasi
-
ab384 committed revision 165 to the Prasi SVN repository, changing 4 files.
2008-12-04 13:16:32 UTC in Prasi
-
ab384 committed revision 164 to the Prasi SVN repository, changing 1 files.
2008-05-13 18:48:53 UTC in Prasi
-
Fixed in 1.5.1, thank you.
2008-05-13 18:43:18 UTC in Prasi
-
Fixed in 1.5.1, thank you.
2008-05-13 18:42:52 UTC in Prasi
-
ab384 committed revision 163 to the Prasi SVN repository, changing 7 files.
2008-05-13 18:37:17 UTC in Prasi
-
Yes, in principle https should be used for all traffic, and there is an option in Prasi to force the use of https. If your host does not allow https, consider moving to another one.
But thank you for the suggestion of using client-side hashing; I will look at how I can include this as an option in Prasi. At first sight it looks incompatible because with that system the passwords must be stored...
2008-05-13 07:53:31 UTC in Prasi
-
Indeed, the REMOTE_ADDR IP has been removed from the calculation of the authentication hash as a quick work-around for hosts with dynamic IP's. I forgot to propagate the changes to the PHP interface. I hope this did not cause you too much trouble. Thank you for the fix, it will be part of the next release.
2008-05-09 08:53:52 UTC in Prasi
-
This is very useful. Thank you. It will be part of the next release.
2008-05-09 08:41:38 UTC in Prasi
