summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-webteam/2011-January/000137.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-webteam/2011-January/000137.html')
-rw-r--r--zarb-ml/mageia-webteam/2011-January/000137.html137
1 files changed, 137 insertions, 0 deletions
diff --git a/zarb-ml/mageia-webteam/2011-January/000137.html b/zarb-ml/mageia-webteam/2011-January/000137.html
new file mode 100644
index 000000000..6fc2fdd3d
--- /dev/null
+++ b/zarb-ml/mageia-webteam/2011-January/000137.html
@@ -0,0 +1,137 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-webteam] Initial hosting requirements for maintainers db
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Initial%20hosting%20requirements%20for%20maintainers%20db&In-Reply-To=%3C1294829551.32187.293.camel%40akroma.ephaone.org%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="000136.html">
+ <LINK REL="Next" HREF="000138.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-webteam] Initial hosting requirements for maintainers db</H1>
+ <B>Michael Scherer</B>
+ <A HREF="mailto:mageia-webteam%40mageia.org?Subject=Re%3A%20%5BMageia-webteam%5D%20Initial%20hosting%20requirements%20for%20maintainers%20db&In-Reply-To=%3C1294829551.32187.293.camel%40akroma.ephaone.org%3E"
+ TITLE="[Mageia-webteam] Initial hosting requirements for maintainers db">misc at zarb.org
+ </A><BR>
+ <I>Wed Jan 12 11:52:31 CET 2011</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="000136.html">[Mageia-webteam] Initial hosting requirements for maintainers db
+</A></li>
+ <LI>Next message: <A HREF="000138.html">[Mageia-webteam] Initial hosting requirements for maintainers db
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#137">[ date ]</a>
+ <a href="thread.html#137">[ thread ]</a>
+ <a href="subject.html#137">[ subject ]</a>
+ <a href="author.html#137">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>Le mercredi 12 janvier 2011 &#224; 11:22 +0100, Romain d'Alverny a &#233;crit :
+&gt;<i> On Wed, Jan 12, 2011 at 11:10, Kosmas Chatzimichalis &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">Kosmas at mach7x.com</A>&gt; wrote:
+</I>&gt;<i> &gt; On 12 January 2011 09:36, Romain d'Alverny &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">rdalverny at gmail.com</A>&gt; wrote:
+</I>&gt;<i> &gt;&gt; On Wed, Jan 12, 2011 at 02:36, Michael Scherer &lt;<A HREF="https://www.mageia.org/mailman/listinfo/mageia-webteam">misc at zarb.org</A>&gt; wrote:
+</I>&gt;<i> &gt;&gt;&gt; Le mardi 11 janvier 2011 &#224; 23:07 +0000, Kosmas Chatzimichalis a &#233;crit :
+</I>&gt;<i> &gt;&gt;&gt;&gt; The initial requirements for installing the maintainers db in the
+</I>&gt;<i> &gt;&gt;&gt;&gt; mageia server are: [...]
+</I>&gt;<i> &gt;&gt;&gt;&gt; 1. RVM (Ruby version manager)
+</I>&gt;<i> &gt;&gt;&gt;
+</I>&gt;<i> &gt;&gt;&gt; From what I know, that would likely mean compiling our own ruby version
+</I>&gt;<i> &gt;&gt;&gt; on the server, using its own separate set of gems. [...]
+</I>&gt;<i> &gt;&gt;
+</I>&gt;<i> &gt;&gt; What's the possible alternative?
+</I>&gt;<i> &gt;
+</I>&gt;<i> &gt; By using RVM, we won't need a chroot environment for gem installation
+</I>&gt;<i> &gt; as installation can be done in a user's account.
+</I>&gt;<i> &gt; Consequent gem installations don't need sudo permission and are
+</I>&gt;<i> &gt; installed on user's account.
+</I>
+You do install a self compiled separate ruby in a separate prefix, with
+a separate set of gems in a different prefix. If the only difference
+with a chroot is that you do not need to use &quot;chroot&quot;, then there isn't
+much difference to me, and then my point was not clear enough.
+
+&gt;<i> Something tells me that misc won't find this a consolation. :-p
+</I>&gt;<i>
+</I>&gt;<i> Misc, if in the end, hosting a rails stack does make things less
+</I>&gt;<i> consistent than with other stacks, we may as well set up a host on a
+</I>&gt;<i> Gandi server and dedicate it (package management and security
+</I>&gt;<i> mgmt-wise to the rails stack).
+</I>
+How would that making it more consistent ?
+Moreover, dedicating a vm just mean one more server to handle, that's
+hardly can be counted as &quot;less work&quot;.
+
+
+&gt;<i> I'm not saying this should be this way but that would be an option to consider.
+</I>
+I do think people do not really understand what I am saying, despite me
+asking to 2 set people to read my mail twice.
+
+Hosting this on alamut ( our shared application server ) or on a gandi
+server is the same, we would a different set of non integrated packages.
+
+Non integrated because that use a totally different system ( ie gem/rvm
+vs rpm/urpmi ) with totally different versions ( ie, defined by coders
+instead of the one agreed when we decided to use the distribution ),
+totally different update mechanism, and with different requirements.
+
+And those gems would need to be taken care like we do for package since
+they are packages. Except we would be on out own. No people to make sure
+they work together ( as upstream developers usually do not care at all,
+ask shikamaru about the gitorious rpm in cooker and some rpm requiring
+older version, and some not ), no people to make sure that security
+update occurs with minimal change ( usually that &quot;let's pack all changes
+together&quot;, which result in more version update than required, with code
+changes ).
+
+
+Another option that I consider would be to use another stack. Nanar
+already told me that he would be able to do it quite fast in catalyst,
+and I consider myself being able to do it in django without much problem
+if I dedicate enough time ( I am quite rusty but for a simple CRUD
+application, it would be quite ok ).
+
+&gt;<i> &gt; Just as a note dreamhost updated all their servers to 3.0.3 and
+</I>&gt;<i> &gt; RubyGems 1.3..6 in a matter of few weeks, and although I don't know if
+</I>&gt;<i> &gt; they had problems, I'm sure that they are security conscious about
+</I>&gt;<i> &gt; their servers as well.
+</I>&gt;<i>
+</I>&gt;<i> There's no question about it. But Dreamhost is a business, moreover, a
+</I>&gt;<i> hosting business so they can dedicate way more people/servers about it
+</I>&gt;<i> than us, at this time.
+</I>
+And well, the equivalent with dreamhost would be you to ask them to keep
+a custom or old version of rails just for you. I am not sure they would
+say &quot;yes&quot;.
+
+--
+Michael Scherer
+
+</PRE>
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="000136.html">[Mageia-webteam] Initial hosting requirements for maintainers db
+</A></li>
+ <LI>Next message: <A HREF="000138.html">[Mageia-webteam] Initial hosting requirements for maintainers db
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#137">[ date ]</a>
+ <a href="thread.html#137">[ thread ]</a>
+ <a href="subject.html#137">[ subject ]</a>
+ <a href="author.html#137">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-webteam">More information about the Mageia-webteam
+mailing list</a><br>
+</body></html>