Fixing the 'edit user' code, dealing with unchanged passwords.
The new UserImage mini-ORM class is done, suspiciously easy to build on top of the mini-ORM. We're retrieving the natal images (natal wheel, aspect table etc) successfully, and the web service supplies them in base64 encoded format. We can either store them in the database (as
either base64 or binary format) or write them to files somewhere, which is the method I prefer, if done correctly, then delivering them would effectively be Apache delivering static image files, with no PHP participation required.
Got the basic writing to a file sorted out. It does mean that there is a directory under the server which is writable by the 'www-data' group (or whichever group Apache is running as.) Each image is saved with the user id as part of the filename in a 'data' directory, and is accessible via Apache as a static file. There is a definite improvement in the delivery of images like the natal_wheel and aspect table.
Next is a list of upcoming transits. I need to merge the various configs we've set up for astro.conf, which has the best image engine config, and transit.conf, which was generated from a set of configuration items setup by Steve. Using that configuration set will give us a nice list of upcoming transits of some importance.
Subscribe to:
Post Comments (Atom)
Posts
2 comments:
user files in data directory.. could be tens of thousands of these so maybe split them up a/a a/b etc? Or some other mechanism?
Agreed - even something as simple as taking the first X digits of the user identity, which would split the user pool into at least 10^X pools.
Post a Comment