2014-03-06 18:36 GMT+01:00 Federico Bruni :
> 2014-03-06 18:20 GMT+01:00 Federico Bruni :
>
> 2014-03-03 13:01 GMT+01:00 Federico Bruni :
>>
>> First of all, the DATABASES options are divided in 3 files:
>>>
>>> - local_settings.py: the setting for local development. By default,
>>> sqlite is used
2014-03-06 18:20 GMT+01:00 Federico Bruni :
> 2014-03-03 13:01 GMT+01:00 Federico Bruni :
>
> First of all, the DATABASES options are divided in 3 files:
>>
>> - local_settings.py: the setting for local development. By default,
>> sqlite is used. I wonder what's the best approach if I know that I
2014-03-03 13:01 GMT+01:00 Federico Bruni :
> First of all, the DATABASES options are divided in 3 files:
>
> - local_settings.py: the setting for local development. By default,
> sqlite is used. I wonder what's the best approach if I know that I want to
> deploy on PostgreSQL on the server. Shoul
Ah! Here's what I was missing!
Now I'm trying to manually sync the databases:
pg_dump -C -h localhost -U localuser dbname | psql -h remotehost -U
remoteuser dbname
But I have problem with the port 5432. I already tried to add ip_private to
listen_addresses in postgresql.conf, as suggested here:
h
Fabric does not sync the content of the databases.
Fabric does sync the database schemas!
On Mon, Mar 3, 2014 at 8:03 AM, Federico Bruni wrote:
> 2014-03-03 13:01 GMT+01:00 Federico Bruni :
>
> Now I should find out why my real project is failing. Maybe I could start
>> it from scratch step by
2014-03-03 13:01 GMT+01:00 Federico Bruni :
> Now I should find out why my real project is failing. Maybe I could start
> it from scratch step by step and see what happens.
>
I've just one more test: added a page in my local project and then launched
'fab deploy' to send the changes to the server