Skip to content

Latest commit

 

History

History
88 lines (53 loc) · 3.22 KB

README.md

File metadata and controls

88 lines (53 loc) · 3.22 KB
Raw

MuraNuxtJSDecoupled

Initial Startup

First you need to start Mura up:

git clone https://github.com/blueriver/MuraNuxtJSDecoupled.git
cd MuraNuxtJSDecoupled
git checkout master
cd mura
docker-compose up

Then go to http://localhost:8888 to initialize Mura's install then login with the default (admin/admin) and edit the default site's settings:

  • Domain= The domain of the remote site that the the content will be served on. (localhost)
  • Is Remote = true
  • Remote Context = The directory structure off of the remote site's web root that the site lives (Leave Empty)
  • Remote Port = The port of the remote site (3000)
  • Resource Domain = The domain that Mura will use the access resource like css and js scripts that are dynamically loaded. (localhost)

Second you need to start Angular up:

Then in terminal go to the ./NuxtJS directory within the project root:

cd {project_root}/nuxtjs
npm install

Then start the NuxtJS service

npm run dev

You can now visit the site at http://localhost:3000

And finally go to your Mura admin (http://localhost:8888/admin) and reload Mura one more to and it will see the mura.config.json from the ./angular directory.

Key Points of Integration with Mura

The intergration is entirely done with Mura.js installed as an npm within the and project while running Mura's official docker container.

Mura Version

You must use Mura 7.1.328 of higher

NPM

https://www.npmjs.com/package/mura.js

Mura.js documentation

https://docs.getmura.com/v7-1/mura-developers/mura-rendering/murajs/

Docker Image

https://hub.docker.com/r/blueriver/muracms/

Theming

With this use case Mura modules, templates and content type includes are now located outside of Mura within the client. The those examples have not yet been added to this project. Just know that when rendering a content node you can target specific content types in the client just like you could in traditional Mura theme development.

Configuring Mura Remotely

There is a mura.config.json file that the Mura service reads in when loading to get what it needs to know from the client.

https://github.com/blueriver/MuraNuxtJSDecoupled/blob/master/NuxtJS/static/mura.config.json

You tell Mura about it as an environment variable

https://github.com/blueriver/MuraNuxtJSDecoupled/blob/master/mura/docker-compose.yml#L22

Here you can see an example of registering a module created from within NuxtJS and registered via the mura.config.json and mura.config.js

https://github.com/blueriver/MuraNuxtJSDecoupled/blob/master/nuxtjs/mura.config.js#L7-L13

https://github.com/blueriver/MuraNuxtJSDecoupled/blob/master/nuxtjs/static/mura.config.json#L8-L13

Mura ORM Assembler and Scaffolder

An important aspect of Mura 7.1 and this new way of working with Mura is using the Mura ORM Assembler and Scaffolder to create your own custom entities. You can then use Mura.js to seamlessly access them within your client. It works the same way as working with normal content and feeds.

https://docs.getmura.com/v7-1/mura-developers/mura-beans-objects/custom-objects/mura-orm/mura-orm-assembler-scaffolder/

Mura Module Configurator Markup Conventions

https://docs.getmura.com/v7-1/mura-ui-markup-conventions/custom-module-display-object-configurators/