Well, if it don't get problems with new tables/fields (migrating), its is
the solution I was looking for.
I just sugest separate the db connections config out of db.py in models,
creating a file 0db_config.py (or similar), to be preserved.
Usually, the settings of database connection(s) are difere
How about a flag when replacing an app via admin that preserves the
content of databases/ sessions/ errors/ uploads/ cache/ ?
On May 26, 1:08 pm, greenpoise wrote:
> Hmmm..I see. Tough stuff. I wonder if there is room for improvement in
> that area for web2py. Something that is transparent betwe
On May 26, 1:40 pm, Yarko Tymciurak
wrote:
> also consider:
>
> of the 3 places: development, staging / final testing, and
> deployment,
>
> some people stage by migrating / merging their existing site to a
> staging site, and then take their current deployment site "down" and
> deploy the stagin
also consider:
of the 3 places: development, staging / final testing, and
deployment,
some people stage by migrating / merging their existing site to a
staging site, and then take their current deployment site "down" and
deploy the staging site --- this is the kind of thing you _might_ want
to d
On May 26, 1:08 pm, greenpoise wrote:
> Hmmm..I see. Tough stuff. I wonder if there is room for improvement in
> that area for web2py. Something that is transparent between the
> developer and the production site.
Generally there are too many variables that depend on the target site
(although th
Hmmm..I see. Tough stuff. I wonder if there is room for improvement in
that area for web2py. Something that is transparent between the
developer and the production site.
Thanks
Dan
On May 26, 1:28 pm, Yarko Tymciurak
wrote:
> On May 26, 11:53 am, greenpoise wrote:
>
> > Oh no, I am not develo
On May 26, 11:53 am, greenpoise wrote:
> Oh no, I am not developing where the live data resides. But when I
> make changes to my application on my development environment, how do I
> transfer/update those changes on my production site?
You have to work out a procedure that works with your product
Oh no, I am not developing where the live data resides. But when I
make changes to my application on my development environment, how do I
transfer/update those changes on my production site?
On May 26, 12:36 pm, Thadeus Burgess wrote:
> You probably don't want to develop on your live data.
>
>
8 matches
Mail list logo
