how to install ForgeRock Open Identity Stack - openam

I download frstack from
https://github.com/wstrange/frstack#install-the-forgerock-open-identity-stack-ois
After I install Ansible and Vagrant, I don't know how to make it work
Are there any references available?
Thanks

Author of that project here. That is very much a work in progress - so I would not start with that.
Just get a tomcat instance running and deploy OpenAM to it. Once you understand the basics then you can look at an automated deployment using Ansible.

Related

GitLab fails on install and/or reconfigure

For a college assignment I had to configure gitlab on my virtual machine that’s hosted on google cloud engine and is currently running Ubuntu 20.04.
I tried to install gitlab twice but the install fails (first it got stuck for at least 5 minutes on unpacking github-ce (13.10.2-ce.0) then it failed.
Reconfiguring gets me the same message but without any context, I don’t know where the error is, what is causing it and how to fix it.
I did research this error but the only thing that I found out is that it’s probably related with the config file. Only line in my config line that’s not commented out is the external url and it has a value so I have no idea what to do.
I guess something on the machine is fup. Try the same on a known-good new machine / fresh install.
Ubunut 20.04
Sounds like a fun OS.

Run nodejs app on start Windows

I have a nodejs app which should start running when windows starts. As I'm new to node and have never done anything similar I don't know how to do it. I have been reading some articles from several webs that use AdvancedInstaller or other software but don't know if there are any ways to do it without using other software. Anyone can help?
You need to use pm2
There are other packages aimed at making pm2 a windows service:
pm2-windows-startup
pm2-windows-service
It seems like you need to create *.sh script and put in the Startup folder
maybe this can help you
or just google sh script startup nodejs windows

Upgrade Python modules at Bluemix, to get out of the error (No trigger by the name “interval” was found)

I am using the ipython of apache spark service at bluemix. I need to reinstall setuptools, but I can't enter password for sudo. How can I proceed to make it work ( the goal is to fulfil the following actually )
https://bitbucket.org/agronholm/apscheduler/issues/77/lookuperror-no-trigger-by-the-name
Thanks,
Boris
You do not have root permissions with this service, so you cannot install anything at the system level and you cannot run sudo. If you want to install apscheduler, then run pip with the '--user' arg so that it installs local to your tenant.
Update: IBM has deployed new software levels last week. If you create a new Apache Spark service on Bluemix, your environment won't include the offending version of setuptools anymore.
original answer:
As Randy pointed out, you cannot reinstall setuptools. Until IBM upgrades that package, use the workaround mentioned in the issue you linked:
"In the meantime, you can instantiate the triggers manually"
https://bitbucket.org/agronholm/apscheduler/issues/77/lookuperror-no-trigger-by-the-name#comment-14180022
The author of apscheduler apparently added a check for the version of setuptools. You'll have to use an older version of apscheduler without that check.

gcloud deploy issue - boot2docker 1.3.1

This is a follow on from the question here:
gcloud deploy error: Image with tag google/docker-registry was not found which is based on the post here http://www.incrediblemolk.com/running-node-js-on-google-app-engine-managed-vms/ .
I've followed the steps in the second link and succeeded in getting gcloud and docker to run the github project https://github.com/GoogleCloudPlatform/appengine-nodejs-quickstart locally. However I am stuck on deployment.
After downloading the docker-registry container, I found that I had the 'insecure registry' issue, so I followed the steps in the top rated answer in the stack overflow question linked above. However when I tried to restart the daemon, I received a 'Tls message' as follows:
docker#boot2docker:/mnt/sda1/var/lib/boot2docker$ sudo /etc/init.d/docker restart
Need TLS certs for boot2docker,127.0.0.1,10.0.2.15,192.168.59.103
I was wondering if there is something that I need to do, or if this is a boot2docker issue? I noticed that in the boot2docker project on github, people mentioned 'workarounds' for disabling tls, which I managed to do by adding a line
DOCKER_TLS=no
to my /var/lib/boot2docker/profile file within the VM, and this did enable me to restart the docker daemon, however "gcloud preview app deploy --server preview.appengine.google.com ." requires that tls is enabled. So I feel like I'm untying one hand from behind my back and replacing it with the other in this instance!
Is there some fix required for this, or am I missing something important? If so, do I need to use boot2docker 1.3.0 as opposed to 1.3.1?
If anyone could help me in this matter that would be greatly appreciated.
Otherwise, my strategy I think would be to wait for these tools to mature a bit more, as I am after all using the preview version of gcloud, and I think TLS support in boot2docker is relatively new.
Yes, 1.3.1 is not compatible with our SDK. Plese use the latest (as of today) 1.3.2 or 1.3.0.

Setting up VCAP (cloudfoundry) without a script

I would like to setup VCAP without a script on my linux box (mostly for learning, but also for controlling which packages get installed). I want to do it for a production like system (so it's not my own linux box, but a server that I use for demo purposes)
I am using Ubuntu 10.04 and I have rvm 1.10 installed). I already asked this question on cloudfoundry support (http://support.cloudfoundry.com/entries/21004021-single-node-vcap-setup-without-a-script-chef-etc)
Really apprecaite your input
Looks like your post on the CF forums was updated. As mentioned there, documentation for self-install doesn't exist. Your best bet is to use the existing install scripts, read through what they're doing, and perform the process manually.
The original install script: https://raw.github.com/cloudfoundry/vcap/master/setup/install
The new Chef-based install script, which will replace the original script: https://github.com/cloudfoundry/vcap/blob/master/dev_setup/bin/vcap_dev_setup

Resources