@@ -189,45 +189,6 @@ Don't forget that deploying your application also involves updating any dependen
189
189
(typically via Composer), migrating your database, clearing your cache and
190
190
other potential things like pushing assets to a CDN (see `Common Post-Deployment Tasks `_).
191
191
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
-
231
192
.. _`Capifony` : http://capifony.org/
232
193
.. _`Capistrano` : http://capistranorb.com/
233
194
.. _`sf2debpkg` : https://github.com/liip/sf2debpkg
0 commit comments