eBag requires Php5 (>=5.2.3 with OpenSSL support) and MySQL (proposed >=5.1.38). Recommended is to use with secure (https) connection and apc memory cache. Because of sharing large amount of data in memory across users (language) and performance reasons, eBag is figured out to run alone on one server. Using it in shared web hosting environment is safe if the other web applications not uses the cache, or they uses different memory variable names.
eBag user interface is optimized for resolutions above 1024x768.
Downloaded package unpack in your server htdocs folder. The index page opened in browser will redirect to installation procedure (if the application is not installed yet), where the configuration data must be defined. If the smpt server data are set, internet connection is required to check and validate them. If the installer returns error: the timezone cannot be set, set the timezone first in php.ini and restart the installation.
After successful installation the browser will be redirected to log in page, and with general username and password root the system is accessible.
For maximum security remove or change extension of migration scripts (like migrate71to8.php) placed in eBag/migrate (for versions before 8.0.0. eBag/models) directory manually or with the command line utility eBag/models/updater_clean.php .
eBag uses DejaVu (c) Bitstream fonts by default. For printing CJK or other unsupported characters the appropriate ttf font files path must be defined in eBag.ini manually.
In case of difficulties with installation, try to edit /eBag/conf/eBag.ini configuration file manually and run /eBag/models/baseinstall.php script to install the application.
Since eBag is beta software by default php notices interrupts program execution. Users who experience php notices this behavior can change in configuration file conf/eBag.ini with changing in section [error] option ignore_notices from value 0 to 1.
Delete the created bases (ebag, ebagstock, ebagtemp, ebagdata(year)) manually. Delete the file eBag/conf/installed.conf, open eBag in the browser and the new installation process will be started.
Create backup copy of /eBag/conf/eBag.ini file. Downloaded package unpack and overwrite existing files.
eBag.ini overwrite with backuped file and manually change version number and version type (beta/final) to
updated. Set folder permissions (uploads, tmp, conf, tfpdf/font/unifont). Restart the server. From version
6.0.0 delete system cache after first login selecting System reset in Settings.
Started from version 8.0.0. php command line utility updater.php is available to make the update process easier. Earlier versions (>= 3.0.0) can be updated if updater files (conf/servers.conf, models/updater.php, models/updater_call.php, models/updater_dump.php and models/updater_clean.php) from newer package are copied into appropriate directories. The updating process requires mysql server to run.
The updater called with option '--mysqldump' will dump databases ebag, ebagtemp, ebagstock and every base with name matching ebagdata + 4 digits (like ebagdata2017) into eBag/tmp directory.
On Linux systems it is recommended for the user who runs the updater to be member of www users (www-data) because of changing the group of newly created files and directories by need (or they have to be reviewed and changed after update). On Windows (if the updater is started with --platform=IIS) the IUSR will get full permissions over mentioned files.
Removing or renaming migration scripts (as migrateXtoY.php) from eBag/migrate (or eBag/models in versions before 8.0.0) directory is possible manually or with command line script updater_clean.php after updating if everything works as expected.
Please backup your base and application files before using the (early beta versions of) automated updater.
For more details run "php updater.php --help" in eBag/models directory from command line.
First steps after installation
The first step on freshly installed system is defining the company address in eBag settings options and setting up units, payment and shipping methods and production phases. Be careful because units, payment and shipping methods and production phases are editable only if they are not used by other documents (offers, orders, etc.) created before. However, new item can be added in a case that previous is mistyped.
Important is to change the default username and password, or create new user with all permissions, and delete the default user, because of security reasons.
Log in as new user, or simple continue to fill your base following the next logic: