SANDBOX_README 3.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100
  1. symfony sandbox
  2. ===============
  3. Thank you for downloading the symfony sandbox. This pre-configured symfony
  4. project will allow you to experiment with the symfony framework immediately,
  5. without any installation or configuration.
  6. Quick start
  7. -----------
  8. The sandbox project will work "out of the box", provided that you extract the
  9. .tgz archive under the root web directory configured for your server (usually
  10. `web/`).
  11. After unpacking the archive, test the sandbox by requesting the following URL:
  12. http://localhost/sf_sandbox/web/
  13. You should see a congratulations page.
  14. Command line
  15. ------------
  16. If you are in the `sf_sandbox/` directory, you can use the command line to do
  17. usual site management operations. For instance, to clear the cache, type:
  18. $ ./symfony.sh clear-cache (*nix)
  19. symfony clear-cache (Windows)
  20. To discover all the available actions of the symfony command line, type:
  21. $ ./symfony.sh -T (*nix)
  22. symfony -T (Windows)
  23. Environments
  24. ------------
  25. The sandbox already contains one application called `frontend`, accessible
  26. through two environments:
  27. - the default environment is the `prod` one, in which the application is fast
  28. but outputs few error messages
  29. - the `dev` environment is slower but gives access to a lot of information
  30. about the current request
  31. To access the `frontend` application in the `dev` environment, type:
  32. http://localhost/sf_sandbox/web/frontend_dev.php/
  33. (don't forget the final /)
  34. Modules
  35. -------
  36. To create a new module `mymodule`, just type in the command line:
  37. $ ./symfony.sh init-module frontend mymodule (*nix)
  38. symfony init-module frontend mymodule (Windows)
  39. To access it, call:
  40. http://localhost/sf_sandbox/web/mymodule
  41. If, at this point, you meet an error, this means that your web server doesn't
  42. support mod_rewrite. Delete the `.htaccess` file from the `web/` directory and
  43. call instead:
  44. http://localhost/sf_sandbox/web/index.php/mymodule
  45. What's in the sandbox?
  46. ----------------------
  47. The sandbox is an empty symfony project where all the required libraries
  48. (symfony, pake, creole, propel and phing) are already included (in the
  49. `sf_sandbox/lib/` directory). It is configured to work without any
  50. configuration if unpacked under the web root, but you can install it anywhere
  51. in your disk. In this case,
  52. - delete the 22nd line of the `sf_sandbox/apps/frontend/config/settings.yml`
  53. (`relative_url_root: /sf_sandbox/web/`)
  54. - create a virtual host in your web server configuration to address the
  55. `sf_sandbox/web` directory
  56. The sandbox is intended for you to practice with symfony in a local computer,
  57. not really to develop complex applications that may end up on the web.
  58. However, the version of symfony shipped with the sandbox is fully functional
  59. and equivalent to the one you can install via PEAR.
  60. Beware that the sandbox is not upgradeable.
  61. Happy symfony!
  62. --------------
  63. Feel free to experiment and try the various techniques described in the
  64. www.symfony-project.com website. All the tutorials can also work in a sandbox.
  65. But in the long run, if you decide to go on with symfony, we advise you to
  66. switch to a PEAR installation, which will guarantee you with the possibility
  67. to use the latest patches and enhancements.
  68. The symfony team
  69. http://www.symfony-project.com/