Styjun

Does knowing the surface area of all faces uniquely determine a tetrahedron?

How did Avada Kedavra get its name?

How did the European Union reach the figure of 3% as a maximum allowed deficit?

How to address players struggling with simple controls?

Why should the equality of mixed partials be "intuitively obvious"?

100-doors puzzle

How "fast" does astronomical events happen?

How do I run a script as sudo at boot time on Ubuntu 18.04 Server?

How can I detect if I'm in a subshell?

Can I drive in EU states and Switzerland with German proof of a surrendered U.S. license?

On George Box, Galit Shmueli and the scientific method?

Is it possible for underground bunkers on different continents to be connected?

Interview was just a one hour panel. Got an offer the next day; do I accept or is this a red flag?

Right indicator flash-frequency has increased and rear-right bulb is out

Can you cover a cube with copies of this shape?

My husband's visa refused but mine wasn't -- can I travel?

How do I gain the trust of other PCs?

High-end PC graphics circa 1990?

Why is gun control associated with the socially liberal Democratic party?

How can I ping multiple IP addresses at the same time?

How to avoid offending original culture when making conculture inspired from original

Why is Skinner so awkward in Hot Fuzz?

Co-worker is now managing my team. Does this mean that I'm being demoted?

Background for black and white chart

What GIT / workflow do I use to avoid overwriting my server side Django users, with my local users who are dummy/test users?

Git for beginners: The definitive practical guideHow to selectively merge or pick changes from another branch in Git?Git workflow and rebase vs merge questionsPushing an existing Git repository to SVNHow do I force “git pull” to overwrite local files?Throw away local commits in GitHow can I reconcile detached HEAD with master/origin?Preferred Github workflow for updating a pull request after code reviewVarious ways to remove local Git changesGit - Undo pushed commits

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;

1

I am developing a Django application in Atom locally, and then on pythonanywhere, when I'm ready, I'm doing a GIT PUSH command after syncing those changes to GITHUB. The problem is, at some point, those changes which were pushed through from my local development env have overwritten all my live users with just the local dummy users I've been using for testing and development.

Basically, I'm testing the login and registration system locally, logging in and registering with lots of dumb emails. Once I was happy it was working, I synced the Django code I'd changed to GITHUB (with the desktop app) and then did a GIT PUSH command on a PythonAnywhere (my server) console. The sqlite DB is included in those updates/sync - is that correct? Or should it just be totally ignored?

I just realised, that one (perhaps all?) pushes have overwritten my sqlite DB, and there were perhaps 30 or so actual users who had signed up on the website whose data is no longer registered on the site. I managed to find a trace of them in the Django Admin logs, and I've found the version history of the Sqlite DB on GITHUB, but my question is - how do I avoid this happening?

What is the workflow to avoid this situation in the future? And is there a command I can run in shell to get those users back into my 'live' database from the backedup SQlite file?

I know this is a simple question, but I'm new to development and I'm slowly getting there with troubleshooting the code, but versioning, GIT, and workflow are tricky things to get my head around.

python django git sqlite github

share|improve this question

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I should say - when I did my GIT PUSH (and started to push the site live) via a terminal, GIT told me something about 'docking' changes? Like, before I could push the changes, it forced me to do a command before I could do that. I did as I was told then pushed the changes - is this where I've gone wrong?
  
  – phil0s0pher
  Mar 25 at 3:55
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It was GIT STASH. This is what I was asked to do. Update - the data from my users is not in any versions of my database which I went and looked through on GITHUB.
  
  – phil0s0pher
  Mar 25 at 4:03
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You don't commit your database to your repository. You shouldn't even use sqlite in production.
  
  – Klaus D.
  Mar 25 at 4:05
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should have ignored the sqlite database completely. Just commit the migrations and re-apply them (python manage.py migrate) on the production server each time you deploy.
  
  – Selcuk
  Mar 25 at 4:05
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please be advised that if you remove the DB from the repository and push — it will be removed at the server-side.
  
  – phd
  Mar 25 at 12:03
  

  
  
  
  

 | 
show 2 more comments

1

I am developing a Django application in Atom locally, and then on pythonanywhere, when I'm ready, I'm doing a GIT PUSH command after syncing those changes to GITHUB. The problem is, at some point, those changes which were pushed through from my local development env have overwritten all my live users with just the local dummy users I've been using for testing and development.

Basically, I'm testing the login and registration system locally, logging in and registering with lots of dumb emails. Once I was happy it was working, I synced the Django code I'd changed to GITHUB (with the desktop app) and then did a GIT PUSH command on a PythonAnywhere (my server) console. The sqlite DB is included in those updates/sync - is that correct? Or should it just be totally ignored?

I just realised, that one (perhaps all?) pushes have overwritten my sqlite DB, and there were perhaps 30 or so actual users who had signed up on the website whose data is no longer registered on the site. I managed to find a trace of them in the Django Admin logs, and I've found the version history of the Sqlite DB on GITHUB, but my question is - how do I avoid this happening?

What is the workflow to avoid this situation in the future? And is there a command I can run in shell to get those users back into my 'live' database from the backedup SQlite file?

I know this is a simple question, but I'm new to development and I'm slowly getting there with troubleshooting the code, but versioning, GIT, and workflow are tricky things to get my head around.

python django git sqlite github

share|improve this question

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I should say - when I did my GIT PUSH (and started to push the site live) via a terminal, GIT told me something about 'docking' changes? Like, before I could push the changes, it forced me to do a command before I could do that. I did as I was told then pushed the changes - is this where I've gone wrong?
  
  – phil0s0pher
  Mar 25 at 3:55
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  It was GIT STASH. This is what I was asked to do. Update - the data from my users is not in any versions of my database which I went and looked through on GITHUB.
  
  – phil0s0pher
  Mar 25 at 4:03
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You don't commit your database to your repository. You shouldn't even use sqlite in production.
  
  – Klaus D.
  Mar 25 at 4:05
  

  
  
  
  


• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  You should have ignored the sqlite database completely. Just commit the migrations and re-apply them (python manage.py migrate) on the production server each time you deploy.
  
  – Selcuk
  Mar 25 at 4:05
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Please be advised that if you remove the DB from the repository and push — it will be removed at the server-side.
  
  – phd
  Mar 25 at 12:03
  

  
  
  
  

 | 
show 2 more comments

I am developing a Django application in Atom locally, and then on pythonanywhere, when I'm ready, I'm doing a GIT PUSH command after syncing those changes to GITHUB. The problem is, at some point, those changes which were pushed through from my local development env have overwritten all my live users with just the local dummy users I've been using for testing and development.

Basically, I'm testing the login and registration system locally, logging in and registering with lots of dumb emails. Once I was happy it was working, I synced the Django code I'd changed to GITHUB (with the desktop app) and then did a GIT PUSH command on a PythonAnywhere (my server) console. The sqlite DB is included in those updates/sync - is that correct? Or should it just be totally ignored?

I just realised, that one (perhaps all?) pushes have overwritten my sqlite DB, and there were perhaps 30 or so actual users who had signed up on the website whose data is no longer registered on the site. I managed to find a trace of them in the Django Admin logs, and I've found the version history of the Sqlite DB on GITHUB, but my question is - how do I avoid this happening?

What is the workflow to avoid this situation in the future? And is there a command I can run in shell to get those users back into my 'live' database from the backedup SQlite file?

I know this is a simple question, but I'm new to development and I'm slowly getting there with troubleshooting the code, but versioning, GIT, and workflow are tricky things to get my head around.

python django git sqlite github

share|improve this question

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

share|improve this question

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

share|improve this question

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617

asked Mar 25 at 3:51

phil0s0pherphil0s0pher

3617