2.1 KiB

Raw Blame History

Lexiconga

This is the light-as-possible rewrite of Lexiconga.

Installation

Clone and run yarn and composer install to install dependencies.
Import src/structure.sql into a database called 'lexiconga' on your MariaDB server to get the database structure.
Copy src/php/api/config.php.changeme to src/php/api/config.php and update the values within to enable connections to your lexiconga database.

Requirements

Yarn 1.12.3+
PHP 7.2.18+
Composer 1.8.5+
MariaDB 10.1.37+
Apache 2.4+

Development

npm start bundles and watches frontend and backend changes. Set up a junction link to dist from the root of your php-processing web server.

It's less useful, but npm run serve-frontend-only will bundle and serve only the front end stuff from localhost:1234. The bundled files all still get bundled into dist.

Production

npm run bundle bundles and minifies the frontend stuff and also copies the backend stuff to dist. Be sure to run npm run clear to delete the contents of dist and .cache before using npm run bundle to make sure you don't get old dev versions of the bundled code included in your upload.

Migration

There is a script called src/php/api/migrate.php.changeme that can be used to help with the migration process from a version1 Lexiconga database into a master database. Note: Migration is intended only for migrating from an old server to a freshly-installed/empty new database. To use this, copy src/php/api/migrate.php.changeme to migrate.php somewhere in the version1 project (probably in /php) and copy the same to /api/migrate.php in your master project, making sure that all the variables for referencing the databases are correct.

Visit migrate.php on your version1 server with ?outgoing=true set in order to begin the transfer. The other server's migrate.php will receive an "incoming" request multiple times, and your screen will display messages as it works.

DELETE THESE migrate.php FILES IMMEDIATELY AFTER MIGRATION IS COMPLETE!.

2.1 KiB Raw Blame History