Setup a PHP/Laravel 5 project with Bootstrap SB Admin 2 in Microsoft Azure -

-

my plan make lavarel project using bootstrap sb admin 2 template. in order tweak azure, used tutorial.

instead of bitbucket used github.

in azure web app, installed composer extension. kudu console installed bower , gulp

d:\home\site>npm install bower npm warn enoent enoent: no such file or directory, open 'd:\home\site\package.json'  npm warn site no description  npm warn site no repository field.  npm warn site no readme data npm warn site no license field.   d:\home\site>npm install gulp npm warn deprecated graceful-fs@3.0.8: graceful-fs v3.0.0 , before fail on node releases >= v7.0. please update graceful-fs@^4.0.0 possible. use 'npm ls graceful-fs' find in tree. npm warn deprecated lodash@1.0.2: lodash@<3.0.0 no longer maintained. upgrade lodash@^4.0.0. npm warn deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 , before fail on node releases >= v7.0. please update graceful-fs@^4.0.0 possible. use 'npm ls graceful-fs' find in tree.

i prepared laravel framework sb admin in localhost , tried push in github. result failure because azure cannot sychronize github. think there problem either bower or gulp don't know how fix it. appreciated. in advance.

the result: enter image description here

command: d:\home\siteextensions\composerextension\hooks\deploy.cmd  install dependencies composer  loading composer repositories package information  installing dependencies lock file  warning: lock file not date latest changes in composer.json. may getting outdated dependencies. run update update them.  nothing install or update  generating optimized autoload files  > php artisan clear-compiled  > php artisan optimize  generating optimized class loader      [symfony\component\process\exception\processtimedoutexception]               process "php artisan optimize" exceeded timeout of 300 seconds.      error has occurred during web site deployment.  install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [--] [<packages>]...  loading composer repositories package information\r\ninstalling dependencies lock file\r\nwarning: lock file not date latest changes in composer.json. may getting outdated dependencies. run update update them.\r\nnothing install or update\r\ngenerating optimized autoload files\r\n> php artisan clear-compiled\r\n> php artisan optimize\r\n\r\n                                                                           \r\n  [symfony\component\process\exception\processtimedoutexception]           \r\n  process "php artisan optimize" exceeded timeout of 300 seconds.  \r\n                                                                           \r\n\r\ninstall [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--ignore-platform-reqs] [--] [<packages>]...\r\nc:\program files (x86)\siteextensions\kudu\55.50526.2249\bin\scripts\starter.cmd d:\home\siteextensions\composerextension\hooks\deploy.cmd

you can remove commands:

"php artisan clear-compiled", "php artisan optimize"

under "post-install-cmd" scripts closure in composer.json file. run these commands via vso or kudu console site after deployment.

here same issue on so, deploying laravel app on azure. , can refer answer workaround solve issue.


Comments

Post a Comment

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

-
this error has shown on many times, seems. prominent answer issue seems restkit 0.20 — coredata: error: failed call designated initializer on nsmanagedobject class however, solution posted doesn't work me. let's start beginning: i want upload file server. want parse response make sure uploaded. if not, try again later. model has boolean variable called nsnumber *senttoserver purpose (in coredata, bool saved nsnumber ) . because don't know whether sending going successful, save entity coredata model first before sending via restkit. when post request successful, server returns json string this: {"id":14,"created":true} notice that, of course, id not set on coredata model yet, both id , created new informations model. here's model: @interface recording : nsmanagedobject @property (nonatomic, retain) nsstring * audiofilepath; @property (nonatomic, retain) nsdate * createdat; @property (nonatomic, retain) nsstring * deviceid; @...
Read more

java - Digest auth with Spring Security using javaconfig -

-
so i'm trying create digest authentication spring following documentation trying translate xml "requirements" in java requirements. let's have xml in docs: <bean id="digestfilter" class= "org.springframework.security.web.authentication.www.digestauthenticationfilter"> <property name="userdetailsservice" ref="jdbcdaoimpl"/> <property name="authenticationentrypoint" ref="digestentrypoint"/> <property name="usercache" ref="usercache"/> </bean> <bean id="digestentrypoint" class= "org.springframework.security.web.authentication.www.digestauthenticationentrypoint"> <property name="realmname" value="contacts realm via digest authentication"/> <property name="key" value="acegi"/> <property name="noncevalidityseconds" value="10"/> </b...
Read more

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -

-
my .env: app_env=local app_debug=true app_key=myappkey app_url=http://localhost db_connection=mysql db_host=localhost db_port=3306 db_database=gestiontaller db_username=root db_password='root' cache_driver=file session_driver=file queue_driver=sync redis_host=127.0.0.1 redis_password=null redis_port=6379 mail_driver=smtp mail_host=mailtrap.io mail_port=2525 mail_username=null mail_password=null mail_encryption=null i've tried password ", ' , without, restarting server every time. i've tried changing localhost 172.0.0.1. yes, password correct, running mysql -u root -p introducing password root in prompt can go mysql. users table: +------------------+-----------+ | user | host | +------------------+-----------+ | debian-sys-maint | localhost | | mysql.sys | localhost | | root | localhost | | root1 | localhost | +------------------+-----------+ i've added homestead.yaml this: database_port: 3306 ...
Read more