Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Since you updated your question, I can give you some relevant info.</p> <p>As you now know, you have a cascading configuration system in symfony which allows different parameters for for example your database connection (among many other things) for your dev and prod environment.</p> <p>As to deployment, symfony comes with a task that utilizes rsync to deploy. In general you do not need to tweak it much, it will by default not deploy any "dev" front controller, so it suits most basic needs. Note that even if the deployment script should exclude the dev front controllers from deploying at all, e ven if you would deploy them, they by default have a small security check which only allows access from localhost. If you need to exclude other files from deployment, you can edit config/rsync_exclude.txt</p> <p>Detailed info in deploying here: <a href="http://www.symfony-project.org/gentle-introduction/1_4/en/16-Application-Management-Tools#chapter_16_deploying_applications" rel="noreferrer">http://www.symfony-project.org/gentle-introduction/1_4/en/16-Application-Management-Tools#chapter_16_deploying_applications</a></p> <p>A big note though, is that this deployment script does NOT handle database deployment. You should do that manually. If you need to deploy database changes to an existing database, you could also do that manual, or look into Doctrine Migrations (assuming you use Doctrine).</p> <p><strong>Update:</strong> you can have a single frontend controller (index.php) for different apps and/or environments. You can either check the hostname or other things, but the cleanest solution I found and employ is setting Apache environment variables. In my Vhost config I'll do:</p> <pre><code>&lt;VirtualHost *:80&gt; Servername www.myproject.dev ... SetEnv SYMFONY_APP frontend SetEnv SYMFONY_ENV dev SetEnv SYMFONY_DEBUG 1 &lt;/VirtualHost&gt; </code></pre> <p>Note that ofcourse I'll have a separate Vhost for every single app/env combination. You shouldn't be deploying vhost configs, so normally you'll only need to set this up once on each host. My modified index.php looks like this:</p> <pre><code>&lt;?php require_once dirname(__FILE__) . '/../config/ProjectConfiguration.class.php'; $app = isset($_SERVER['SYMFONY_APP']) ? $_SERVER['SYMFONY_APP'] : 'frontend'; $env = isset($_SERVER['SYMFONY_ENV']) ? $_SERVER['SYMFONY_ENV'] : 'prod'; $debug = isset($_SERVER['SYMFONY_DEBUG']) ? $_SERVER['SYMFONY_DEBUG'] : false; $configuration = ProjectConfiguration::getApplicationConfiguration($app, $env, $debug); sfContext::createInstance($configuration)-&gt;dispatch(); </code></pre> <p>With this setup, I can just remove frontend_dev.php and any other frontend controllers apart from index.php from my repository.</p>
    singulars
    1. This table or related slice is empty.
    1. POSymfony 1.4 best practice production & development configuration
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGerry
    1. USGerry
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSymfony 1.4 best practice production & development configuration
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks I guess issue I have is to how to manage enviroments with git in this case. This person illustrates a possible hack (http://www.4pmp.com/2010/10/programmatically-set-environment-for-symfony-project/). Really tough I think the best option is to write some conditions in index.php that looks at the url and set the enviroment based on that e.g. localhost or example.com/mysymfonyproject_dev is set to "dev" and example.com/mysymfonyproject is set to "live" different domains for dev and live might work out better of course than just folders in domain.
      singulars
      1. PO
      1. USDerek Organ
    2. COI don't see why you need a hack in Git, or do you have multiple dev environments with different configs. That said, you can indeed change index.php and I personally use Apache environment variables to set app/environment, see my updated response.
      singulars
      1. PO
      1. USGerry
    3. COI really like the way you use the apache environment variables. Thanks will defo use something like that I think. And yes I do have multiple development areas. Local mac for me, local windows for other developer, staging server and live. thanks for the suggestion.
      singulars
      1. PO
      1. USDerek Organ
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload