Download the latest edition of the StoreCore files from the GitHub
repository if you haven’t already. Always download or fork the
master
branch for production purposes.
Create a new MySQL database for StoreCore on your web server. Do not use
the default MySQL test
database or a database name with the test_
prefix.
Add a MySQL user who has all privileges for accessing and modifying the StoreCore database.
Find the config.php
configuration file, then edit the file and add your
database information in the Database
section.
Optional. If configured correctly, StoreCore is able to install the
database by itself. However, the installation MAY run faster and smoother
if you install the database manually with a database administration tool
like MySQL Workbench, phpMyAdmin, or a MySQL command line interface. First
run the SQL file core-mysql.sql
to create all tables; next run the
i18n-dml.sql
file to add all language pack data. Both SQL files are
located in the /StoreCore/Database/
folder.
Upload the StoreCore files to the desired location on your web server. This
usually is a folder called public_html
for a domain or www
for a
subdomain like www.example.com
. Do not upload the /tests/
folder to a
production server (or delete it afterwards): this folder contains PHP unit
tests for development purposes.
Run the StoreCore installation by accessing the /install/
folder in a web
browser. For example, if StoreCore was uploaded for the www.example.com
host name, then point your browser to the URL https://www.example.com/install/
.
If StoreCore was not previously installed, you will be guided through the
necessary steps to complete the installation.
All installation and configuration activities are logged to .log
text files
in the /logs/
directory. If the StoreCore installation fails for any reason,
please first check these log files for possible errors, warnings or other
critical messages.
The location of the /logs/
directory is defined in the global constant
STORECORE_FILESYSTEM_LOGS_DIR
in the config.php
configuration file. If
this global constant is undefined (or the config.php
file was not loaded),
log files MAY be saved in different directories. This usually is the current
working directory for the main PHP application, for example the /install/
directory when you are executing the /install/index.php
application.
Please read through our contributing guidelines. Included are directions for opening issues, posting feature requests, coding standards, and notes on development.
Editor preferences are available in the editor config for easy use in common text editors. Read more and download plugins at http://editorconfig.org.
For transparency into our release cycle and in striving to maintain backward compatibility, StoreCore is maintained under the Semantic Versioning (SemVer) guidelines Sometimes we may screw up, but we’ll adhere to those rules whenever possible.
StoreCore repositories use three kinds of labels, or tags, to track issues on GitHub:
Issue type | Color | Hex |
---|---|---|
bug | Red 500 | #f44336 |
documentation | Deep Purple 500 | #673ab7 |
enhancement | Teal 500 | #009688 |
feature request | Green 500 | #4caf50 |
question | Pink 500 | #e91e63 |
Issue priority | MoSCoW | Shade | Hex |
---|---|---|---|
priority critical | P0 must have | Amber 800 | #ff8f00 |
priority high | P1 should have | Amber 600 | #ffb300 |
priority medium | P2 could have | Amber 400 | #ffca28 |
priority low | P3 won’t have | Amber 200 | #ffe082 |
Current issue status | Shade | Hex |
---|---|---|
under consideration | Grey 200 | #eeeeee |
planned | Grey 400 | #bdbdbd |
work in progress | Grey 600 | #757575 |
help wanted | Grey 900 | #212121 |
Ward van der Put
Tristan van Bokkem
Code copyright © 2015–2019 StoreCore™. All code is released as Free and Open-Source Software (FOSS) under the GNU General Public License.