I am new to mahout and web services related matters.
I have a huge problem concerning the deployment of a simple recommender as a .war file so far and that is because the steps followed by Manning Mahout Book - the only book found so far concerning mahout- refer to an older version of the platform.
I'm currently using mahout 0.9 which, with which i have created a recommender app that successfully runs on my IDE. However when it comes to the deployment of this project i can't find a step-by-step guide to handle my problem.
Does anyone have a clue on how to deploy a 0.5+ mahout project as a .war file?
The .war packaging was removed years ago. There is no means to deploy this that just gives you a web app. It is a library only.
Related
Folks,
We have got an enterprise application which uses Apache Service Mix for deployment. The application consists of various services and each is created as separate Maven project (bundle).During development, we are actually building each service separately and in-order to deploy it,its being put in the deploy folder. Also, we have to uninstall the bundle from the container(say; karaf) and then install it again from the console to bring the new changes in effect. This is fine during the development phase.
Now we want to deploy the code to an UAT environment (Amazon EC2) for the client to do the testing. We are now confused about how to deploy the bundles to the remote environment. Do we have a standard approach for CI using Jenkins(or some other tool) to automate the build and deploy process , so that someone who has no knowledge about the bundles(SMX) can deploy the code. We are using Github for source code management.
We have searched a lot in this regard and couldn't find any resources which provide some leads/hints on this.
Any help/tips is highly appreciated. If you need more info, I can give more details.
~Ragesh
We do have exactly similar setup and we use the Jenkins to build and let the Sysadmin to copy the bundles to one server and then he enables the rsync to rest of the servers.
Remember, always deploy the dependent bundle first and then remaining ..
Since we have this dependency ,we can't go automating this process.
I have existing MEAN stack application. I found more tutorials, but I cannot find anything about deploying existing app to Docker. Is this possible?
As long as you can get the sources of your project on your deployment platform (the Ubuntu server), you can then follow the guide "Dockerizing a Node.js web app".
It shows how to create a simple web application in Node.js, then build a Docker image for that application, and lastly run the image as a container.
You can see a more complete example at Semaphore.
Can anyone help me with squiz matrix migration.? How to find out squiz database in the running server? There is no relevant docs explaining the same.
You can find the database details for the running Squiz Matrix system by looking in data/private/conf/db.inc.
Squiz Matrix includes a script to generate a backup tarball. Details here:
https://manuals.matrix.squizsuite.net/server-administrator/chapters/backup-script
Your biggest issue will be making sure you've got all the prerequisites installed on the destination. There's another script to help you with that:
https://manuals.matrix.squizsuite.net/server-administrator/chapters/system-management-scripts#check_requirements.php
can some one help me. I want to setup a internal repository for maven. For this i wanted to use Apache Archiva and i'm new to both maven and archiva. My question is what is the exact difference b/w standalone and web archiva installations (i found these 2 ways in archiva documentation).
My intention is to create internal repository to be used by all developers. Every one should get dependencies from there. I have to install archiva in a server with in our organization(LAN). What is the preferable for my situation?
I found steps to install in both ways, but they are little confused as i am new to archiva. Could some one please explain me clearly?
Operating System : Windows
Maven : 3.0.5
Archiva : 1.3.6
Thanks in advance.
The standalone distribution is more easy to install.
The wrapper will restart your instance in case of issues.
The important part is to separate content from installation see http://archiva.apache.org/docs/1.4-M3/adminguide/standalone.html section "Separating the base from the installation"
I just began the process of setting up a new Mac as a Rails development machine, but the thought occurred to me: do I have to do all this again from scratch or can I somehow copy/clone my development environment from my existing machine (also a Mac).
Could I, for example, clone my machine using SuperDuper? Or are there any other tools to make the process of developing from more than one machine less agonizing than manually re-installing databases, Ruby, Rails, etc?
Thanks in advance for any ideas.
The rails framework itself is designed to be highly portable, especially version 3 ( with the introduction of a tool called bundler ), it lets you package all of your code and dependencies very easily which makes redeploying elsewhere simple.
Also you could look into using a tool such as RVM for managing ruby installations, RVM makes it very easy to deploy new versions of ruby into any environment.
http://rvm.beginrescueend.com/
And bundler:
http://gembundler.com/
The whole ethos of Ruby and Rails is based around portability and transparency. Once you start developing with it you start to see how easy it is to redeploy your app to other environments.
If you use a distributed version control system like git, you'll be able to pull down a copy of your application to any machine connected to the web.
Capistrano is also something you might want to look at, its a deployment tool and if you couple it with a version control tool such as git, you have a very powerful combination for pushing updates/changes to your deployed application
You can use Carbon Copy Cloner (http://www.bombich.com/) to copy your HD to another, which you can boot from. Also, if you use TimeMachine on another drive/network drive, then you can restore another machine from the backup.