[extensions-web: 8/75] Update README and move *.example to etc/

[Jasper St. Pierre <jstpierre src gnome org>]

commit 27ab040e7d82e4cb8b6008c7b638f20e5fed77a1
Author: Jasper St. Pierre <jstpierre mecheye net>
Date:   Mon Sep 12 16:54:40 2011 -0400

    Update README and move *.example to etc/

 README.rst                                         |   41 ++++++++++++++++++++
 etc/sweettooth.httpd.conf.example                  |    9 ++++
 .../sweettooth.wsgi.example                        |    0
 3 files changed, 50 insertions(+), 0 deletions(-)
---
diff --git a/README.rst b/README.rst
index 46f0967..514d249 100644
--- a/README.rst
+++ b/README.rst
@@ -16,6 +16,8 @@ must go through code review and testing.
 Getting Started
 ---------------
 
+You can get started developing the website with::
+
   $ git clone git://github.com/magcius/sweettooth.git
   $ cd sweettooth
   $ virtualenv_ --no-site-packages ./venv
@@ -32,6 +34,45 @@ at /review/.
 .. _virtualenv: http://www.virtualenv.org/
 .. _pip: http://www.pip-installer.org/
 
+Testing with the Shell
+======================
+
+If you have GNOME Shell, and you want to test the installation system, you're
+going to have to hack your system. For security reasons, the browser plugin and
+GNOME Shell both ping the URL https://extensions.gnome.org directly. The
+easiest way to get around this is to make a development environment with the
+proper things that it needs. Since the Django development server doesn't
+natively support SSL connections, we need to install Apache. Follow the
+instructions above to get a proper SweetTooth checkout, and then::
+
+  # Install Apache
+  $ sudo yum install httpd mod_wsgi mod_ssl
+
+  # Generate a self-signed cert
+  $ openssl req -new -x509 -nodes -out extensions.gnome.org.crt -keyfile extensions.gnome.org.key
+  # ... answer questions or just use blanks
+
+  # Install it on your system.
+  $ sudo cp extensions.gnome.org.crt /etc/pki/tls/certs/
+  $ sudo cp --preserve=mode extensions.gnome.org.key /etc/pki/tls/private/
+
+  # The shell will look for a special file called 'extensions.gnome.org.crt',
+  # for development purposes. Otherwise it will use your system's CA bundle.
+  $ mkdir -p ~/.local/share/gnome-shell
+  $ cp extensions.gnome.org.crt ~/.local/share/gnome-shell/
+
+  # Configure Apache.
+  $ cp etc/sweettooth.wsgi.example ./sweettooth.wsgi
+  $ $EDITOR ./sweettooth.wsgi
+
+  $ cp etc/sweettooth.httpd.conf.example ./sweettooth.httpd.conf
+  $ $EDITOR ./sweettooth.httpd.conf
+  $ sudo cp sweettooth.httpd.conf /etc/httpd/conf.d/sweettooth.conf
+
+  # Edit /etc/hosts
+  $ sudo tee -a /etc/hosts <<< 'extensions.gnome.org 127.0.0.1'
+
+
 Requirements
 ------------
 
diff --git a/etc/sweettooth.httpd.conf.example b/etc/sweettooth.httpd.conf.example
new file mode 100644
index 0000000..8fe9f3d
--- /dev/null
+++ b/etc/sweettooth.httpd.conf.example
@@ -0,0 +1,9 @@
+<VirtualHost 127.0.0.1:443>
+        ServerName extensions.gnome.org
+
+        WSGIScriptAlias / /home/jstpierre/Source/sweettooth/sweettooth.wsgi
+
+        SSLEngine on
+        SSLCertificateFile    /etc/pki/tls/certs/extensions.gnome.org.crt
+        SSLCertificateKeyFile /etc/pki/tls/private/extensions.gnome.org.key
+</VirtualHost>
diff --git a/sweettooth.wsgi.example b/etc/sweettooth.wsgi.example
similarity index 100%
rename from sweettooth.wsgi.example
rename to etc/sweettooth.wsgi.example