Aye - 1.3 - one of the best features along with Doctrine 1.2... :)
Pre 1.3 we used a bash script for stand alone installs and we use Chef
(http://wiki.opscode.com/display/chef/Home) for managed installs.
The only extra thing the bash script does is bootstrap the SF install
itself.
Chef is a
That's nice ... 1.3 eh?
Thanks for the info :)
On Fri, Oct 9, 2009 at 3:58 AM, david wrote:
>
> The current installer option pretty much allows all that now very simply
> via the installer and a terminal window.
> Unless you're thinking of something along the lines of a web installer or
> have
Generic doesn't mean it will cater for all situation. If it can cater
for even 50% of all projects, it will be a very successful generic
tool.
On Fri, Oct 9, 2009 at 3:54 AM, Gareth McCumskey wrote:
> To answer your comments:
>
> - symfony project:permissions sets all correct permissions
> - The
The current installer option pretty much allows all that now very simply
via the installer and a terminal window.
Unless you're thinking of something along the lines of a web installer or
have some other scenario in mind.
You just need to supplement things with a bootstrap.sh script that:
->
To answer your comments:
- symfony project:permissions sets all correct permissions
- There is a symfony script check_configuration.php as a part of the library
that can be run to check that all required dependencies are met.
- symfony configure:database allows you to change connection settings fo
A generic installer would be something like:
- System checks environment requirements, the usual: php version,
apache version, mod rewrite, gd (plugins may add more requirements)
- User enter database name, user, password
- System creates necessary database structures (table, etc, etc)
- System c
No it wouldn't. Wordpress is a CRM system at its heart and thats really all
its there for. symfony is much lower level than that and you cannot have a
generic installer created for it because there are far too many possible
variables to consider and so many different ways you can develop an
applica
> sf provides all the parts to make installers - you just need to glue 'em
> together.
Correct! And it would make it easier to spread Symfony to the mass if
it has a generic installer built in.
I know, I know, what don't I build it myself? I'd like to, but at the
moment I'm pretty stretched out.
Wordpress is an application, Symfony is a framework that you can use to
build applications.
sf provides all the parts to make installers - you just need to glue 'em
together.
On Wed, 07 Oct 2009 00:32:18 +0200, Jake Barnes
wrote:
>
>
>
> On Oct 5, 2:54 am, Eno wrote:
>> On Mon, 5 Oct 200
> One of the big weaknesses of Symfony is that it can not be deployed as
> easily as WordPress. The fact that non-technical people have an easy
> time installing WordPress gives WordPress much of its presence on the
> web scene.
As far as I know symfony is not a blog, and it's made with _techni
Yeah, I'm thinking:
1. Have install.php on web folder and lock it or delete it after
installation is successful
2. Requirements checking if the environment has everything required
(plugins should be able to add requirement check too)
3. Let end user enters database information (like in Wordpress)
On Oct 5, 7:26 am, Tom Boutell wrote:
> This is true, but if you deploy with svn don't forget:
>
> RewriteRule (\.svn)/(.*?) - [F,L]
>
> In your .htaccess. You don't want people snooping in the .svn folders.
You can "svn export" and none of the .svn folders will be exported.
>
> On Oc
On Oct 5, 2:54 am, Eno wrote:
> On Mon, 5 Oct 2009, Sid Bachtiar wrote:
> > I was trying to look something more for non-developer.
>
> > Let's say I developed a website then when I give the source code to my
> > client (who isn't computer illiterate, but is not familiar with
> > Symfony); at th
svn export "repPath" should generate the structure without the .svn
control folders/files.
With 1.3 we have the installer option with generate:project - while it
will require a rethink on how we deploy - could be more flexible/useful.
It should be a more reliable approach - you'll be working
By default when we checkout from SVN the permissions don't allow access to
anything. Running symfony project:permissions sets permissions correctly for
everything thats needed, including leaving .svn folders inaccessible except
for the user that checked out (root in our case), so that .htaccess opt
This is true, but if you deploy with svn don't forget:
RewriteRule (\.svn)/(.*?) - [F,L]
In your .htaccess. You don't want people snooping in the .svn folders.
On Oct 5, 3:06 am, Gareth McCumskey wrote:
> First, in your batches directory for your symfony write a batch script (in
> PHP even if
First, in your batches directory for your symfony write a batch script (in
PHP even if you want) that will run all the necessary symfony commands
needed, like "symfony cc" etc. Then make sure its all committed to SVN. I
have found deploying to a server easier to do with SVN rather than rsync
which
Of course not. I'm talking about someone technical, who knows how to
install the like of Wordpress, and other popular PHP, but not familiar
with Symfony, nor want/need to learn development in Symfony.
On Mon, Oct 5, 2009 at 7:54 PM, Eno wrote:
>
> On Mon, 5 Oct 2009, Sid Bachtiar wrote:
>
>> I w
On Mon, 5 Oct 2009, Sid Bachtiar wrote:
> I was trying to look something more for non-developer.
>
> Let's say I developed a website then when I give the source code to my
> client (who isn't computer illiterate, but is not familiar with
> Symfony); at the moment I'll have to teach them a lot of
I was trying to look something more for non-developer.
Let's say I developed a website then when I give the source code to my
client (who isn't computer illiterate, but is not familiar with
Symfony); at the moment I'll have to teach them a lot of things on how
to install/deploy, symfony commands
On Mon, 5 Oct 2009, Sid Bachtiar wrote:
> I'm wondering if there is a documentation for non-developer (e.g.:
> system admin) on how to install a website developed in Symfony.
Its in the usual place:
http://www.symfony-project.org/book/1_2/16-Application-Management-Tools#chapter_16_deploying_app
21 matches
Mail list logo
