the databases/ is needed if you need to do migrations.
you can skip it only if you always use migrate=False in prod.
On Wednesday, February 3, 2016 at 3:00:32 AM UTC+1, Alex Glaros wrote:
>
> is the correct method to do a "Pack Custom" without the "databases", then
> send the rest to the new site
is the correct method to do a "Pack Custom" without the "databases", then
send the rest to the new site, along with the Postgres dump file?
In other words would be sending
1. just code and other stuff (controller, static, db.py, etc) without
data, and
2. pg_dump file separately
3.
web2py is great but IMHO it should be constrained to do it work, that is to
be a web framework. Backends should be treated as such, and backup/restore
procedure should definitely live only there, with specific tools optimized
to do what they do. A right tool for each job in this case translates
worked! your last line sums up my feelings :-)
--
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
Keep in mind that when using SQLite, the database moves with the app
because the SQLite database file is stored in the app's /databases folder.
This is not the case for any other databases.
Anthony
On Friday, January 29, 2016 at 4:07:02 PM UTC-5, Alex Glaros wrote:
>
> I move my app back and fo
set migrate=False.
do a backup (pgdump) on #1
do a restore on #2
live happy.
On Friday, January 29, 2016 at 10:07:02 PM UTC+1, Alex Glaros wrote:
>
> I move my app back and forth between different development PCs and when I
> pack the app on site #1 and upload to site #2 there is no data in it.
>
6 matches
Mail list logo
