For consistency, I'd like to see paste.ini follow the same route as mediagoblin.ini. That is, I'd like GMG to make a version-controlled paste.example.ini that gets cp --no-clobbered to paste.ini in Makefile.in. Once this has been done, paste.ini should be added to .gitignore.

--- a/.gitignore
+++ b/.gitignore
@@ -28,6 +28,7 @@
 *.egg/
 /env
 /mediagoblin.ini
+/paste.ini
 /node_modules/

--- a/Makefile.in
+++ b/Makefile.in
@@ -101,12 +101,16 @@ endif
 extlib:
        ./devtools/update_extlib.sh
 
-develop: $(maybe_venv_dep) i18n mediagoblin.ini
+develop: $(maybe_venv_dep) i18n mediagoblin.ini paste.ini
 
 # NEVER clobber a user's mediagoblin.ini once they've defined it
 mediagoblin.ini:
        cp --no-clobber mediagoblin.example.ini mediagoblin.ini
 
-# base-configs: paste.ini mediagoblin.example.ini
+# NEVER clobber a user's paste.ini once they've defined it
+paste.ini:
+       cp --no-clobber paste.example.ini paste.ini
+
+# base-configs: paste.example.ini mediagoblin.example.ini

Somewhere during the install process a file named pip-selfcheck.json was created in my mediagoblin root directory. This should be excluded from the git repository.

I get the following warnings when I run bin/gmg dbupdate in v0.8.0.

(mediagoblin-0.8.0) ~/mediagoblin-0.8.0 $ bin/gmg dbupdate
/usr/lib/python2.7/site-packages/gi/module.py:178: Warning: g_array_append_vals: assertion 'array' failed
  g_type = info.get_g_type()
/usr/lib/python2.7/site-packages/gi/module.py:178: Warning: g_hash_table_lookup: assertion 'hash_table != NULL' failed
  g_type = info.get_g_type()
/usr/lib/python2.7/site-packages/gi/module.py:178: Warning: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed
  g_type = info.get_g_type()

Are these safe to ignore? If so, would it make sense to suppress the warning output?