I've installed Spinnaker on AWS using https://aws.amazon.com/quickstart/architecture/spinnaker/
I've also installed Halyard and updated Spinnaker to 1.5.0
Problem is after I execute
hal config features edit --chaos true
The option for ChaosMonkey doesn't appear in the UI.
I've restarted the service and rebooted the system, I've also tried to manually change the setting in any settings.js files of Deck , but to no avail.
What am I missing ?
There is a guide here for getting chaos monkey up-and-running on GCE with hal. I realize it's not a perfect answer, but maybe it will point out a platform independent step you might have missed?
Related
I used halyard version 0.42.0-20180302093153 and Spinnaker version 1.6.0.
Is there any way that makes me to use hal command: hal deploy apply offline ?
Although there was no ability to do this when you asked your question, there's been work on this since then, under https://github.com/spinnaker/spinnaker/issues/2640. Presumably at some point this will get officially released and the documentation will be updated accordingly, but as of today it appears to be in a "coming, but not here yet" state.
I am using version 4.5.5 of jhipster.
My OS is Linux Mint.
I am using IntelliJ as my IDE.
Everything is working fine in terms of generating the code, building and running the code.
Client
Unfortunately, when I make changes to the client code (html or ts), the changes are not reflected until I recompile the client code completed. To achieve this I do "mvn -Pdev,webpack". It takes quite a while to restart the client and this is really holding me back.
Hot Deploy
What I expect to happen is that I can run "npm start" and when I save a change to a ts or a html file that it will be picked up and the change immediately visible in the browser.
Questions
Any ideas why the client hot deploy is not working ?
Any ideas how I identify where the issue is ?
For example, how do I know what folders are being watched by the hot deploy ?
Thanks a million for you help.
I am sure others have encountered the same issue and will read the answer gladly.
Kind regards,
Fergal.
PS Need any details, simply ask.
Figured it out.
Somebody else had a similar issue with a globally installed instance of webpack.
I installed a local version and the file updates are being detected and recompiled and the app hot deployed. Now working perfectly.
To install a local version webpack.js.org/guides/installation/#local-installation.
I'm getting started with Vagrant and spent some time installing packages, setting up my DB and adding some data to the DB. Now that I have a base working box for my development environment, I would like to share this image with colleagues, that they can use as local VMs.
Is this not possible with vagrant? I just tried vagrant package and then destroyed it and did a vagrant up with my config.vm.box_url pointed to that packaged box location. To my dismay none of my installed packages, or files and configurations were included with my packaged vm.
Am I misunderstanding what vagrant is for or perhaps expecting vagrant to do something it's not designed to do here? If installed packages aren't the purpose of vagrant package, then what use cases is it for?
I've read through the docs and not found answers to these questions there.
Of course I can provision everything, and I'll get there too, but it's not what I'm getting at in this question.
I've since come to the conclusion that vagrant is basically for provisioning. If I need this I can just use virtual-box, but provisioning is a better approach because system packages and application dependencies etc. are a moving target.
Using provisioning allows future provisions to stay up to date and potentially expose incompatibilities.
I'm trying to deploy openMRS v.1.9.2 to a local VM running CentOS & Glassfish 2 for work. Unfortunately, I could not get it to work. Normally, I just download the standalone found at source forge. I just double-click the jar, and I'm good to go.
I normally just SSH into the the VM, so I first tried doing everything through a terminal. Here are the steps I took:
Using wget, retrieve the .zip
Create a dir (I just called it /openmrs), cd into the new directory, and then expand the .zip.
cd into the directory.
At this point, there are two options to start openMRS.
Run the bash script: ./run-on-linux.sh
Run the .JAR: java -jar [insert_jar_name].jar -commandline
When I run the .JAR, I get a stack trace.
When I try to run the bash script, I get another error.
Anyways, I thought I found a potential solution in an openMRS JIRA ticket, but it seems aimed at Glassfish 3, and not Glassfish 2 (which is what I need to use).
I then tried deploying the .WAR via the Glassfish admin UI. I thought it would work, but after going through the steps of selecting a language, whether or not to use demo data, etc. I received this.
Does anyone have experience deploying openMRS to Glassfish 2.1.1? Unfortunately Glassfish 3 doesn't seem to be a realistic option. I would really appreciate any help here. Thanks.
Although it doesn't solve my problem of not being able to successfully deploy openMRS to an instance of Glassfish v.2, I did manage to get myself further by just installing MySQL on the VM. Our work machines are all set up for postgres, so I think should have guessed earlier that not having a MySQL server installation was the problem.
Here is a tutorial I used to install MySQL
So, in college I had a Debian server which used to host a wiki, with mediawiki version 1.9. This server stopped working, and all I have now is its HD. I want to transfer this wiki to a new server, which also runs Debian, but I can't do that with Debian's current stable version of mediawiki, 1.15, because it is not possible to transfer a wiki to another version of mediawii.
So, my idea is to install mediawiki 1.9 on the new server, and then move the wiki. But I am having problems with installing it.
When I go to http://my_hostname/config/index.php, to configure the new wiki, so that I can transfer the other one, I get the following message, and nothing happens:
Checking environment...
Please include all of the lines below when reporting installation problems.
PHP 5.3.3-7+squeeze8 installed"
I really don't have a clue on what is wrong. ANY help would be greatly appreciated!
Like you commented yourself, it would certainly be worth a try to using your existing configuration. The configuration is typically some site preferences and database configuration, so make sure dat your database is setup in the same way as before.
Regarding your configuration problems, maybe php filters away the errors. You can check this by searching for error_reporting in your php.ini.
Just follow the instructions at http://www.mediawiki.org/wiki/Manual:Upgrading. Probably no point in trying to install at MediaWiki 1.9.
You may want to do a clean install of MediaWiki 1.18.1 first just to make sure your system is ready, all dependencies met, etc.