I need some clear steps to install ngrinder,A Performance testing tool.
Even though I followed the steps in the following link, I am not able to setup the environment in my machine.
Visit Here for installation steps.
http://www.cubrid.org/wiki_ngrinder/entry/ngrinder-devzone
So, Please help me to sort out this problem to setup the environment to do the performance testing using ngrinder.
Related
docdokuplm
Hi !
Just checking out your PLM, looks great! I followed your instructions:
https://github.com/docdoku/docdoku-plm/wiki/Installation-Guide
I used the nightly build.
After uploading the ear file and then using http://localhost:8080 I see the Payara server page. Was there something else I need todo or where do I start to troubleshoot? Thoughts?
Thank you!
The page displayed at 8080 is the default landing page. If you have deployed the DocDokuPLM application and configured the settings detailed within the instructions, you can open the application through Payara Server. Go to Applications -> DocDokuPLM -> Launch, and you'll get a series of links which should help you troubleshoot.
If you can't see any, run through the installation procedure again to ensure that you haven't missed a step - it seems like there's a few steps which must be configured exactly correctly for the application to work.
According to this GitHub issue, this seems like a bug with DocDokuPLM. As with most software, nightly builds are inherently risky. Looking at the source, though, it seems that the code changes fairly rarely, so you might try with the previous version of Payara Server (173), though the stack traces in the GitHub issue don't look to me like an issue with Payara.
The backend server and the UI are two separated components.
If you want to install the User Interface you have to go there :
https://github.com/docdoku/docdoku-web-front
The project which you have deployed is just for backend,inorder to interact with UI just clone the web-client from this repo https://github.com/docdoku/docdoku-web-front and in command prompt use this command npm run dev then you can use this project, make sure the port number which is mentioned in app/webapp.properties.json of web-client project is same as you have given in server-config.
Read https://github.com/docdoku/docdoku-web-front/wiki/Development-Guide for more details
I want to build web ui for StrongLoop. It would let a user build and deploy process with that UI like StrongLoop Arc.
There are simple node applications(Web Services) without created with StrongLoop tools. Need to deploy these applications via web ui. Solution in my mind is some server-side processes, listed steps below:
Upload zip folder(node application) to server
Extract zip and build to tar.gz by shell command (slc build) through node.js child_process API
Deploy tar.gz file to relevant StrongLoop host by shell command(slc deploy..) through API which is mentioned on previous step.
I wonder is there any alternative way to deploy node application(without created with StrongLoop tools) to StrongLoop host via web ui using some StrongLoop API?
I have looked API could not find specific solution.
What you require is a CDP (Continuous delivery pipeline) setup, there seem to be many ways in which you can achieve this (easiest way is using Codeship or similar platforms), but if you want to know how it works it requires a bit of orchestration tools to help you. To describe the steps I'll be using the following tools:
Docker (what is docker?)
Ansible (Use Cases and How it works?)
Jenkins (What is it and Why to use it?)
"There are many other combination of tools that you can look at, but this should give you an idea"
Now that we have the tools, I'll try to describe the deployment pipeline with a very basic use-case.
Step I "Ideally" - Creating a docker image for your nodejs application.
What generally everyone suggests is that you create a docker image of your application. Then save this image on docker-hub. How this will help you is that, now your nodejs application is contained inside a docker image which makes it independent of the Host and can be deployed anywhere you want.
To create this image all you need to do is create a Dockerfile, which is described in the in the link I've shared.
Step II "Ideally" - Creating an Ansible playbook to mimic the setup steps of your application.
Ansible playbooks are basically used to automate every manual process that you would need to do in order to setup-deploy-run your application. This decreases the need to run even trivial tasks like "slc build".
Step III "Ideally" - This is where we get to the UI stuff
By using Jenkins, you are given a UI which will help you configure tasks that can be combined with Github hooks and trigger the deployment as soon as you make a commit. This is explained in more details in the link shared.
So to summarize, This is what goes on at back to some extent, in order to automate the build and deployment of your application using UI. I hope this serves as a good starting point to achieve your requirements, and also in case you want skip these steps in the start, you could always go with Codeship or similar other tools to help you with the steps that you've mentioned.
Trying to setup an app with JHipster. Every tutorials I follow I have errors and failures.
Whatever options I select I got errors on my project.
Following the JHipster MiniBook procedure I have error like this on my IDE at start:
http://imgur.com/bWdek5W
And when I follow the directives to page 24 and try to run
./gradlew bootRun
I got a build failed: http://imgur.com/jFeJEQ6
I don't know what I'm doing wrong. I follow step by step the book, or other tutorials. Something must be wrong configured on my computer.
Any idea ?
Just looking at the error messages which are shown:
On the first screenshot you have configured your IDE to use Java 1.6 source code. JHipster is using Java 1.8, so the lambda expressions (which are new in Java 1.8) cannot be compiled.
On the second screenshot you have configured JHipster to use an external database. But you have not followed the documentation, which tells you to configure that external database in your application-dev.yml configuration file (and to start the database, of course!)
I am using grunt to build my application, I want to use different configurations when the application is being run from built version and when I run it as a developer using simply nw.
Is there any such option which helps distinguish this behaviour?
You will need to set the desired configuration IN the processed source. There are many ways to accomplish this. Check out this blog post for some ideas http://addyosmani.com/blog/environment-specific-builds-with-grunt-gulp-or-broccoli/
I am trying to configure browser-perf for measuring browser performance metrics. I am able to run it via commandline using
browser-perf --selenium=http://localhost:4444/wd/hub http://yourwebsite.com
However, I want to configure the Node Module API for browser-perf.
Following is the issue:
1. I am not able to find a command to execute the node API browser-perf tests.
2. Also, where do I place the call to browserPerf() - In conf OR in spec ??
If someone can provide steps for the Node API setup, that would be really helpful!
PS: I found protractor-perf conf.js command is used to protractor-perf tests. Just not able to find something similar for browser-perf!
The below link gives all the necessary steps to setup and execute browser-perf tests
https://gist.github.com/axemclion/9594795