Page 1 of 1

new install -

Posted: 04 Dec 2017, 11:21
by phpgraham
Hi

Just ran a new install
"aimeos/aimeos-laravel": "~2017.10.3"
"php artisan vendor:publish --tag=public --force",
"php artisan vendor:publish",
"php artisan migrate",
composer update

It responded nothing to migrate ?

Is this correct? is there no database tables to install ?

Re: new install - nothing to migrate ?

Posted: 04 Dec 2017, 11:22
by aimeos
The database tables are created with this command:

Code: Select all

./artisan aimeos:setup

Re: new install -

Posted: 04 Dec 2017, 11:26
by phpgraham
Ignore that post
the next command sets up tables :)
php artisan aimeos:setup --option=setup/default/demo:1

all going well so far..

Re: new install -

Posted: 04 Dec 2017, 11:44
by phpgraham
I noticed in instructions you have:
To see all components and get everything working, you also need to create your main Blade template in resources/views/app.blade.php.
Laravel 5.5 default install now puts app.blade.php in resources/views/layouts folder

So to get aimeos to work you have to move the app.blade.php file from
resources/views/layout folder
to
resources/views folder

then site is viewable

Re: new install -

Posted: 04 Dec 2017, 12:03
by phpgraham
i notice all the javascript and css is linked to https://cdnjs.cloudflare.com

the admin site hangs waiting for this download

Is there a way to set up to disable cloudfare linkage and just have local routing of js / css / images ?
for local development server this would be best, i can understand production live server usage of cloudfare is best

Re: new install -

Posted: 04 Dec 2017, 21:54
by aimeos
You can overwrite the Blade template for the JQAdm interface and replace the cloudflare links by links to local files:
https://github.com/aimeos/aimeos-larave ... .blade.php