Has anyone tried to setup OSRM so it works in aerodromes. So, instead of routing on roads (highway:trunk, highway:primary, etc..) I can route on a aerodrome:runway, aerodrome:taxiway and aerodrome:parking_position.
According to https://github.com/Project-OSRM/osrm-backend/issues/4814, the WayHandlers file needs to be updated (as well as updating the profile).
However, there isn't any info on what specifically to do. I'm also using the docker images (osrm/osrm-backend) - is the profile/WayHandlers processing done only in the osrm-extract phase?
Related
I'd like to configure the Adobe Cloud Manager production pipeline to invalidate the whole dispatcher cache. What paths do I have to give at the production pipeline dispatcher invalidation configuration to have that done? Is it possible to give a pattern here that matches everything? The page-invalidate description talks about a path-pattern, but doesn't describe what exactly that means.
We work with statfilelevel=2. It seems the .stat files are very important for that, though the description given here is unfortunately not precise enough, not sure I understand that right.
I tried to configure /content as path - that just touches /mnt/var/www/html/.stat (/mnt/var/www/html is the docroot), which seems to apply to nodes like /* but not like /content/* .
If I give /content/oursite, that touches /mnt/var/www/html/content/.stat , too, but that does seem to apply to nodes like /content/oursite or /content/othersite, but not to pages like /content/oursite/about - for which would /mnt/var/www/html/content/oursite/.stat be relevant, if I understand that right.
Do I seriously have to enumerate a page in each site that has a .stat file, or is there a more sensible way to get everything invalidated? After all, a deployment could easily change the HTML of every page if a component has changed.
If you have ACS commons installed then you can try to use this powerful feature
https://adobe-consulting-services.github.io/acs-aem-commons/features/dispatcher-flush-rules/index.html
Following the steps mentioned at mybatis-ignite integration page # mybatis-ignite with Ignite 2.0, i see that the call to the mapper hangs & never returns. This is after working around several other issues like requiring ignite-cache configuration to be placed in IGNITE_HOME/config/default-config.xml which still doesn't get picked up unless i place it in a physical location in the project dir (otherwise i see the error in the log "Initializing the default cache. Consider properly configuring 'config/default-config.xml' instead.") which again also seems to have no effect.
Since the integration seems to have several issues i am not sure if it is still supported..any thoughts from any one who has successfully done this or from the mybatis-ignite team would be great.
Edit: If it helps, i have placed a small self contained project # https://github.com/softwarebrahma/MyBatis-Ignite-L2-cache-POC that can be used to reproduce the issues i have mentioned.
I missed mentioning in the repo..but only the Ports table & schema is used for the purposes of the demo the other tables are not used. What happens is that in the file (github.com/softwarebrahma/MyBatis-Ignite-L2-cache-POC/blob/master/domain/src/main/java/com/brocade/dcm/domain/xml/PostsMapper.xml) if i remove the line "cache type="org.mybatis.caches.ignite.IgniteCacheAdapter" />" then everything will work fine without ignite caching. But the moment i add that line as shown in the uploaded file the mapper method calls just hangs.
I'm interested in using Hot Module Replacement with a newly created React app.
Facebook Incubator's create-react-app uses Webpack 2 which can be configured to support HMR, however in order to do so, one needs to "eject" the create-react-app project.
As the documentation points out, this is a "one way" operation and cannot be reversed.
If I'm to do this, I want to know what I might be giving up. I've been unable to locate any documentation that explains the potential drawbacks of ejecting.
The current configuration allows your project to get updates from create-react-app core team. Once you eject you no longer get this.
It's kind of like pulling in bootstrap css via CDN as opposed to downloading the source code and injecting it directly into your project.
If you want more control over your webpack, there are ways to configure/customize it without ejecting:
https://www.npmjs.com/package/custom-react-scripts
I got a need to integrate various service webUIs into knox gateway.For now ,i use CAS as authentication and got hdfs,hbaseUI,sparkHistoryUI worked fine.I searched google and baidu and found no detailed materials or docs for knox rewrite.xml,so i got problems in integrating new services such as kibana,hue etc.The root cause is that rewrite.xml contains many tags and attr that i just know nothing about.
As a try,i integrate tomcat7.0 ROOT webapp.here is the correspond service.xml and rewrite.xml:
service.xml
rewrite.xml
when i connect the tomcat home page ,everything is ok.but when i clicked the hyper-link "configuration" in the navigation bar. i got infinite number of redirect and finally "ERR_TOO_MANY_REDIRECTS" in the browser.
My question is :1)how to write the rewrite.xml to make this demo work fine.
2)is there any materials or documents about the detail of rewrite tags to share
I will appreciate if any one would help.thanks!
Start with this article: https://cwiki.apache.org/confluence/display/KNOX/Proxying+a+UI+using+Knox
For additional information, you can also see the documentation for service definition files: http://knox.apache.org/books/knox-0-9-1/dev-guide.html#Service+Definition+Files
Hope this is helpful.
I am working with openstack and I want to pin vcpus to pcpus in guest xml. Now, the pinning operation can be done using
virsh vcpupin guestname vcpu pcpu
But I want to do it using python API. I investigated the openstack code and found out that get_guest_config function in libvirt/driver.py is responsible for generation of guest XML file. Now, I tried to put vcpupin attribute here by guest.vcpupin or guest.cputune_vcpupin but none of them is working. Any idea what am I doing wrong? Or is this functionality not available with openstack?
Okay, I figured it out. You need to define the attributes in the nova.virt.config before using them. After defining the attribute, it's working fine.