node.js : Use slapos stack

software/kvm/software.cfg

@@ -15,7 +15,6 @@ extends =
   ../../component/dash/buildout.cfg
   ../../component/lxml-python/buildout.cfg
   ../../stack/nodejs.cfg
-  ../../stack/shacache-client.cfg
 
 develop =
   ${:parts-directory}/websockify
@@ -34,31 +33,8 @@ parts =
   dcron
   logrotate
 
-find-links +=
-  http://www.nexedi.org/static/packages/source/slapos.buildout/
-
 versions = versions
 
-# Use only quite well working sites.
-allow-hosts =
-  *.nexedi.org
-  *.python.org
-  *.sourceforge.net
-  alastairs-place.net
-  dist.repoze.org
-  effbot.org
-  github.com
-  peak.telecommunity.com
-  psutil.googlecode.com
-  www.dabeaz.com
-  www.owlfish.com
-  launchpad.net
-
-# XXX: Workaround of SlapOS limitation
-# Unzippig of eggs is required, as SlapOS do not yet provide nicely working
-# development / fast switching environment for whole software
-unzip = true
-
 #XXX-Cedric : Currently, one can only access to KVM using noVNC.
 #             Ideally one should be able to access KVM by using either NoVNC or VNC.
 #             Problem is : no native crypto support in web browsers. So we have to disable ssl

stack/nodejs.cfg

 [buildout]
 extends =
   ../component/nodejs/buildout.cfg
-  ../stack/shacache-client.cfg
+  ../stack/slapos.cfg
 
 versions = versions
 
-find-links +=
-    http://www.nexedi.org/static/packages/source/slapos.buildout/
-
-# Use only quite well working sites.
-allow-hosts =
-  *.nexedi.org
-  *.python.org
-  *.sourceforge.net
-  alastairs-place.net
-  dist.repoze.org
-  effbot.org
-  github.com
-  peak.telecommunity.com
-  psutil.googlecode.com
-  www.dabeaz.com
-
 parts =
   eggs
   nodejs