How to bootstrap this repo in Ember?

[torenware]

I'm trying to figure out what all is needed to get this up to test. I've done the following:

• Pulled master from the boztek / ember-data-drupal repo.
• cd ember-data-drupal
• npm install
• bower install
• ember serve

This is because it doesn't look like simply doing "ember install ember-data-drupal" would install something that would actually run. As is, I get the standard "start here" ember page.

It's possible that the README is not making it clear how this repo relates to actually building an ember app that works with D8 hosted JSON API. A couple of other github repos are mentioned, but it's not clear how the whole thing fits together.

I've used ember a bit, and Drupal 8 a lot, but don't get how to use your repo. What do I need to do in order to do that?

Thanks,
Rob

[torenware]

Got this working. Order is:

• Pull the demo ember front end from https://github.com/boztek/ember-drupal-demo-front.
• Configure the frontend per README, and verify that the rental app loads with its Mirage data.
• Now pull the demo drupal back end from https://github.com/boztek/ember-drupal-demo-cms.
• Configure it per its README, and start the dev drupal server.
• Log into the Drupal server. Try to create some rental content.
  • You'll initially fail, since "Rental Type" is required, but has no items. Cause is a lack of terms in the Rental Type vocabulary.
  • Created a couple of terms.
  • Verify that you can, in fact, now create rental content.
• Now go back to the ember front end command prompt, and enter generate the ember proxy to point to your backend. This will restart the front end.
• Verify that the content you created in Drupal in fact has replaced the 3 Mirage entries.

I'm guessing that it's worth adding some stock terms similar to what's in Mirage would be a good change to the config, and some pointer from the original plugin page to more complete demo instructions. I'll see about creating a PR for this.

Now that I get how to set this up, I'm impressed how nice the demo is. A very nice use of composer and drupal console that works beautifully. Thanks for your efforts on this.

[left23]

This was helpful @torenware. Thanks for clarifying the steps, and confirming everything works.

And thanks @boztek for your work on this.

Just a few notes that may help others, and for posterity sake.

1. Taxonomy terms are content, not config
   From what I know about Drupal content management, we can't add taxonomy terms to config. The vocabularies are config, but terms themselves are content. Afaik, terms will need to be added manually after the site install and config import, as pointed out in @torenware post above.

• I currently can't get the 'type' working, despite adding a few taxonomy terms.

2. The JSONAPI module has been updated since (8.x.1.0), and the name space has changed from /api to /jsonapi.

Example
Old: http://127.0.0.1:8088/api/node/rental?_format=api_json
New: http://127.0.0.1:8088/jsonapi/node/rental

The changes in response to the JSONAPI Drupal module update have been incorporate in this repo already, see #2

The Front-end demo repo uses a older version this addon.
The CMS demo uses an older version of JSONAPI Drupal module.
So when used together, everything works out of the box, but things will start to fail if Drupal modules are updated without updating the Addon.