I want that instead of the home page https://ibb.co/Xb6VJsy, the product page https://ibb.co/bzL0KnS is displayed, I don't know how to do this.
This is the structure of my current Bundle:
└── Bogota
└── Bundle
└── NewBundle
├── BogotaNewBundle.php
└── Resources
├── config
│ └── oro
│ └── bundles.yml
├── public
│ └── first_theme
│ ├── css
│ │ └── styles.css
│ └── images
│ └── cathedral-of-bogota-pngrepo-com.png
└── views
└── layouts
└── first_theme
├── config
│ └── assets.yml
└── theme.yml
You can change the home page within the Web Catalog Management:
go to Marketing / Web Catalogs
click on "Edit Content Tree" for the chosen web catalog
And change the default content variant for the root tree node. By default, it's set to the "System Page" - "Oro Frontend Root". Set the "System Page Route" to "Oro Product Frontend Prduct Index":
For more details on the web catalog management, see the documentation:
https://doc.oroinc.com/user/concept-guides/content-management/web-catalog/
From the code level, you can achieve the same using the data migration:
https://doc.oroinc.com/backend/entities/fixtures/#data-fixtures
Related
I am testing the loading of modules in webpack. How would you indicate the path of the dependency in an AMD module?
My project has something like this:
├── modules
│ ├── mod1.js
│ ├── mod2.js
│ └── others
│ └── mod3.js
├── public
│ └── bundle.js
├── src
│ └── app
│ └── app.js
└── webpack.config.js
in app.js I import only mod3.js therefore you must compile the three JS (mod1, mod2, mod3) since mod3.js depend on them.
I have a "others" route. Every time I create a folder I have to include the following line in webpack.config.js?
path.resolve(__dirname, 'modules/others'),
Is it not possible to indicate the path of the dependency in the module itself without webpack compiling go to the hard defined in the config?
Thank you
Having a code structure like below which contains documentation at the root level how can I TELL IDEA to import the Code/spark subfolder as a project?
.
├── Code
│ ├── foo
│ │ ├── bar
│ │ └── baz
│ └── spark
│ ├── build.sbt
│ ├── common
│ ├── job1
│ ├── project
│ ├── run_application
│ ├── sbt
│ ├── scalastyle-config.xml
│ └── version.sbt
├── Docs
You need to add Content Root, go to Project Structure settings (Ctrl + Alt + Shift + s), select your module, then on the right panel click Add Content Root and select Docs folder. Then you can select it and mark as part of the Module, for documentation I believe it should be Resources.
Even better: use a proper build tool like gradle and then apply https://docs.gradle.org/current/userguide/composite_builds.html
I use ansible for a while with standalone playbooks and now would like to configure role structure at my environment.
This is folder structure(example, summarised)
├── hosts
├── playbooks
│ ├── project1-staging.yml
│ └── project1-production.yml
├── roles
│ └── project1-compile
│ ├── files
│ │ └── project1.conf
│ ├── handlers
│ │ └── main.yml
│ ├── meta
│ │ └── main.yml
│ ├── tasks
│ │ └── main.yml
│ ├── templates
│ └── vars
│ └── main.yml
│ └── ec2-create
│ ├── handlers
│ │ └── main.yml
│ ├── meta
│ │ └── main.yml
│ ├── tasks
│ │ └── main.yml
│ ├── templates
│ └── vars
│ └── main.yml
│ └── project1-deploy
│ ├── handlers
│ │ └── main.yml
│ ├── meta
│ │ └── main.yml
│ ├── tasks
│ │ └── main.yml
│ ├── templates
│ └── vars
│ └── main.yml
├── vars.yml
It looks straightforward.
I would like to execute project1-staging.yml playbook to create a new staging environment for specific version, like that;
ansible-playbook project1-staging.yml -e 'version=1'
and playbook below;
---
- name: deploy project1 (staging) {{ version }}
hosts: local
connection: local
roles:
#- project1-compile version={{ version }}
- { role: ec2-create, project: project1, count:1 }
- { role: project1-compile, version: {{ version }} }
- { role: project1-deploy, version: {{ version }}, target: {{last_ec2}} }
There are some problem at this structure and also i don't like it.
- Is that proper way?
- how can i use result of ec2-create role, i would like to deploy codes to server which is just created and i don't know id.
- are there another method to pass parameters to roles?
Take a look at Inventory Modules. More specifically add_host module.
Synopsis
Use variables to create new hosts and groups in inventory for use in
later plays of the same playbook. Takes variables so you can define
the new hosts more fully.
Examples
# add host to group 'just_created' with variable foo=42
- add_host: name={{ ip_from_ec2 }} groups=just_created foo=42
# add a host with a non-standard port local to your machines
- add_host: name={{ new_ip }}:{{ new_port }}
# add a host alias that we reach through a tunnel
- add_host: hostname={{ new_ip }}
ansible_ssh_host={{ inventory_hostname }}
ansible_ssh_port={{ new_port }}
I would like to know the right way to change modules loading priorities in Linux. I want to have hdmi and LCD output the most quickly.
For now it take 3 seconds to came, I know it's not delay due to hdmi or TV because the first stuff I see on screen is some lines about mali init (mali is the name of the GPU here).
I use a A10-Olinuxino-Lime board with an homemade rootfs generated using buildroot and a custom Linux made for this kind of processor (linux-sunxi).
The tree of /etc/:
etc/
├── dhcp
│ ├── dhclient.conf
│ └── dhcpd.conf
├── dropbear
├── fstab
├── group
├── hostname
├── hosts
├── init.d
│ ├── rcK
│ ├── rcS
│ ├── S01logging
│ ├── S20urandom
│ ├── S40network
│ ├── S50dropbear
│ ├── S80dhcp-relay
│ ├── S80dhcp-server
│ ├── S80mali
│ └── S99TVOS
├── inittab
├── inittab~
├── inputrc
├── issue
├── ld.so.cache
├── ld.so.conf
├── ld.so.conf.d
├── mtab -> /proc/mounts
├── network
│ ├── if-down.d
│ ├── if-post-down.d
│ ├── if-post-up.d
│ ├── if-pre-down.d
│ ├── if-pre-up.d
│ ├── if-up.d
│ └── interfaces
├── nsswitch.conf
├── os-release
├── passwd
├── profile
├── protocols
├── random-seed
├── resolv.conf -> ../tmp/resolv.conf
├── securetty
├── services
├── shadow
├── ts.conf
└── wpa_supplicant.conf
Do you have any ideas ?
I'd create an /etc/init.d/S00modules script containing a sequence of insmod (or modprobe if your env supports it) lines.
If that doesn't help, then your modules are loaded even earlier,and you'll have to find how and where that happens. I'd first look at /sbin/init or what is used instead.
I'm updating an existing rails 2 app to rails 3, and having some trouble understanding the asset pipeline. I have read through the guide and as I understand it, files in any of the following directories will resolve to /assets:
app/assets
lib/assets
vendor/assets
and you could access them using helpers...i.e.
image_tag('logo.png')
But what I don't understand is how collisions are handled? For example, what if there are the following files:
app/assets/images/logo.png
lib/assets/images/logo.png
If I go to myapp.com/assets/images/logo.png, which file will be returned? I could check for collisions manually within my app, but this becomes a pain point when using gems that rely on the asset pipeline.
Based on what I've found, you can't have duplicate files, as rails will just return the first one found.
This seems like a bit of a design flaw, as a gem may not namespace their own assets
Why not taking advantage of the index manifest and organize your app/assets into decoupled modules? You can then reference to a particular image, image_tag('admin/logo.png'), and get for free your UI codebase organised in a more meaningful way. You could even promote a complex component, such as Single Page Application into it's own module and reuse it from different parts of the app.
Let's say you app is composed out of three modules: the public side, an admin UI and, e.g., a CRM to let your agents track the selling process at your company:
app/assets/
├── coffeescripts
│ ├── admin
│ │ ├── components
│ │ ├── index.coffee
│ │ └── initializers
│ ├── application
│ │ ├── components
│ │ ├── index.sass
│ │ └── initializers
│ └── crm
│ ├── components
│ ├── index.sass
│ └── initializers
├── images
│ ├── admin
│ ├── application
│ └── crm
└── stylesheets
├── admin
│ ├── components
│ └── index.sass
├── application
│ ├── components
│ └── index.sass
└── crm
├── components
└── index.sass
21 directories, 6 files
Don't forget to update your application.rb so they will be precompiled properly:
config.assets.precompile = %w(admin.js application.js crm.js
admin.css application.css crm.css)