Re: [mezzanine-users] Database not populated using Fabric deploy

[rwr . r3dp]

OK, I did manage to get logged into the admin pages by creating a django 
admin supersuer on the server. Just need a reliable method for syncing 
databases.

On Thursday, January 18, 2018 at 5:50:52 PM UTC-6, Eduardo Rivas wrote:
>
> Hello!
>
> The fabfile assumes your test database contains data not suitable for 
> production. You will need to manually dump and restore your DB in the 
> production server if you want to transfer your development data. My 
> suggestion is you create your own Fabric task to automate the process if 
> this is something you'll need to do often.
>
> As for the migrations, they are automatically run on first deploy, so 
> unless you've created new migrations, nothing will be applied when running 
> "migrate". What you have in production is a database with all tables and 
> columns created but no rows.
>
> Hope that helps :)
>
> On 2018-01-18 5:40 PM, rwr@gmail.com  wrote:
>
> Hi all 
>
> I'm brand new to Mezzanine, but not to Django.
>
> I created a test mezzanine project and it runs perfectly on loclhost. It's 
> a default project with the provided sample data, no mods at all.
>
> I deployed the project to a fresh Linode Debian Stretch server using 'fab 
> secure' and then 'fab all'. Everything seemed to work perfectly, I can hit 
> the site and see the Mezzanine homepage no problem. But it doesn't seem to 
> have populated the database on the server at all. I'm using postgres and 
> can see, using psql, that the project database was created. I also can't 
> login into the admin page of the site. Again, I believe this is simply 
> because database wasn't populated. All of the project log files on the 
> server are empty.
>
> I also ran 'fab deploy' and it seemed to work but tells me there were no 
> migrations to apply. I also ran 'python manage.py migrate', which also 
> reported no migrations to apply.
>
> What information can I provide to help understand what's going on here. 
> Or, is there just something, some step maybe, that I missed?
>
> Thanks in advance for ny help.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to mezzanine-use...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Database not populated using Fabric deploy

[rwr . r3dp]

OK, time to seek help again...

I have tried a number of backup/dump and restore/load mechanisms to try and 
sync data between my local development project db and the server production 
db. Again, fab deploy works great and I can access the site on my server. 
But no matter what db sync method I use, once the db is restored on the 
server side, I get an Internal Server Error (http 500) error. 

I've tried pg_dump/pg_restore, fab backup/restore, python manage.py 
dumpdata/loaddata. I also tried pgAdmin backup/restore. Every one produces 
the same results.

I've also created another project with no sample data, same results. Again, 
it deploys perfectly and is accessible. I'd be OK with this except once the 
site is on the production server I can't login to admin. The same situation 
if I include sample data in the project creation.

I've dug through the group posts and found lots of examples of folks using 
several methods for database sync but I can't get anything to work. I'm 
sure this shouldn't be this difficult and that I'm missing something dumb, 
but I can't for the life of me find it.

Any suggestions?



On Thursday, January 18, 2018 at 5:50:52 PM UTC-6, Eduardo Rivas wrote:
>
> Hello!
>
> The fabfile assumes your test database contains data not suitable for 
> production. You will need to manually dump and restore your DB in the 
> production server if you want to transfer your development data. My 
> suggestion is you create your own Fabric task to automate the process if 
> this is something you'll need to do often.
>
> As for the migrations, they are automatically run on first deploy, so 
> unless you've created new migrations, nothing will be applied when running 
> "migrate". What you have in production is a database with all tables and 
> columns created but no rows.
>
> Hope that helps :)
>
> On 2018-01-18 5:40 PM, rwr@gmail.com  wrote:
>
> Hi all 
>
> I'm brand new to Mezzanine, but not to Django.
>
> I created a test mezzanine project and it runs perfectly on loclhost. It's 
> a default project with the provided sample data, no mods at all.
>
> I deployed the project to a fresh Linode Debian Stretch server using 'fab 
> secure' and then 'fab all'. Everything seemed to work perfectly, I can hit 
> the site and see the Mezzanine homepage no problem. But it doesn't seem to 
> have populated the database on the server at all. I'm using postgres and 
> can see, using psql, that the project database was created. I also can't 
> login into the admin page of the site. Again, I believe this is simply 
> because database wasn't populated. All of the project log files on the 
> server are empty.
>
> I also ran 'fab deploy' and it seemed to work but tells me there were no 
> migrations to apply. I also ran 'python manage.py migrate', which also 
> reported no migrations to apply.
>
> What information can I provide to help understand what's going on here. 
> Or, is there just something, some step maybe, that I missed?
>
> Thanks in advance for ny help.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to mezzanine-use...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Database not populated using Fabric deploy

[rwr . r3dp]

Thanks for the quick reply, Eduardo . 

That makes perfect sense. That's why I didn't figure it out myself. lol...

I thought about the migration issue right after posting. It doesn't have 
anything to do with data, only model structure.

Thanks again for the help. 

On Thursday, January 18, 2018 at 5:50:52 PM UTC-6, Eduardo Rivas wrote:
>
> Hello!
>
> The fabfile assumes your test database contains data not suitable for 
> production. You will need to manually dump and restore your DB in the 
> production server if you want to transfer your development data. My 
> suggestion is you create your own Fabric task to automate the process if 
> this is something you'll need to do often.
>
> As for the migrations, they are automatically run on first deploy, so 
> unless you've created new migrations, nothing will be applied when running 
> "migrate". What you have in production is a database with all tables and 
> columns created but no rows.
>
> Hope that helps :)
>
> On 2018-01-18 5:40 PM, rwr@gmail.com  wrote:
>
> Hi all 
>
> I'm brand new to Mezzanine, but not to Django.
>
> I created a test mezzanine project and it runs perfectly on loclhost. It's 
> a default project with the provided sample data, no mods at all.
>
> I deployed the project to a fresh Linode Debian Stretch server using 'fab 
> secure' and then 'fab all'. Everything seemed to work perfectly, I can hit 
> the site and see the Mezzanine homepage no problem. But it doesn't seem to 
> have populated the database on the server at all. I'm using postgres and 
> can see, using psql, that the project database was created. I also can't 
> login into the admin page of the site. Again, I believe this is simply 
> because database wasn't populated. All of the project log files on the 
> server are empty.
>
> I also ran 'fab deploy' and it seemed to work but tells me there were no 
> migrations to apply. I also ran 'python manage.py migrate', which also 
> reported no migrations to apply.
>
> What information can I provide to help understand what's going on here. 
> Or, is there just something, some step maybe, that I missed?
>
> Thanks in advance for ny help.
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to mezzanine-use...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [mezzanine-users] Database not populated using Fabric deploy

[Eduardo Rivas]

Hello!

The fabfile assumes your test database contains data not suitable for 
production. You will need to manually dump and restore your DB in the 
production server if you want to transfer your development data. My 
suggestion is you create your own Fabric task to automate the process if 
this is something you'll need to do often.


As for the migrations, they are automatically run on first deploy, so 
unless you've created new migrations, nothing will be applied when 
running "migrate". What you have in production is a database with all 
tables and columns created but no rows.


Hope that helps :)


On 2018-01-18 5:40 PM, rwr.r...@gmail.com wrote:

Hi all

I'm brand new to Mezzanine, but not to Django.

I created a test mezzanine project and it runs perfectly on loclhost. 
It's a default project with the provided sample data, no mods at all.


I deployed the project to a fresh Linode Debian Stretch server using 
'fab secure' and then 'fab all'. Everything seemed to work perfectly, 
I can hit the site and see the Mezzanine homepage no problem. But it 
doesn't seem to have populated the database on the server at all. I'm 
using postgres and can see, using psql, that the project database was 
created. I also can't login into the admin page of the site. Again, I 
believe this is simply because database wasn't populated. All of the 
project log files on the server are empty.


I also ran 'fab deploy' and it seemed to work but tells me there were 
no migrations to apply. I also ran 'python manage.py migrate', which 
also reported no migrations to apply.


What information can I provide to help understand what's going on 
here. Or, is there just something, some step maybe, that I missed?


Thanks in advance for ny help.
--
You received this message because you are subscribed to the Google 
Groups "Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to mezzanine-users+unsubscr...@googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.


--
You received this message because you are subscribed to the Google Groups "Mezzanine 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[mezzanine-users] Database not populated using Fabric deploy

[rwr . r3dp]

Hi all

I'm brand new to Mezzanine, but not to Django.

I created a test mezzanine project and it runs perfectly on loclhost. It's 
a default project with the provided sample data, no mods at all.

I deployed the project to a fresh Linode Debian Stretch server using 'fab 
secure' and then 'fab all'. Everything seemed to work perfectly, I can hit 
the site and see the Mezzanine homepage no problem. But it doesn't seem to 
have populated the database on the server at all. I'm using postgres and 
can see, using psql, that the project database was created. I also can't 
login into the admin page of the site. Again, I believe this is simply 
because database wasn't populated. All of the project log files on the 
server are empty.

I also ran 'fab deploy' and it seemed to work but tells me there were no 
migrations to apply. I also ran 'python manage.py migrate', which also 
reported no migrations to apply.

What information can I provide to help understand what's going on here. Or, 
is there just something, some step maybe, that I missed?

Thanks in advance for ny help.

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to mezzanine-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.