I've spent a week trying to understand how Hybris installer works and I thought I could create any type of application with recipes. However my teammate said that those recipes are useless for dev or production setup. But why installer folder is a top folder in Hybris installation? Only for demo?
相关问题
- How to invoke Ant in a Jenkins Groovy Pipeline
- Correct locale for Indonesia( “id_ID” Vs “in_ID” )
- What is recipe in SAP Hybris?
- HYBRIS - How components and slots work in JSP file
- How to get config data from local.properties to im
相关文章
- HYBRIS - How components and slots work in JSP file
- How to get config data from local.properties to im
- hybris - Which Spring Controller is serving my req
- How could I reduce the Hybris server startup time?
- What are the differences between MSI and EXE insta
- Create Custom Action to Start Application and Exit
- Linux Program can't find Shared Library at run
- How can I allow MSI features to be selected in a W
In the Hybris WIKI are two sites that explain this one:
Installing Hybris Using Installer Recipes
Installing SAP Hybris Commerce
But you can also just have a look into the install recipes. There is no big magic behind it. Just browse to:
(for example) and have a look into it. First it sets some properties, than it defines which extensions should be used and at last it install addons on other extensions (normally on the storefront).
Your teammate correct, installer used for creating demo system.