1. Ian Bicking
  2. silverlining

Commits

Ian Bicking  committed 0748ec8

update ubuntu version references to lucid

  • Participants
  • Parent commits f800e95
  • Branches default

Comments (0)

Files changed (5)

File docs/design.txt

View file
  • Ignore whitespace
 Ubuntu
 ======
 
-This system is based on Ubuntu.  Jaunty, Karmic, in the future no
-doubt other updates will come around.  For the most part the
-Jaunty/Karmic distinction is temporary (I suppose it should just be
-upgraded to Karmic), and supporting multiple revisions isn't ideal or
-desired.
+This system is based on Ubuntu.
 
-Support for other Linux distributions is not desired.  No one has
+Support for other Linux distributions is not desired.  Few people have
 asked about this so far, so I'm hoping this will be a
 non-controversial choice.  Many parts of the system expose Ubuntu
 (especially the ``packages`` configuration).  The config files are
 be a finely tuned machine; complex, but refined.  That takes a lot of
 iterating, and I need a community of people iterating with me to get
 there.
-

File docs/index.txt

View file
  • Ignore whitespace
 
 The server is setup thusly:
 
-* Ubuntu Jaunty (Karmic seems to work too).
+* Ubuntu Lucid 10.04 LTS
 
 * Python 2.6.
 
     in future.
 
 ``silver setup-node``:
-    This takes a bare Ubuntu Jaunty system and sets it up.
+    This takes a bare Ubuntu Lucid system and sets it up.

File docs/porting.txt

View file
  • Ignore whitespace
 is done *outside* the application).
 
 To test an actual deployment you need a server to deploy to.  Silver
-Lining can deploy to any dedicated Ubuntu Karmic machine that has been
+Lining can deploy to any dedicated Ubuntu Lucid machine that has been
 configured by Silver Lining (using ``silver setup-node``), but the
 cloud makes getting a testing server very easy and quite cheap (when
 testing, you can allocate a server just for a few hours for testing

File docs/providers.txt

View file
  • Ignore whitespace
 
 You don't *need* to use commands like ``silver create-node`` to make
 use of Silver Lining.  If you have a machine with a fresh install of
-Ubuntu Jaunty (or Karmic) then you can use ``silver setup-node`` to
+Ubuntu Lucid then you can use ``silver setup-node`` to
 configure the machine and ``silver update`` to deploy applications.
 It's harder to test things without the ability to create and destroy
 servers on demand, but the basic infrastructure is not really

File docs/zope-quickstart.txt

View file
  • Ignore whitespace
 Because we will have binary eggs that are OS architecture specific, we need to build everything on the same
 type of machine that we are going to deploy to.
 
-Install silverlining on a Rackspace Cloud machine running Ubuntu Karmic 9.10::
+Install silverlining on a Rackspace Cloud machine running Ubuntu Lucid::
 
     $ cd /opt
     $ virtualenv -p python2.6 silverlining
 
     $ ssh-keygen
     Generating public/private rsa key pair.
-    Enter file in which to save the key (/root/.ssh/id_rsa): 
+    Enter file in which to save the key (/root/.ssh/id_rsa):
     Created directory '/root/.ssh'.
-    Enter passphrase (empty for no passphrase): 
-    Enter same passphrase again: 
+    Enter passphrase (empty for no passphrase):
+    Enter same passphrase again:
     Your identification has been saved in /root/.ssh/id_rsa.
     Your public key has been saved in /root/.ssh/id_rsa.pub.
     The key fingerprint is:
     your new Zope instance.
 
     Username: admin
-    Password: 
-    Verify password: 
-    
+    Password:
+    Verify password:
+
 Make a Zope2 admin user
 -----------------------
 
 
     $ cd zope-on-wsgi/etc
     $ mv zope.conf zope.conf.orig
-    
+
 Edit the zope.conf file to look like this::
 
     %define INSTANCE <TODO: find out how to use a relative path>
     instancehome $INSTANCE
 
     effective-user www-mgr
-    
+
     <zodb_db main>
         <filestorage>
           path $INSTANCE/var/Data.fs
         mount-point /temp_folder
         container-class Products.TemporaryFolder.TemporaryContainer
     </zodb_db>
-    
+
 Make sure the www-data user owns the directory
 ----------------------------------------------
 
-If you set the effective-user to "www-data", then you need to make sure that 
+If you set the effective-user to "www-data", then you need to make sure that
 this user has ownership of the directory.
 
     $ chown -R www-data:www-data zope-on-wsgi
 
-    
+
 Make the WSGI configuration
 ---------------------------
 
 And add a password file etc/passwd::
 
     admin:admin
-    
+
 Test it with paster
 -------------------
 
 Set up the WSGI runner
 ----------------------
 
-Edit the zope-on-wsgi/app.ini file to point to the zope2.ini file you just created. 
+Edit the zope-on-wsgi/app.ini file to point to the zope2.ini file you just created.
 Replace the <insert your runner here> with etc/zope2.ini.
 
     [production]
     ## If you always upload this app to a particular hostname, use this:
     #default_host = ...
     packages = python-setuptools
-    
+
 Try serving the app using silverlining
 --------------------------------------
 
 ----------------------
 
     # silver create-node wsgify --setup-node
-    Creating node (image=Ubuntu 9.10 (karmic); size=256 server)
+    Creating node (image=Ubuntu 10.04 LTS (lucid); size=256 server)
     Status 3 at IP 174.143.146.185
     The hostname/ip is not setup in /etc/hosts
     Would you like me to set it up?  [y/n] y
     Setting up authentication on server...
     Using key file:  /root/.ssh/id_rsa.pub
     Warning: Permanently added 'wsgify,174.143.146.185' (RSA) to the list of known hosts.
-    root@wsgify's password: 
+    root@wsgify's password:
     (check your email for the password)
     Updating indexes and setting up rsync
     ...
     Copying files from `/etc/skel' ...
     Restarting apache2 and varnish
-    
+
 Update the server with your app
 -------------------------------