Hosted Trial - FAQ
After you have been through the two introductory tutorials, you are ready to explore further and create your own Proof-of-Concept project for your company or organization.
This FAQ page gives you the key principles you need to work effectively with your hosted magnolia-trials.com instance.
Multiple projects side-by-side
In the Hello Magnolia - Hosted Headless you learned how to create a new light module where you could package all configuration for a new project.
|
It is a good practice to put each project in its own module. However there are a few things to keep in mind when you take this approach. |
Gotcha: Definitions are not scoped to one module
Definitions (such as content types, apps & endpoints) supplied in a light module are available by name anywhere in Magnolia. (With the exception of templates and dialogs.)
In general this is handy and makes them easy to work with, but it could also interfere in a project. For example if two modules bring in a `cars' content type, then when you reference `cars' it will be unpredictable which one will be resolved.
Definitions App
The Definitions app is a good way to troubleshoot any problems, and also a great place to explore what is configured on the system.
In the Magnolia UI, type Definitions in the Find Bar at the top, and open the app. Here you can see all of the registered definitions on the entire system, whether they came from your project or the system itself. Use the filters in the column headers to slice & dice, such as entering the name of your module, basic-trips-lm or spa-website-lm in the Module column header.
Switch to the Problems tab, to see any problems in any modules. Minor problems don’t break the definitions, but can indicate when something is misconfigured.
|
Importing Content
Sometimes you may want to import content into a system, for example a tutorial or demo project may supply sample content, or you may want to export content from one Magnolia instance, and import it in another one. This is done via xml (sometimes yaml) text files, and are referred to as bootstrap files.
A convenient way to import content to your hosted trial instance is to place bootstrap files in your repository in the
/content-importer/author directory, and then git push the changes. The Content Importer module system will detect the files and then create Tasks which are visible in the header of the Magnolia UI. You just need to approve those tasks and the content will be imported on your Author instance. To publish the content to your Public instance, just go the appropriate apps and use the Publish action.
|
Another approach to importing is to go to the app of interest, and directly use the Import action in that app. (Use the Export action to create bootstrap files.)
Removing a project
You should keep the provisioned demo project installed as you go through the tutorials. When you are done with the first tutorials, you can develop your project adjacent to the demo project. But given the issues described above, you may eventually wish to remove the pre-installed spa-website-demo from your server.
When you do decide to remove it, here is how:
Remove Content
The content is installed in the database.
Remove Configuration
Removing the files from the light-modules directory will remove their impact on the system configuration. You could remove the entire spa-website-demo directory. You can move the files elsewhere, or simply delete them.
Once you have removed the files, perform a git commit and push.
This will remove the configured contentTypes, apps, restEndpoints, templates and so forth.
The `App Launcher' will show the apps until you logout and login again.
Learn More
You’re off to a great start with Magnolia. You have reached the end of the tailored learning path for the magnolia-trials.com service. You are ready to explore the further available resources.
Magnolia Academy & Training
Magnolia Academy is our online learning solution for Magnolia users. It comprises a collection of video-based online courses and is packed with exercises and knowledge checkpoints. Solution codes are shared through Git.
Check out our instructor-led trainings too.
Install locally for best devX
These tutorials include installing Magnolia on your local computer. While this setup takes a little longer, you’ll be rewarded with a great developer experience. Every change you make will be picked up instantly by your local computer.
Concepts
Before proceeding with more tutorials, consider getting the big picture with 1 or more of the 6 concept pages.
| This takes you to the Headless section of the documentation site. |
Next Tutorials
While these tutorials are not tailored to the magnolia-trials.com service, you can still deploy them to your hosted server if you would like, using the above information from this FAQ.
Hello Magnolia SPA
It’s headless, but with a great authoring experience. Enable authors to edit your React, VUE or Angular apps in a visual What-You-See-Is-What-You-Get fashion.
This is the tutorial for a minimal SPA Editing project. Great starter project.
| This takes you to the Headless section of the documentation site. |