As long as your app is capable of server-side rendering (SSR) then you can render it in a Sitecore Content Management (CM) role and use Experience Editor (EE) to manage the app and content for the app.
Beyond that, your app can live on a Node.js server somewhere (separate from Sitecore) and consume Layout Service data for rendering.
You are not able to use ...
Have you previously worked with older versions of Sitecore with Docker? If so, you may still have an environment variable floating around with an invalid license.
The getting started project appears to be using the mounted license file strategy. The SITECORE_LICENSE var shouldn't be set, as it is in your screenshot of the id container env vars. Having this ...
Sitecore JSS is using Sitecore MVC pipelines behind the scenes. So caching works the same way as in Sitecore MVC - the output of the rendering (in JSS case it is JSON) is cached in Sitecore's HTML cache (which can be configured per rendering/component). LayoutService indeed returns cached JSON per component.
If by viewEngine you mean this https://jss....
The official Habitat Home JSS example application from Sitecore is available on the Sitecore Omni GitHub: https://github.com/Sitecore/Sitecore.HabitatHome.Omni
This example uses React, but my understanding is that it only has a single mode in the example. It is a complete implementation of a fictional "Habitat Fitness" brand that shows Sitecore ...
This has happened because "Docker Desktop" was not running on my machine. I started "Docker Desktop" and execute the script again. I was able to install a sample project for Sitecore Headless Development.
It really depends on your requirements, what you'd like to achieve and in what timeframe. You should consider that even if 10.1 just released, it will take some time until the project you want to migrate to will be released.
If you plan on having all the sitecore capabilities (like personalization) in your React app you should use the first two options, as ...
The Not Found error can be misleading, it's output for any web exception -- either a 404 or a 500 would trigger it. Double check the logs of your rendering host for any errors.
Also, ensure you have the Experience Editor configured in your Startup.cs:
A WithExperienceEditor configuration in your ConfigureServices
A UseExperienceEditor call in your Configure
There are two types of Item resolver in JSS:
First and which you already implemented:
public class ResolveItem : HttpRequestProcessor
public override void Process(HttpRequestArgs args)
var item = ANY YOUR LOGIC TO GET 404 item.
Context.Item = item;
Are you planning multiple jss app for multiple sites or single jss app for multiple sites?
First scenario, take different builds and keep it in different folders in the proxy server. Then define same number of config (config.js).
Install vhost (npm install vhost) in the proxy server , which can be used to conditionally take config to be executed based on the ...