bezoerb/generator-sf

Yeoman generator that scaffolds out a Symfony PHP app including Browsersync, various CSS preprocessors, jspm, webpack, browserify and Service Worker

generator-sf

This Yeoman generator scaffolds a symfony app with full featured frontend grunt/gulp tooling. Just scaffold your app and you are ready to go.

Installation

First, install Yeoman and generator-sf using npm (we assume you have pre-installed node.js).

Install dependencies

npm install -g yo grunt gulp

To install generator-sf from npm, run:

npm install -g generator-sf

Then generate your new project:

yo sf

Features

• Symfony framework
• Twig templating engine
• Assetic removed
• Browsersync dev/prod server with livereload
• Choose the build tool which fits your needs
  • Gulp
  • Grunt
• Choose the CSS preprocessor which fits your needs
  • Sass
  • Less
  • Stylus
  • or no preprocessor at all
• Choose CSS Framework
  • uikit
  • Bootstrap
  • Foundation
  • inuitcss (sass only)
  • no framework?
• Choose Javascript module loader
  • Webpack (ES6)
  • JSPM + SystemJS (ES6)
  • Browserify (ES6)
• File revving
• Image optimization
• Critical (Extract & Inline Critical-path CSS)
• uncss (Automatically strip off unused css)
• Service Worker
• Organized Gruntfile with load-grunt-config
• Preconfigured testing Stack: Karma, Mocha & Chai
• Phpunit

Things to come

• Feel free to add feature requests ;)

Environments

The browsersync server uses it's own symfony environment to prevent asset loading conflicts with the environment loaded via apache2.

Directory structure

The directory structure is based on the Symfony Best Practices

Dev

• Assets are located in app/Resources/public
• Templates can be found in app/Resources/views

Production

• All production assets are located in the web folder.
• Run grunt build or gulp build to compile, optimize and rev your assets for production.

Changelog

See CHANGELOG.md

License

MIT

Getting To Know Yeoman

• Yeoman has a heart of gold.
• Yeoman is a person with feelings and opinions, but is very easy to work with.
• Yeoman can be too opinionated at times but is easily convinced not to be.
• Feel free to learn more about Yeoman.

License

MIT © Ben Zörb

generator-sf's Issues

Gulp build --env prod skips making production files

gulp build --env prod is not generating main.css or main.js and the php templates are the initial ones, not my modified ones.

Any ideas? I'm on node 6.10 on php 7

app_dev.php works fine, gulp serve works fine

P.S. I'm in a hackathon... I'm working around it by running a production mode php-middleware server.

THANKS!

404 on initial setup

? Would you like to use the Symfony "Standard Edition" distribution 4.1.4 (latest) Yes
? Would you like to enable Git for this project (includes post-merge hook)? No
info Fetching https://github.com/symfony/symfony-standard/archive/v4.1.4.zip ...
info This might take a few moments
events.js:183
throw er; // Unhandled 'error' event
^

HTTPError: Response code 404 (Not Found)
at EventEmitter.ee.on.res (C:\Users\Home\AppData\Roaming\npm\node_modules\generator-sf\node_modules\got\index.js:250:24)
at emitOne (events.js:116:13)
at EventEmitter.emit (events.js:211:7)
at Immediate.setImmediate [as _onImmediate] (C:\Users\Home\AppData\Roaming\npm\node_modules\generator-sf\node_modules\got\index.js:99:8)
at runCallback (timers.js:810:20)
at tryOnImmediate (timers.js:768:5)
at processImmediate [as _immediateCallback] (timers.js:745:5)

Routing Issue with paths with extensions

I have a symfony route that would handle the following url http://localhost:8000/myaction/generated.txt

gulp's server won't handle it and returns
Cannot GET /myaction/generated.txt

Seems to be related to the same issue I had with generator-grunt-symfony Where it would route .json requests
bezoerb/generator-grunt-symfony#205 (comment)

I'm looking into it, not as familiar as I was with grunt... any pointers?

UPDATE:
Culprit is clearly

generator-sf/generators/buildtool/gulp/templates/gulp/helper/utils.js

Line 31 in 37ac37a

if (!/\.\w{2,}$/.test(obj.pathname) || /\.php/.test(obj.pathname)) {

The solution I had used was to give php-proxy-middleware everything but browsersync and then modify app_dev.php to route based on whether a real file existed, similar to a lot of mod_rewrite rules.