Multiuser installation of the system

Suppose you want to provide personal storages for your friends or other people. For example,

www.mysite.com/alex/
www.mysite.com/maria/
www.mysite.com/dad/

Of course, you can install the system individually for each user. The system occupies very little space, so it’s not a problem after all. The problem is updating user storages. Every time a newer version is out you will have to update scripts in each folder. To solve this issue we recommend installing the engine in a separate directory and then link users to the existing system. In this case you will have to update the system in one place only. Note, that you still need to create databases for each user individually, and each such user will have his or her individual settings.

Step 1

At first, install the system as usual. For example, into the eonza folder. You can use this installation as your personal storage. We can proceed without installation, but in this case you should put an empty conf.inc.php file into this directory. This is required to prevent others from installing the system here.

Step 2

This step should be repeated for each user you link, and can be automated. Let’s say you want to create a personal information storage for the user alex.

1. Create a folder named alex on the site. Set write permissions to this folder off the bat. You will clear them after the installation. If the file storage alex/storage will also be here, it should retain its write permissions.
2. Unpack eonza/tools/user.zip into the alex subdirectory. You should see three files there: .htaccess-i, ajax.php, index.php. If the system directory is different from /eonza, then you should replace paths to Eonza in these files.
3. Create a database for this user if it doesn’t exist yet.
4. Open www.mysite.com/alex/ in your browser. You should see the Eonza installation page. Specify all necessary data and finish the installation. The following files should appear in the alex directory: .htaccess and conf.inc.php. You can also place your custom.js here if you want.
5. Send to the alex user the login and the password you specified during installation. This user will have administrator permissions, and his system won’t conflict with other users on your website.

This way you can connect to Eonza as many users as you need, and whenever a newer version is released, you will have to update scripts in one place only.

With this method, you can install Eonza as a website administration panel. For example, you can install the system to the eonza directory, and give access to it from the admin directory. In this case, the engine will not contain any configuration files.