You can tell Django to move to a specific migration

    ./manage.py migrate myapp 0005_migration_to_run

But Django will run **every** migration up to (or back to) the migration you&#39;ve chosen.

You could try [faking][1] to the migration before

    ./manage.py migrate --fake myapp 0004_previous_migration
    ./manage.py migrate myapp 0005_migration_to_run

You might then want to fake to the migration you started at.

[1]: https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-option---fake

Is it possible to &#39;Open Quickly&#39; in the right pane of the Assistant Editor? This would increase productivity by like 20x

Xcode: Is it possible to &#39;Open Quickly&#39; the right pane of the Assistant Editor?

I am trying to push to my repo but receiving an error:

    fatal: unable to access &#39;https://github.com/myrepo.git/&#39;: Could not resolve proxy: --list        

I already changed the proxy settings :
                 
    git config --global --unset http.proxy  

my global config settings are:

    push.default=simple
    http.sslverify=false
    url.https://.insteadof=git://
    credential.helper=cache --timeout=3600

But still getting this error? How can I solve this?

                        

Git: How to remove proxy

In django 1.8 is there a way to run a specific migration and that migration only.

Not for one app only but a specific file in that apps migrations directory.

EDIT TO ORIGINAL:

        Traceback (most recent call last):
      File &quot;manage.py&quot;, line 10, in &lt;module&gt;
        execute_from_command_line(sys.argv)
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/__init__.py&quot;, line 338, in execute_from_command_line
        utility.execute()
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/__init__.py&quot;, line 330, in execute
        self.fetch_command(subcommand).run_from_argv(self.argv)
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/base.py&quot;, line 393, in run_from_argv
        self.execute(*args, **cmd_options)
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/base.py&quot;, line 444, in execute
        output = self.handle(*args, **options)
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/commands/migrate.py&quot;, line 146, in handle
        plan = executor.migration_plan(targets)
      File &quot;/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/db/migrations/executor.py&quot;, line 50, in migration_plan
        self.loader.graph.node_map[target].children
    KeyError: (&#39;wagtailcore&#39;, &#39;0001_initial&#39;)


Did a little searching and located this https://code.djangoproject.com/ticket/24225#no1

Django 1.8 Run a specific migration

In django 1.8 is there a way to run a specific migration and that migration only.
Not for one app only but a specific file in that apps migrations directory.
EDIT TO ORIGINAL:
<pre><code class="hljs language-arduino"> Traceback (most recent call last):
 File "manage.py", line 10, in &#x3C;module>
 execute_from_command_line(sys.argv)
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
 utility.execute()
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/__init__.py", line 330, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/base.py", line 393, in run_from_argv
 self.execute(*args, **cmd_options)
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/base.py", line 444, in execute
 output = self.handle(*args, **options)
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/core/management/commands/migrate.py", line 146, in handle
 plan = executor.migration_plan(targets)
 File "/home/vagrant/virtualenvs/aku/lib/python3.4/site-packages/django/db/migrations/executor.py", line 50, in migration_plan
 self.loader.graph.node_map[target].children
KeyError: ('wagtailcore', '0001_initial')
</code></pre>
Did a little searching and located this <a href="https://code.djangoproject.com/ticket/24225#no1" target="_blank" rel="noopener noreferrer">https://code.djangoproject.com/ticket/24225#no1</a>

Trying to create a super user for my database:

    manage.py createsuperuser

Getting a sad recursive message:

*Superuser creation skipped due to not running in a TTY. You can run `manage.py createsuperuser` in your project to create one manually.*

Seriously Django? Seriously?


The only information I found for this was the one listed above but it didn&#39;t work:
https://stackoverflow.com/questions/26980003/unable-to-create-superuser-in-django-due-to-not-working-in-tty

And this other one here, which is basically the same:
https://stackoverflow.com/questions/14059573/cant-create-super-user-django



Not able to create super user with Django manage.py

I&#39;m curious how other django developers manage multiple code branches (in git for instance) with migrations.

My problem is as follows:
- we have multiple feature branches in git, some of them with django migrations (some of them altering fields, or removing them altogether)
- when I switch branches (with `git checkout some_other_branch`) the database does not reflect always the new code, so I run into &quot;random&quot; errors, where a db table column does not exist anymore, etc...

Right now, I simply drop the db and recreate it, but it means I have to recreate a bunch of dummy data to restart work. I can use fixtures, but it requires keeping track of what data goes where, it&#39;s a bit of a hassle.

Is there a good/clean way of dealing with this use-case? I&#39;m thinking a `post-checkout` git hook script could run the necessary migrations, but I don&#39;t even know if migration rollbacks are at all possible.

django migrations - workflow with multiple dev branches

I am trying to write `setup.py` for my package. My package needs to specify a dependency on another Git repository.

This is what I have so far:

    from setuptools import setup, find_packages

    setup(
        name=&#39;abc&#39;,
        packages=find_packages(),
        url=&#39;https://github.abc.com/abc/myabc&#39;,
        description=&#39;This is a description for abc&#39;,
        long_description=open(&#39;README.md&#39;).read(),
        install_requires=[
            &quot;requests==2.7.0&quot;,
            &quot;SomePrivateLib&gt;=0.1.0&quot;,
            ],
        dependency_links = [
         &quot;git+git://github.abc.com/abc/SomePrivateLib.git#egg=SomePrivateLib&quot;,
        ],
        include_package_data=True,
    )

When I run:

    pip install -e https://github.abc.com/abc/myabc.git#egg=analyse

I get

&gt; Could not find a version that satisfies the requirement
&gt; SomePrivateLib&gt;=0.1.0 (from analyse) (from versions: ) No matching
&gt; distribution found for SomePrivateLib&gt;=0.1.0 (from analyse)

What am I doing wrong?





How to write setup.py to include a Git repository as a dependency

I&#39;m building a new Docker image based on the standard Ubuntu 14.04 image. 

Here&#39;s my *Dockerfile*:

    FROM ubuntu:14.04
    RUN apt-get update -y
    RUN apt-get install -y nginx git python-setuptools python-dev
    RUN easy_install pip
    ADD . /code
    WORKDIR /code
    RUN pip install -r requirements.txt # only &#39;django&#39; for now
    ENV projectname myproject
    EXPOSE 80 8000
    WORKDIR ${projectname}
    CMD [&#39;python&#39;, &#39;manage.py&#39;, &#39;runserver&#39;, &#39;0.0.0.0:80&#39;]

When I try to run this image, I get this error...

 

&gt;    /bin/sh: 1: [python,: not found

But if I open a shell when running the image, running `python` opens the interactive prompt as expected. 

Why can&#39;t I invoke `python` through `CMD` in the Dockerfile?

Docker image error: &quot;/bin/sh: 1: [python,: not found&quot;

I am trying to install the pip package PIL. However the install doesn&#39;t work throwing the following error.

    Could not find a version that satisfies the requirement pil (from xhtml2pdf==0.0.4-&gt;-r virtualenv-reqs.txt (line 16)) (from versions: )
      Some externally hosted files were ignored as access to them may be unreliable (use --allow-external pil to allow).
    No matching distribution found for pil (from xhtml2pdf==0.0.4-&gt;-r virtualenv-reqs.txt (line 16))

The install does work when I have an older version of pip, but with the current version of pip `7.1.2` I am not able to download the package. I am using the following command to install the pip packages

    pip install --timeout=1000 -i http://pypi.ksjc.sh.colo/simple --trusted-host pypi.ksjc.sh.colo -r virtualenv-reqs.txt

What is the issue with this. I thought it might be an SSL issue which is why I added the `--trusted-host` flag. Is there any way to the `--allow-external` flag to be used with the `virtualenv-reqs` file.

pip install PIL fails

Following is my file *2015_09_14_051851_create_orders_table.php*.
And I want to change `$table-&gt;integer(&#39;category_id&#39;);` as a string with new migration.


    &lt;?php
    
    use Illuminate\Database\Schema\Blueprint;
    use Illuminate\Database\Migrations\Migration;
    
    class CreateOrdersTable extends Migration {
    
    	/**
    	 * Run the migrations.
    	 *
    	 * @return void
    	 */
    	public function up()
    	{
    		Schema::create(&#39;orders&#39;, function(Blueprint $table)
    		{
    			$table-&gt;increments(&#39;id&#39;);
    			$table-&gt;string(&#39;num&#39;);
    			$table-&gt;integer(&#39;user_id&#39;);
    
    			$table-&gt;text(&#39;store_name&#39;);
    			$table-&gt;integer(&#39;store_name_publication&#39;);
    
    			$table-&gt;string(&#39;postal_code&#39;, 255);
    			$table-&gt;string(&#39;phone_number&#39;, 255);
    
    			$table-&gt;text(&#39;title&#39;);
    			$table-&gt;text(&#39;description&#39;);
    
    			$table-&gt;string(&#39;list_image_filename1&#39;, 255);
    			$table-&gt;string(&#39;list_image_filename2&#39;, 255)-&gt;nullable();
    			$table-&gt;string(&#39;list_image_filename3&#39;, 255)-&gt;nullable();
    			$table-&gt;string(&#39;list_image_filename4&#39;, 255)-&gt;nullable();
    			$table-&gt;string(&#39;list_image_filename5&#39;, 255)-&gt;nullable();
    
    			$table-&gt;integer(&#39;term&#39;);
    
    			$table-&gt;datetime(&#39;state0_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state1_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state2_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state3_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state4_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state5_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state6_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state7_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state8_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state9_at&#39;)-&gt;nullable();
    			$table-&gt;datetime(&#39;state10_at&#39;)-&gt;nullable();
    
    			$table-&gt;integer(&#39;category_id&#39;);
    			$table-&gt;integer(&#39;target_customer_sex&#39;);
    			$table-&gt;integer(&#39;target_customer_age&#39;);
    
    			$table-&gt;integer(&#39;payment_order&#39;);
    			$table-&gt;integer(&#39;num_comment&#39;);
    			$table-&gt;integer(&#39;num_view&#39;);
    			$table-&gt;string(&#39;num_pop&#39;);
    
    			$table-&gt;integer(&#39;money&#39;);
    			$table-&gt;integer(&#39;point&#39;);
    
    			$table-&gt;datetime(&#39;closed_at&#39;);
    			$table-&gt;timestamps();
    			$table-&gt;softDeletes();
    		});
    	}
    
    	/**
    	 * Reverse the migrations.
    	 *
    	 * @return void
    	 */
    	public function down()
    	{
    		Schema::drop(&#39;orders&#39;);
    	}
    
    }

Laravel migration table field&#39;s type change

When running laravel migrations, I am facing a small inconvenience. I use Laravel 5.1.

Since there are a lot of tables with many relationships, it is probably impossible that I rename the migration files so they run in the correct order, so no foreign key constraint is violated. This was what I did once in the past, and it was very inpractical.

What I&#39;m doing now is defining each migration like this:

    class CreateSomeTable extends Migration
    {
        public function up()
        {
            DB::statement(&#39;SET FOREIGN_KEY_CHECKS=0;&#39;);
            // my table definitions go here
            DB::statement(&#39;SET FOREIGN_KEY_CHECKS=1;&#39;);
        }

        public function down()
        {
            DB::statement(&#39;SET FOREIGN_KEY_CHECKS=0;&#39;);
            // drop table
            DB::statement(&#39;SET FOREIGN_KEY_CHECKS=1;&#39;);
        }
    }

The problem with this is that it&#39;s tedious to write and it clutters up the code.

I&#39;ve also thought about creating two dummy migration files, whose only purpose would be to enable and disable the foreign key checks, and I would name them in such a way that they would run at the beginning and the end of each migration.

If there is an elegant solution, would it be possible to apply it to the seeding process as well, since this tends to be a problem there as well.

This is obviously a very improvised solution, and I am asking if there is a better way of doing it. Is there some `beforeMigrate` and `afterMigrate` methods that I can override or something along those lines?

And if not, how do you go about doing it?

Any insights would be appreciated, I dislike all the options I have stated.

Laravel migrations nice way of disabling foreign key checks

Using Mac OS X and Homestead 2.2.1 with Laravel 5.2.

In terminal (within homestead in my project folder) I can do php artisan to see all the available commands. When I try to run php artisan migrate I get a connection error:  
`  SQLSTATE[HY000] [2002] Connection refused  `

&lt;hr&gt;

I have setup a Laravel project with these **.env** settings  

    DB_HOST=127.0.0.1
    DB_DATABASE=tcv
    DB_USERNAME=homestead
    DB_PASSWORD=secret

I have also tried *localhost* for DB_HOST and *root* for DB_USERNAME and DB_PASSWORD. And all possible variations of these put together!  
  
&lt;hr&gt;

In Sequel Pro (db management application) I CAN connect with these settings

    Host       127.0.0.1
    Username   homestead
    Password   secret
    Database   tcv
    Port       33060
But this database is obviously empty, because I cant migrate to it from terminal ...

As far as I can make out it is a configuration issue, since I can connect to it with Sequel Pro. But I have honestly no freaking idea what is setup wrong.

Thanks for the help !!


**EDIT**  
For some reason I get the same `SQLSTATE[HY000] [2002] Connection refused` error when moving my project to MAMP and running php artisan migrate.  
Now I am completely lost  ... 


SQLSTATE[HY000] [2002] Connection refused within Laravel homestead

I have a table with a default value already assigned. For an example we can look at the following:

    Schema::create(&#39;users&#39;, function (Blueprint $table) {
				$table-&gt;increments(&#39;id&#39;)-&gt;unsigned();
				$table-&gt;integer(&#39;active&#39;)-&gt;default(1);
			});

I now want to change my default value on the active field. I am expecting to do something like this:

    if (Schema::hasTable(&#39;users&#39;)) {
			Schema::table(&#39;users&#39;, function (Blueprint $table) {
				if (Schema::hasColumn(&#39;users&#39;, &#39;active&#39;)) {
					$table-&gt;integer(&#39;active&#39;)-&gt;default(0);
				}
			});
		}

But of course it tells me the column is already there. How can I simply update the default value of column x without dropping the column?

Laravel migrations change default value of column

I have a `uuid` field (not a primary key). The generated migration is:

    from __future__ import unicode_literals
    
    from django.db import migrations, models
    import uuid
    
    
    class Migration(migrations.Migration):
    
        dependencies = [
            ....
        ]
    
        operations = [
            ...
            migrations.AddField(
                model_name=&#39;device&#39;,
                name=&#39;uuid&#39;,
                field=models.UUIDField(default=uuid.uuid4, unique=True),
            ),
            ...
        ]

But when doing `python manage.py migrate` it is crashing with:

&gt; django.db.utils.IntegrityError: could not create unique index
&gt; &quot;restaurants_device_uuid_key&quot; DETAIL:  Key
&gt; (uuid)=(f3858ded-b8e0-4ac0-8436-8a61b10efc73) is duplicated.

Strangely enough, the problem does not seem to occur with primary keys (which are maybe created by the database, and not internally by django?)

How can I add a uuid field, and make sure that migrations work?

Django migration with uuid field generates duplicated values

I was trying to create migrations within an existing app using the makemigrations command but it outputs &quot;No changes detected&quot;.

Usually I create new apps using the `startapp` command but did not use it for this app when I created it.

After debugging, I found that it is not creating migration because the `migrations` package/folder is missing from an app. 

Would it be better if it creates the folder if it is not there or am I missing something?

Django - makemigrations - No changes detected

In Django&#39;s migrations code, there&#39;s a `squashmigrations` command which: &quot;Squashes the migrations for `app_label` up to and including `migration_name` down into fewer migrations, if possible.&quot;

So, if you want to squash, say, the first 5 migrations, this will help.

What&#39;s the best way to squash starting with a particular `migration_name`?

In a project I&#39;m currently working on, we&#39;ve added 5-10 new migration files as we&#39;ve added new features. We&#39;ll deploy the whole project at once and it looks like running these individually will take too long. I&#39;d like to squash all the migrations for this project into a single migration and test the time to run that.

How to squash recent Django migrations?

I&#39;ve been a user of Django for about 2 years now and there is a feature I have always been afraid of using : _**faking migrations**_.

I&#39;ve looked pretty much everywhere and the most information I can get is from the [documentation][1] where it states that:

**--fake**

&gt; Tells Django to mark the migrations as having been applied or
&gt; unapplied, but without actually running the SQL to change your
&gt; database schema.
&gt; 
&gt; This is intended for advanced users to manipulate the current
&gt; migration state directly if they’re manually applying changes; be
&gt; warned that using --fake runs the risk of putting the migration state
&gt; table into a state where manual recovery will be needed to make
&gt; migrations run correctly.

**--fake-initial**

&gt; Allows Django to skip an app’s initial migration if all database
&gt; tables with the names of all models created by all CreateModel
&gt; operations in that migration already exist. This option is intended
&gt; for use when first running migrations against a database that
&gt; preexisted the use of migrations. This option does not, however, check
&gt; for matching database schema beyond matching table names and so is
&gt; only safe to use if you are confident that your existing schema
&gt; matches what is recorded in your initial migration.

I get the general idea and why one would want to use this feature. But, I don&#39;t understand the part where it says that this is _**intended for advanced users only.**_

Can someone explain what is happening behind the scene and why manual recovery would be needed. 

**NOTE**  

I&#39;m not looking for the exact raw SQL queries that runs when faking a migration. I&#39;m only looking for a general idea of what is happening behind the scene and maybe an example of why faking a migration
 would result in a state where `makemigrations` would not be working correctly.


  [1]: https://docs.djangoproject.com/en/1.11/ref/django-admin/#cmdoption-migrate-fake

Content Type	Original Author	Original Content on Stackoverflow
Question	bgrantdev	View Question on Stackoverflow
Solution 1 - Django	Alasdair	View Answer on Stackoverflow

Django 1.8 Run a specific migration

Django Problem Overview

Django Solutions

Solution 1 - Django

Git: How to remove proxy

Xcode: Is it possible to 'Open Quickly' the right pane of the Assistant Editor?

Attributions