Django Deployment in Helicon Zoo picks up wrong database

[mario Profile]

I deployed a Django app in Helicon Zoo. It has an external database and a SQLite database. My problem is with the SQLite database where the users are. When I deployed the site, instead of using the database that I already had, the deployed project created a new database and I had to create my username again to be able to log in to the web app.

So now if I make a change in the database in my development machine I have to make the same changes in the database in the production server.

In the development machine the sqlite file is in my src folder. In the production server the sqlite is in src as well as in the Project folder. But the one being used is the one in the project folder.

I tried to look for a solution of where to change the settings for the path for the sqlite in Helicon Zoo database but didn't find anything.

Has anyone had this problem?

[Suser1970 Profile]

I have the same problem. Any help??

[alvinaash Profile]

So to acquaint it first you have with present "Zoo - > Formats - > Python reach out" in the territory where you require this site. Request is so all startup contents did their business and somebody to do my task virtualenv is made so you should see welcome Python broaden page

[alvinaash Profile]

So to acquaint it first you have with present "Zoo - > Formats - > Python reach out" in the territory where you require this site. Request is so all startup contents did their business and somebody to do my task virtualenv is made so you should see welcome Python broaden page