Thanks Matt for your reply, I successfully completed the web application on my laptop. Now I am pushing it on server. What are the changes i need to do so that my application runs smoothly on server.
Thanks On May 4, 2:48 pm, Matt Robinson <m...@lazycat.org> wrote: > On 4 May 2011, at 21:55, Laxmi wrote: > > > I recently completed the web application on my laptop. Now I need to > > push it on production server. > [...] > > but my question is how can i create instances of my application like > > development, staging, production. > > My advice is to set up Apache VHosts on either subdomains > (staging.example.com) or different ports (:8080). Then secure your staging > somehow (e.g. by limiting the IP range with Apache's deny/allow rules[1], or > setting up HTTP Basic auth[2]). > > Your development instance should be on your own machine or somewhere that > isn't accessible to the live server, so you don't have to worry about people > breaking your app while you're still testing and looking for holes. > > Setting up VHosts is pretty easy on modern linux distributions like Ubuntu or > Debian[3] - define the site in a file in /etc/apache2/sites-available then > make a symbolic link to it in sites-enabled, run "apache2ctl configtest" then > restart if it checks out. For a little more performance, you can move the > RewriteRules from your symfony project's web/.htaccess into the VHost > definition, too. > > If your production host doesn't give you access to Apache configuration, then > things get a bit more tricky. You could own a separate account for staging, > maybe. My kind of snobbish opinion is that your production server should at > least be a VPS or a dedicated server so you have some control, but I > understand that you might have other things to do than be a linux sysadmin :) > > I use the "./symfony -t project:deploy" command[4] to push out changes, which > is just a wrapper for rsync. To have your staging and production instances on > the same server, but using different databases, I recommend putting > /config/databases.yml (and maybe /apps/frontend/config/app.yml) into your > /config/rsync_exclude.txt file, and uploading them manually the first time, > then they can have different configuration for each instance. > > -- Matt > > [1]http://www.cyberciti.biz/faq/apache-restrict-access-based-on-ip-addre... > [2]http://httpd.apache.org/docs/2.0/howto/auth.html > [3]http://www.debian-administration.org/articles/412 > [4]http://www.symfony-project.org/jobeet/1_4/Doctrine/en/22#chapter_22_s... -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
