Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit2af84eb

Browse files
frnejaviereguiluz
authored andcommitted
Style / grammar fixes for the deployment chapter
1 parentc56f912 commit2af84eb

File tree

3 files changed

+53
-14
lines changed

3 files changed

+53
-14
lines changed

‎cookbook/deployment/azure-website.rst‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -6,14 +6,14 @@ Deploying to Microsoft Azure Website Cloud
66

77
This step by step cookbook describes how to deploy a small Symfony web
88
application to the Microsoft Azure Website cloud platform. It will explain how
9-
tosetup a new Azure website including configuring the right PHP version and
9+
toset up a new Azure website including configuring the right PHP version and
1010
global environment variables. The document also shows how to you can leverage
1111
Git and Composer to deploy your Symfony application to the cloud.
1212

1313
Setting up the Azure Website
1414
----------------------------
1515

16-
Tosetupa new Microsoft Azure Website, first `signup with Azure`_ or sign in
16+
Toset upa new Microsoft Azure Website, first `sign up with Azure`_ or sign in
1717
with your credentials. Once you're connected to your `Azure Portal`_ interface,
1818
scroll down to the bottom and select the **New** panel. On this panel, click
1919
**Web Site** and choose **Custom Create**:
@@ -41,7 +41,7 @@ next step.
4141
Step 2: New MySQL Database
4242
~~~~~~~~~~~~~~~~~~~~~~~~~~
4343

44-
On this step, you will be prompted tosetup your MySQL database storage with a
44+
On this step, you will be prompted toset up your MySQL database storage with a
4545
database name and a region. The MySQL database storage is provided by Microsoft
4646
in partnership with ClearDB. Choose the same region you selected for the hosting
4747
plan configuration in the previous step.
@@ -114,7 +114,7 @@ the web server.
114114
Choosing a more recent PHP version can greatly improve runtime performance.
115115
PHP 5.5 ships with a new built-in PHP accelerator called OPCache that
116116
replaces APC. On an Azure Website, OPCache is already enabled and there
117-
is no need to install andsetup APC.
117+
is no need to install andset up APC.
118118

119119
The following screenshot shows the output of a:phpfunction:`phpinfo` script
120120
run from an Azure Website to verify that PHP 5.5 is running with
@@ -171,7 +171,7 @@ this file just needs to be moved into the custom website extension directory.
171171
longer be necessary.
172172

173173
To get the ``php_intl.dll`` file under your ``site/wwwroot`` directory, simply
174-
access the online **Kudu** tool by browsing to the followingurl:
174+
access the online **Kudu** tool by browsing to the followingURL:
175175

176176
..code-block::text
177177
@@ -342,7 +342,7 @@ credentials, CSRF token protection, etc. These parameters come from the
342342
..image::/images/cookbook/deployment/azure-website/step-16.png
343343
:alt:Configuring Symfony global parameters
344344

345-
The most important thing in this cookbook is to correctlysetup your database
345+
The most important thing in this cookbook is to correctlyset up your database
346346
settings. You can get your MySQL database settings on the right sidebar of the
347347
**Azure Website Dashboard** panel. Simply click on the
348348
**View Connection Strings** link to make them appear in a pop-in.
@@ -395,7 +395,7 @@ Symfony application is more complex than a basic Symfony Standard Edition, you
395395
may have additional commands to execute for setup (see:doc:`/cookbook/deployment/tools`).
396396

397397
Make sure that your application is running by browsing the ``app.php`` front
398-
controller with your web browser and the followingurl:
398+
controller with your web browser and the followingURL:
399399

400400
..code-block::bash
401401
@@ -408,7 +408,7 @@ Configure the Web Server
408408
~~~~~~~~~~~~~~~~~~~~~~~~
409409

410410
At this point, the Symfony application has been deployed and works perfectly on
411-
the Azure Website. However, the ``web`` folder is still part of theurl, which
411+
the Azure Website. However, the ``web`` folder is still part of theURL, which
412412
you definitely don't want. But don't worry! You can easily configure the web
413413
server to point to the ``web`` folder and remove the ``web`` in the URL (and
414414
guarantee that nobody can access files outside of the ``web`` directory.)
@@ -453,9 +453,9 @@ application, configure it with the following content:
453453
</configuration>
454454
455455
As you can see, the latest rule ``RewriteRequestsToPublic`` is responsible for
456-
rewriting anyurls to the ``web/app.php`` front controller which allows you to
456+
rewriting anyURLs to the ``web/app.php`` front controller which allows you to
457457
skip the ``web/`` folder in the URL. The first rule called ``BlockAccessToPublic``
458-
matches allurl patterns that contain the ``web/`` folder and serves a
458+
matches allURL patterns that contain the ``web/`` folder and serves a
459459
``403 Forbidden`` HTTP response instead. This example is based on Benjamin
460460
Eberlei's sample you can find on GitHub in the `SymfonyAzureEdition`_ bundle.
461461

@@ -471,7 +471,7 @@ and executed on a Microsoft IIS web server. The process is simple and easy
471471
to implement. And as a bonus, Microsoft is continuing to reduce the number
472472
of steps needed so that deployment becomes even easier.
473473

474-
.. _`signup with Azure`:https://signup.live.com/signup.aspx
474+
.. _`sign up with Azure`:https://signup.live.com/signup.aspx
475475
.. _`Azure Portal`:https://manage.windowsazure.com
476476
.. _`PHP MSDN documentation`:http://blogs.msdn.com/b/silverlining/archive/2012/07/10/configuring-php-in-windows-azure-websites-with-user-ini-files.aspx
477477
.. _`git-scm.com`:http://git-scm.com/download

‎cookbook/deployment/heroku.rst‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ published by Heroku.
1111
Setting up
1212
----------
1313

14-
Tosetupa new Heroku website, first `signup with Heroku`_ or sign in
14+
Toset upa new Heroku website, first `sign up with Heroku`_ or sign in
1515
with your credentials. Then download and install the `Heroku Toolbelt`_ on your
1616
local computer.
1717

@@ -133,7 +133,7 @@ create the ``Procfile`` file and to add it to the repository:
133133
2) Set the Environment to prod
134134
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
135135

136-
During adeploy, Heroku runs ``composer install --no-dev`` to install all of the
136+
During adeployment, Heroku runs ``composer install --no-dev`` to install all the
137137
dependencies your application requires. However, typical `post-install-commands`_
138138
in ``composer.json``, e.g. to install assets or clear (or pre-warm) caches, run
139139
using Symfony's ``dev`` environment by default.
@@ -325,7 +325,7 @@ This is also very useful to build assets on the production system, e.g. with Ass
325325
`Grunt`_ or `gulp`_.
326326

327327
.. _`the original article`:https://devcenter.heroku.com/articles/getting-started-with-symfony2
328-
.. _`signup with Heroku`:https://signup.heroku.com/signup/dc
328+
.. _`sign up with Heroku`:https://signup.heroku.com/signup/dc
329329
.. _`Heroku Toolbelt`:https://devcenter.heroku.com/articles/getting-started-with-php#local-workstation-setup
330330
.. _`getting Started with PHP on Heroku`:https://devcenter.heroku.com/articles/getting-started-with-php
331331
.. _`ephemeral file system`:https://devcenter.heroku.com/articles/dynos#ephemeral-filesystem

‎cookbook/deployment/tools.rst‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -189,6 +189,45 @@ Don't forget that deploying your application also involves updating any dependen
189189
(typically via Composer), migrating your database, clearing your cache and
190190
other potential things like pushing assets to a CDN (see `Common Post-Deployment Tasks`_).
191191

192+
The Tools
193+
---------
194+
195+
`Capifony`_:
196+
197+
This tool provides a specialized set of tools on top of Capistrano, tailored
198+
specifically to symfony and Symfony projects.
199+
200+
`sf2debpkg`_:
201+
202+
This tool helps you build a native Debian package for your Symfony project.
203+
204+
`Magallanes`_:
205+
206+
This Capistrano-like deployment tool is built in PHP, and may be easier
207+
for PHP developers to extend for their needs.
208+
209+
Bundles:
210+
211+
There are many `bundles that add deployment features`_ directly into your
212+
Symfony console.
213+
214+
Basic scripting:
215+
216+
You can of course use shell, `Ant`_, or any other build tool to script
217+
the deploying of your project.
218+
219+
Platform as a Service Providers:
220+
221+
PaaS is a relatively new way to deploy your application. Typically, a PaaS
222+
will use a single configuration file in your project's root directory to
223+
determine how to build an environment on the fly that supports your software.
224+
One provider with confirmed Symfony support is `PagodaBox`_.
225+
226+
..tip::
227+
228+
Looking for more? Talk to the community on the `Symfony IRC channel`_ #symfony
229+
(on freenode) for more information.
230+
192231
.. _`Capifony`:http://capifony.org/
193232
.. _`Capistrano`:http://capistranorb.com/
194233
.. _`sf2debpkg`:https://github.com/liip/sf2debpkg

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp