If DB is local postgres, or mysql, export data on old machine and import on
the other after migration. This may takes some experimentation to get keys
importing properly.
If external and managed (say RDS), then migrations are not needed - the DB
is already there and populated. The above expor
This works for sqlite. postgre, etc. you have to do as above.
On Monday, December 10, 2018 at 8:03:10 PM UTC-5, Simon A wrote:
>
> if you are really lazy, you can just zip your whole project. then transfer
> to another machine.
>
> I transfer my projects from work (using windows) to home (using
On 11/12/2018 12:03 PM, Simon A wrote:
On Tuesday, December 11, 2018 at 3:14:07 AM UTC+8, computer
engineering Forum wrote:
I want to change my pc but i fear i wont be able to access the
projects
I would assume my new pc is going to fail five minutes after I
successfully transfer pr
if you are really lazy, you can just zip your whole project. then transfer
to another machine.
I transfer my projects from work (using windows) to home (using ubuntu)
then vice versa. I only had to manually install the necessary packages will
be notified to you when you need to get them install
1. Make requirement file let's say requirement.txt using pip freeze
command, which keep records of packages used in the project.
2. Make a copy of project folder to the new machine.
3. Create virtual environment on new machine.
4. Activate and install package from requirement.txt file to the virtua
I want to change my pc but i fear i wont be able to access the projects
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com
6 matches
Mail list logo
