tamtam-proxy-frontend
v0.3.2
Published
TamTam Proxy Frontend
Downloads
20
Readme
TamTam Proxy Frontend
Folders
/html/
: Working directory Non build html templates/build/
: Folder where html will be build for development/dist/
: Folder for distribution (minifying etc)
Grunt
grunt
: Start with prompts (questions) to help you with the right deployment optionsgrunt server
: Build your templates to thebuild/
folder with a local server with livereload and watchers (this wil be automatically done when you runyo tamtam
)grunt dist
: Build and minify your project to thedist/
folder for distribution to production servergrunt dist:server
: Build and minify your project to thedist/
folder for distribution to production server with a local server with livereload and watchers
Adding templates
Edit index.js
to export an appropriately named render function for your new
template. Then edit the locals
object in Gruntfile.js
to contain default
variables for your new template. The name of the export in index.js
and the
key used in the locals
object should be the same for Grunt to build it properly.
Deploying
- Decide what the new SemVer version should be.
- Increment the "patch" version if you are deploying a tweak or fix (
x.x.+1
). - Increment the "minor" version if you are deploying a new feature (
x.+1.0
). - Increment the "major" version if you are deploying backwards incompatible changes (
+1.0.0
).
- Use
git flow release start x.x.x
to create a release candidate branch. - Bump the version by editing (or using
npm version
) and comittingpackage.json
. - Test the release candidate branch with the product owner and commit any bugfixes.
- Make sure you've built your assets (
grunt dist
). - Use
git flow release finish x.x.x
to merge to master and tag the release. - Use
git checkout x.x.x
to load the staged version. - Use
npm publish
to publish this new version to the Node Package Manager. - Use
git checkout develop
to continue development.