angusfretwell / craftsman Goto Github PK

• Add license Craft agreement to the generator
• Download Craft from http://buildwithcraft.com/latest.zip?accept_license=yes
• Extract only the app folder, bundle config, etc. into the generator

Not very useful... also having .ssh in Dropbox causes a lot of permissions issues.

Add a file which contains a list of all deployment URLs; any of these environments should able to be specified with the --env parameter.

The file should also specify a default environment, and each environment should be labelled as either a production or development environment.

As per https://www.vagrantup.com/blog/feature-preview-vagrant-1-6-docker-dev-environments.html

Make the generator less opinionated and allow it to be used with non-Dokku deployment environments.

1. Create file with module structure
2. Link from _layout.html

Suggestions:

• Inspector
• Contact Form
• Truncate
• Active
• Email field
• LinkIt
• Wordcount
• Simple Sitemap
• Smartmap
• GroupBy

http://progrium.viewdocs.io/dokku/application-deployment

Was keen to use this as we're also using Craft and Dokku. Seem to be running into an issue when running yo craftsman

events.js:141
      throw er; // Unhandled 'error' event
      ^

Error: You must provide a `message` parameter
    at Prompt.throwParamError (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/lib/prompts/base.js:88:9)
    at Prompt (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/lib/prompts/base.js:44:10)
    at new Prompt (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/lib/prompts/input.js:25:15)
    at PromptUI.fetchAnswer (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/lib/ui/prompt.js:92:16)
    at /usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:4599:20
    at tryCatcher (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:567:29)
    at InnerObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:4806:43)
    at InnerObserver.tryCatcher (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:567:29)
    at AutoDetachObserverPrototype.next (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:5274:51)
    at AutoDetachObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/usr/local/lib/node_modules/yo/node_modules/yeoman-environment/node_modules/inquirer/node_modules/rx/dist/rx.js:1710:35)

I've tried to update some of the versions in package.json and have also manually added babel eslint babel-eslint to the npm install -g list.

Any ideas?

Some installable script (shell is probably fine; should be totally portable with zero dependencies) that will take a single argument (PROJECT_NAME):

craftsman new $PROJECT_NAME

The script should:

1. Clone the latest release of Craftsman to a directory based on PROJECT_NAME
2. Add a hostfile entry for PROJECT_NAME.app
3. Replace values in the Craftsman.yaml file based on PROJECT_NAME
4. Echo out next steps (i.e. run vagrant up) and a link to the Craftsman documentation

1. Select object, component, etc.
2. Create file with header, etc.
3. Link file from main.scss

Should allow for selection of modules to install https://github.com/inuitcss

Backup and timestamp remote databases to a persisted /backups directory in the repository.

• Introduction
• Installation & setup
• Gulp usage
• Vagrant usage
• Custom provisioning (after.sh)
• Craftsman.yaml configuration
• Dotenv configuration
• SCSS usage
• ES2015/Browserify usage
• Front-end library integration (jQuery, Bootstrap)
• Deployment (Capistrano, Heroku)
• Contributing

Reduces friction in getting a new developer up-and-running on a project; ideally vagrant up should be the only command needed to be run after cloning a repository in order to have a functioning development environment.

Default

• title
• lede (Text)
• featuredImage (Asset)
• body (Rich Text)
• bodyMatrix (Matrix)
  • body
    • body (Rich Text)
    • image (Asset)
    • postion (position (L + R)
  • images
    • images (Assets)
    • position (Position)
    • gallery (Lightswitch)
  • pullQuote
    • quote (Text)
    • citation (Text)
  • sectionHeading
    • heading (Text)
    • lede (Text)

SEO

• siteDescription
• siteKeywords
• siteImage

Settings

• googleAnalyticsUA

Contact

• contactName
• contactShortName
• contactAddress
• contactPhone
• contactEmail
• contactSocial
  • facebook
  • twitter
  • instagram
  • pinterest
  • foursquare
  • linkedin
  • youtube
  • vimeo
  • flickr

SEO

• seoTitle
• seoDescription
• seoKeywords
• seoImage
• seoType
• seoRobots

Not doing so is a pain for development as things like flexbox does't work.

I got the following error:

Craft\Exception
E-mail error: Could not instantiate mail function

/var/www/craft/app/services/EmailService.php(475)

if ($errorMessage)
466             {
467                 // Fire an 'onSendEmailError' event
468                 $this->onSendEmailError(new Event($this, array(
469                     'user' => $user,
470                     'emailModel' => $emailModel,
471                     'variables' => $variables,
472                     'error' => $errorMessage,
473                 )));
474 
475                 throw new Exception(Craft::t('Email error: {error}', array('error' => $errorMessage)));
476             }
477 

Craft_Exception.pdf

This means that developers can forego having Gulp installed globally on their host machine, if they so choose.

• app.json
• Procfile
• Add PHP platform requirements to composer.json