Contents
How to configure Sitecore in a JSS app?
To configure the Sitecore connection, run jss setup at a command line within your JSS app, and follow the prompts. You will be asked for several pieces of information: ‘Website’ folder: This is the root physical path to the Sitecore instance, used to deploy config files and JS build artifacts.
How can I check if my license is JSS enabled?
To check if your license is a JSS-enabled license, open your license.xml in a text editor and search for Sitecore.JSS – if it’s found, you’re ready to use JSS. Not there? Read on. Recently updated partner license should already have the key that enables JSS.
When to add JSS bindings to IIS Instance?
After adding the host name entry, add it as a binding on your IIS instance as well: If you are planning on deploying multiple JSS applications, you will need to configure different hosts and host name bindings in IIS in order for Sitecore to resolve the proper site.
How to host a JSS app on localhost?
Sitecore docs for the site element don’t specify a way to declare a port. I tried changing the site declaration in my patch file to exclude the hostname attribute. The result my app renders without images when I visit localhost:44001. When I inspect the returned HTML, the URLs to the images are missing the port number.
What are the default options for JSS deploy items?
When run with default options, jss deploy items also runs jss manifest, and jss package. Options for all of these commands may also be passed to deploy items. Content, media, or dictionary items are excluded by default for safety, in case a content editor has changed the data.
Which is the command line interface for JSS?
During JSS development, you will be commonly using scripts provided by the JSS CLI (command line interface). These scripts can be run from within a JSS application at your command line of choice (bash, PowerShell, cmd, etc). These are the main scripts you will be using frequently during JSS development.