use bootstrap-3.0.0 - I haven't seen any obvious regression at first sight

[myslice.git] / README

diff --git a/README b/README
index a5d09f1..5ababdb 100644 (file)
--- a/README
+++ b/README
@@ -1,4 +1,4 @@
-his file documents the contents of this module
+This file documents the contents of this module
 
 See the devel/ subdir for more devel-oriented doc.
 
@@ -13,7 +13,6 @@ See the devel/ subdir for more devel-oriented doc.
 * git clone ssh://yourlogin@git.onelab.eu/git/myslice-django.git
 
 * edit myslice/settings.py and
-** change DEVELOPER_ROOT if you didnt clone into ~/git/myslice-django
 ** change the location of your backend API (not yet supported)
 
 * edit myslice/config.py and enter the details of your manifold backend
@@ -22,7 +21,7 @@ See the devel/ subdir for more devel-oriented doc.
 $ manage.py syncdb
 
 * gather static files
-$ make static
+$ ./manage.py collectstatic (formerly, we used make static, which is deprecated)
 
 * run a local server:
 $ manage.py runserver 0.0.0.0:8000
@@ -33,6 +32,9 @@ when you just need to hit ^C yourself when your static files need to be refreshe
 * use it from your browser 
 (See more notes on using the development server below)
 
+* install dependencies
+$ pip install -r path/to/requirements/file.txt
+
 ==================== Status
 
 *** Authentication ***
@@ -92,6 +94,7 @@ Third party tools shipped:
 * datatables
 * spin
 * bootstrap
+* and others are added as we build the system when they become needed
 
 I've tried to keep track of the version I picked and to have an easy upgrade path.
 
@@ -216,3 +219,19 @@ that would reset all-static/ and all-templates/ for you from the other contents
 
 
 
+======== update django database to reflect changes in existing models without any migration system (e.g., south) =========
+
+$python manage.py reset <your_app>
+#Django 1.5.1
+$python manage.py flush
+
+This will update the database tables for your app, but will completely destroy any data that existed in those tables. 
+If the changes you made to your app model do not break your old schema (for instance, you added a new, optional field) 
+you can simply dump the data before and reload it afterwards, like so:
+
+
+$python manage.py dumpdata <your_app> > temp_data.json
+$python manage.py reset <your_app>
+$python manage.py loaddata temp_data.json
+
+If your changes break your old schema this won't work - in which case tools like south or django evolution are great.