mysql - Migration doesn't execute when I push my Laravel app on Pagodabox.io? -


when push laravel app on pagodabox, seams cancel migrations, keeps saying "command cancelled! success" , when try see live app, getting error message: 

sqlstate[42s02]: base table or view not found: 1146 table 'gopagoda.posts' doesn't exist (sql: select * `posts`).

i did set db credentials production (for mysql db).

an app works fine on local server.

also, may relevant, have free account. not sure if migrations available free accounts!?

<= :::::::::::::::::::::: end build output ::::::::::::::::::::::::::: """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""  +> uploading libs storage warehouse +> uploading build storage warehouse +> provisioning production servers (may take while)  web1 :: before deploy hook 1 :: /////////////////////////////// $ php artisan -n migrate --seed ************************************** *     application in production!     * **************************************  command cancelled! [✓] success

my boxfile:

#######  php boxfile  #######  # boxfile yaml config file houses configuration # related app’s deployment , infrastructure. allows # custom-configure app's environment specific # project's needs.  # documentation links # boxfile : pagodabox.io/docs/boxfile_overview # php settings in boxfile : pagodabox.io/docs/boxfile_php_settings # php on pagoda box : pagodabox.io/docs/php # build & deploy hooks : pagodabox.io/docs/build_deploy_hooks  global:   env:     - laravel_env:production  build:   type: php   stability: production   lib_dir: 'vendor'  web1:   type: php   name: laravel   httpd_document_root: public   php_extensions:     - mcrypt     - pdo_mysql   network_dirs:     storage1:       - app/storage/cache       - app/storage/logs       - app/storage/meta       - app/storage/sessions       - app/storage/views   before_deploy:     - 'php artisan -n migrate --seed'   after_deploy:     - 'php artisan -n cache:clear'     - 'rm -f app/storage/views/*'  database1:   name: gopagoda   type: **mysql**  storage1:   type: nfs   name: laravel-writables

with interactivity disabled, artisan automatically aborts migrations run in "production" environment. can force migration run adding --force flag migrate command.

web1:         before_deploy:     - 'php artisan -n migrate --seed --force'

-

Comments

Post a Comment

Popular posts from this blog

apache - PHP Soap issue while content length is larger -

we have developed soap based webservice post data third party webservice. accepts 4 params. in 1 of parameters accepts xml string no size limit restriction put in place. the webservice works fine in local environment running on php 5.2 , apache2. works content length long 10 mb. in staging server running nginx , php fpm.we have updated max post size , max upload filesize in php.ini , client_max_body param in nginx.conf allow upto 50 mb. but webservice client keeps on loading in staging environment. gives 502 timeout , gives soap error. can me understand issue here?
Read more

asynchronous - Python asyncio task got bad yield -

i confused how play around asyncio module in python 3.4. have searching api search engine, , want each search request run either parallel, or asynchronously, don't have wait 1 search finish start another. here high-level searching api build objects raw search results. search engine using kind of asyncio mechanism, won't bother that. # no asyncio module used here class search(object): ... self.s = some_search_engine() ... def searching(self, *args, **kwargs): ret = {} # raw searching according args , kwargs , build wrapped results ... return ret to try async requests, wrote following test case test how can interact stuff asyncio module. # here testing script @asyncio.coroutine def handle(f, *args, **kwargs): r = yield f(*args, **kwargs) return r s = search() loop = asyncio.get_event_loop() loop.run_until_complete(handle(s.searching, arg1, arg2, ...)) loop.close() by running pytest, return runtimeerror: task got bad yield : {results s...
Read more

javascript - Complete OpenIDConnect auth when requesting via Ajax -

the normal openidconnect server works like: you go a.com/secure-resource you 302 server your browser handles , sends identity server you login there it sends a.com via post you logged in on a.com , a.com/secure-resource on browser. however have scenario i'm trying solve need help. the user logged in on idserver the user logged in on a.com the user not logged in on b.com we need send ajax call web server b.com (from domain a.com ) b.com configured use openidconnect. but because request b.com via ajax, user cannot redirected idserver. (all in response 302 ) we can go ahead , handle 302 via ajax (i'm still not sure whether work, security-wise). but is there scenario in identityserver/openidconnect designed these situations? with identityserver in scenario setup server b.com use bearer token authentication, need use access token provided a.com in headers of ajax call $.ajax({ url: 'http://b.com', headers: { ...
Read more