Adam van den Hoven wrote:
The thread on what "standard" plugins do people use as well the "Oops
I deleted the contest2 content" thread got me thinking that it would
be great if someone wrote a tutorial to the effect of, "How to
customize your Radiant command".
Usually I start 90% of my radiant sites by installing the same
extensions; they fit into the way I like to do my work. I am also
inherently lazy so I'd rather put a lot of work in now to prevent
having to do that work over and over again later (I'm told that's not
actually lazy, but I'm not convinced).
Things I would like know how to do:
1) add my own "default" plugins to the created site
2) add my own initial site templates (or force a single initial setup)
3) take production database parameters from the command line (I tend
to follow the same pattern since most of my sites are on dreamhost)
4) save the results in Git (either in my own repository on Dreamhost
or in GitHub)
5) update my custom radiant with the lastest changes (either plugins
or radiant itself) half a year from now. .
I like the idea of making the radiant command do things the way I like
it but (5) is critical if I don't want to fall behind. I also want to
control which "versions" I see of any of these so that I don't get
hosed when version 0.8 comes out and now half my extensions won't work
with 0.7.9
Sorry, dude, but that wouldn't work that way because of the nature of
open source. Not everybody maintains their extensions with up to the
minute changes for Radiant edge, there is no standard way for managing
Radiant projects in git, extensions aren't always in git repos and the
extensions are rarely tagged for which which commits work with which
Radiant versions. Not to mention that some people prefer to use the
multi_site extension for their Radiant projects which brings a whole
other set of complications. Also, Dreamhost hosting for Radiant projects
presents a further set of complications that someone like myself doesn't
encounter because I use Rails Playground instead.
The only way that it might be possible for your suggestion to work is
for RadiantMachine to get up and running and have it become the standard
way of building and hosting Radiant apps. It would need to be kind of
like Wordpress where they have a large number of sites that are hosted
by the mothership, but if people so desire they can build and run a
Wordpress site on their own servers. What do you think, Sean, you're not
busy, eh? Feel like becoming a millionaire? All you need is some venture
capital.
Seriously, though, I think Radiant is just fine as it is. Well, it would
be nice to have those "blogging" features alluded to for 7.1 (?). Then
it would be perfect. Well, it would be great if...
~Nate
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
