cookiecutter/cookiecutter-django
1
1
Fork 0
mirror of https://github.com/cookiecutter/cookiecutter-django.git synced 2025-10-30 07:27:33 +03:00
Code Issues Packages Projects Releases Wiki Activity

More simplification.

Browse Source
This commit is contained in:
Audrey Roy Greenfeld 2015-10-03 16:56:53 -07:00
parent 2d609432b9
commit d09abc8d86
1 changed files with 4 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/developing-locally-docker.rst
View File

@ -36,16 +36,13 @@ name them accordingly. Instead of 'dev1' you might have 'dev2', 'myproject',
Get the IP Address Get the IP Address
-------------------- --------------------
Acquiring the IP Address is good for two reasons: Once your machine is up and running, run this::
1. Confirms that the machine is up and running.
2. Tells us the IP address where our Django project is being served.
::
$ docker-machine ip dev1 $ docker-machine ip dev1
123.456.789.012 123.456.789.012
This is also the IP address where the Django project will be served from.
Saving changes Saving changes
-------------- --------------
@ -53,15 +50,12 @@ If you are using OS X or Windows, you need to create a /data partition inside th
virtual machine that runs the docker deamon in order make all changes persistent. virtual machine that runs the docker deamon in order make all changes persistent.
If you don't do that your /data directory will get wiped out on every reboot. If you don't do that your /data directory will get wiped out on every reboot.
To create a persistent folder, log into the virtual machine by running: To create a persistent folder, log into the virtual machine by running::
::
$ docker-machine ssh dev1 $ docker-machine ssh dev1
$ sudo su $ sudo su
$ echo 'ln -sfn /mnt/sda1/data /data' >> /var/lib/boot2docker/bootlocal.sh $ echo 'ln -sfn /mnt/sda1/data /data' >> /var/lib/boot2docker/bootlocal.sh
In case you are wondering why you can't use a host volume to keep the files on In case you are wondering why you can't use a host volume to keep the files on
your mac: As of `boot2docker` 1.7 you'll run into permission problems with mounted your mac: As of `boot2docker` 1.7 you'll run into permission problems with mounted
host volumes if the container creates his own user and chown's the directories host volumes if the container creates his own user and chown's the directories