There is nothing equivalent to this in web2py. You just remove that line. On Thursday, 22 May 2014 12:43:59 UTC-5, Diogo Munaro wrote: > > > Hey Massimo, and how could I replace > > > command: "django-admin.py syncdb --noinput" > > ? > > I need migrate=False because I have a loadbalancer with elastic beanstalk > > > Em quinta-feira, 25 de julho de 2013 11h45min05s UTC-3, Aladdin Teng > escreveu: >> >> Thank you very much. >> >> On Thursday, July 25, 2013 8:53:33 PM UTC+8, Massimo Di Pierro wrote: >>> >>> The instructions should be almost identical except that: >>> >>> 1) you do not pip install Django >>> 2) you do not ever call django-admin >>> 3) instead you download and unzip web2py. The web2py folder plays the >>> role of the mysite folder in the example >>> 4) you do not edit any django config file (there is no django!) >>> 5) instead you edit db.py and you replace db= DAL(...) with >>> >>> import os >>> uri = >>> “mysql://%(RDS_USERNAME)s:%(RDS_PASSWORD)s@%(RDS_HOSTNAME)s:%(RDS_PORT)s/%(RDS_DB_NAME)s” >>> >>> % os.environ >>> db = DAL(uri, pool_size=10) >>> session.connect(request, response db=db) # sessions in DB! >>> >>> 6) before you commit and push you must create a file >>> web2py/application.py which contains >>> <FILE web2py/application.py> >>> import sys >>> import os >>> path = os.path.dirname(os.path.abspath(__file__)) >>> os.chdir(path) >>> sys.path = [path] + [p for p in sys.path if not p == path] >>> sys.stdout = sys.stderr >>> import gluon.main >>> application = gluon.main.wsgibase >>> <FILE> >>> >>> This should work. If you try it please post your findings. >>> >>> Caveat 1. You must get web2py from web2py_src.zip from the web site and >>> not from the Git report else the web2py git repo will conflict with the git >>> repo you are supposed to create according to this tutorial. >>> >>> Caveat 2. From: >>> http://blog.uptill3.com/2012/08/25/python-on-elastic-beanstalk.html >>> "It's critical to understand that the Elastic Beanstalk images are all >>> ephemeral, in the 'old' style of AWS AMIs. This means that nothing on an >>> instances filesystem will survive through a deployment, redeployment, or >>> stoppage of the environment/instance. " This means that >>> session/tickets/uploads must all go to the file system. web2py admin will >>> be useful. You also needs to setup sticky sessions and I am not sure >>> whether AWS does it automatically or not. >>> >>> >>> On Wednesday, 17 July 2013 11:14:20 UTC-5, Aladdin Teng wrote: >>>> >>>> Hi! >>>> >>>> Is there an update on this demo? >>>> I am looking into AWS deployment too. >>>> >>>> Thanks. >>>> >>>> On Saturday, October 13, 2012 9:52:03 AM UTC+8, Massimo Di Pierro wrote: >>>>> >>>>> I will try a demo asap but I do not have an account so it will take a >>>>> tille time. In principle everything in eb is not django specific and >>>>> should >>>>> work with web2py almost out of them box. >>>>> >>>>> On Tuesday, 9 October 2012 11:42:35 UTC-5, CST International Mike >>>>> wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> I trying to find an AWS Elastic Beanstalk Web2py installation recipe. >>>>>> >>>>>> Amazon have a Django version >>>>>> http://docs.amazonwebservices.com/elasticbeanstalk/latest/dg/create_deploy_Python_django.html >>>>>> >>>>>> My Linux\web2py skill are a little weak and rusty. ( over a year now) >>>>>> >>>>>> Regards Michael >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>
-- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
