Hi!
Could it be that when using Passenger you'd save a little on the
memory usage by having more common code in betweeen the apps? Anyhow,
with Passenger 2 however even running vendor-Rails shouldn't be a big
sin (from what I read somewhere).
I tried running two gem-based installations
Joe Van Dyk wrote:
Personally, I don't know why you'd want to use a gem for radiant, but
the option is there.
I guess it's might convenient in development!
Any time any of my applications depends on a 3rd party library, I try
to package up that library with my application.
I agree - in
Personally, I don't know why you'd want to use a gem for radiant, but
the option is there.
Any time any of my applications depends on a 3rd party library, I try
to package up that library with my application.
Joe
On Mon, Nov 10, 2008 at 2:19 PM, Simon Rönnqvist <[EMAIL PROTECTED]> wrote:
> OK, s
On 2008/11/10, at 15:19, Simon Rönnqvist wrote:
And is there any easy way to move an installation from/to being a
repo-version to/from an installation pointing to a gem?
From the command line you can use
# go from gem to vendor'd bleeding edge
rake radiant:freeze:edge
# go from gem to vendo
OK, so for what purpose was Radiant made a gem then? :)
And is there any easy way to move an installation from/to being a repo-
version to/from an installation pointing to a gem?
cheers, Simon
On Nov 10, 2008, at 23:32 , Joe Van Dyk wrote:
I'd keep as much as you can in the repository.
I'd keep as much as you can in the repository. What happens if you
need to upgrade Radiant for one of your applications, but need to keep
another application on an older Radiant version? It's no problem if
Radiant (and the rest of the libraries you use) are bundled up with
the application.
Joe
Hi!
I just dug up this old post. :)
I found that I can also install gems in my home-directory at
Dreamhost, I tested installing Radiant that way and it worked. Would
you still recommend cloning from the repo or is using a gem just as
good, what pros and cons do you see?
I'm guessing th
Hi!
Thanks for the tip, this was a really straight forward method to get
everything working... and adding the multi_site extension in the same
way was no hard thing to do either.
So here's the simple version of the tutorial. :)
cheers, Simon
On Oct 8, 2008, at 16:57 , Casper Fabriciu
Casper Fabricius said the following on 08/10/08 09:57 AM:
Hi Simon,
I'd recommend to do a
git clone git://github.com/radiant/radiant.git my_radiant_app
instead. Remember to create a database.yml file and to create the
mysql database on DH.
*sigh*
I had just got my head around SVN when you
Hi Simon,
I'd recommend to do a
git clone git://github.com/radiant/radiant.git my_radiant_app
instead. Remember to create a database.yml file and to create the
mysql database on DH.
Med venlig hilsen / Best regards,
Casper Fabricius
http://casperfabricius.com
On 08/10/2008, at 15:44, Simon
Radiant must be unpacked directly into vendor/radiant, not vendor/gems.
Sean
Simon Rönnqvist wrote:
Hi!
I've been trying to use Radiant unpacked with Dreamhost. But I fail to
get it working, maybe I'm doing something wrong... but I failed to
find any good howto.
I unpacked Radiant into my
Hi!
I've been trying to use Radiant unpacked with Dreamhost. But I fail to
get it working, maybe I'm doing something wrong... but I failed to
find any good howto.
I unpacked Radiant into my Radiant app's vendor/gems/ folder using
"gem unpack radiant".
(I'm not 100% sure where I should p
12 matches
Mail list logo