I have puppet 3.4.2 and Vagrant 1.6.5. We configured our puphpet setup over a year ago.
This is all working fine on my environment, but a fresh install downloads a new version of the base box which has an updated version of puppet and so our old configurations don't work.
We are using this box: https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64. I must have v1 but for new instances it will download v2.1
I have tried updating the puphpet config.yaml, but when I upload this to puphpet.com I get the message "The config file provided was empty! Please recreate your manifest manually below.".
So I see a few solutions but I have blockers on each of them:
Use the old base box. Is there an archive copy of V1 of this server somewhere on the internet? https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64
Use the new base box but downgrade Puppet. How do you downgrade Puppet and all it's dependancies?
Figure out some way of importing my config.yaml in to puphpet.com and start using the new versions. Is there anything I need to do to get puphpet.com to recognise an old file?
Reconfigure the whole file from scratch. Do you know anyone that can help me?
Thanks for advice.
It's still there, but no longer supported or publically listed.
All boxes come pre-installed with Puppet 3.4.3, which is BC with 3.4.2.
Sorry, changes in the past month or two have broken BC with old config.yaml files. You'll need to manually select your options again.
Just do this. Honestly, it's textboxes, dropdowns and radio boxes, and will take you less than 10 minutes.
Related
I use vagrant and installed it first day of a bootcamp I took. I'm now trying to learn react but the installed version of node is too low to use npx/npm. I've tried a ton of different things, looked up different videos and I'm at a wall. I now have nodeJS version 12, and node v7 and my environment seems to just default to v7 and I can't sudo apt remove it
Well, I think there are 2 steps to resolve your issue, more or less it will help you in a long run.
Uninstall all the node installed
You can follow this guide on SO to do the removal steps: How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
5 mentioned steps are enough to make sure your dev is clean of node.
This will revert your development back to default environment. After that, just dont install any new node like the old way you did.
Install nvm to manage node version management
Go to https://github.com/nvm-sh/nvm and follow their installation guide.
Basically this tool will help to manage your node version on your machine. You can install multi version and choose which one to work on, depend on your specific needs.
The installation guide is quite easy to follow, for some Mac OS user there might have some slight tweaks, but it's not that difficult.
Hope this help,
nvm 100% solved the issue. Was able to use it to update the one that wasnt updating, and i was able to uninstall the unused version. Unfortunately i could never get create-react-app to work. Its something to do with a node_module folder installed in my root files that i cant find and delete so it crashed every time i try to create react app. But i think i can just use cdn to create a react app so i guess its not that important, at least i have npm/npx if i need it
I have been running a pretty old version of Homestead for years. At various times, I have tried updating a few times. I always got an error about being unable to resolve a package. Since the version of Homestead that I was running was technically working, I probably left my old version of Homestead running a bit longer than I should have.
I finally buckled down and worked through updating it. Everything appears to be back like it was except for one frustrating difference. Many of the projects in my Homestead interact with one another, oAuth, API integrations, etc., and while I can visit any project in my browser like before, none of the projects can resolve one another.
I always receive a curl error:
cURL error 6: Could not resolve host:
So, for example, one project that relies on an API call to another project for a dropdown list in a form, the API call never resolves and I can't populate the form.
Has anyone experienced anything similar? Any thoughts on what may be causing this? I have Googled around without much luck.
The problem initially started when I updated my laravel/homestead box. So, I thought that maybe the update corrupted the box somehow. I have run vagrant destroy and then vagrant add laravel/homestead to reinstall the newest version and the issue is still there. I noticed that the newest version that installs is 8.0.0-alpha2, so I tried specifying vagrant add --box-version 7.3.1 (the latest stable that doesn't have alpha or beta in the name) and again I am getting the same issue.
GuzzleHttp \ Exception \ ConnectException
cURL error 6: Could not resolve host: outside-project.local (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser.
If I make the exact same API call that the project is trying to make, it resolves as expected in Postman. I can also visit the project and all projects as expected in the browser. I would expect that projects can resolve each other just like they did before I tried updating Homestead.
If any one else is experiencing this, here is how I got it working:
vagrant ssh and add any projects that need to communicate with one another to the /etc/hosts file.
I want to update a module on my running WildFly10.0.0.CR4 Server with the help of a cli file on Windows.
For example I would need this to update the Infinispan plugin from version 8.0.1.Final to version 8.0.2
According to a book I am referrencing to, this could be something like
jboss-cli.bat --file=myupdate.cli
where the myupdate.cli file contains the code telling the server what to do (In this case, update Infinispan). I just need to know what to enter into that file - Best would be an example with Infinispan and a documentation on how to write such a file for other plugins by myself.
Thank you in advance!
EDIT:
It may also just delete the old version and install a completely new one, if this is easier.
You don't really want to just update random libraries/modules. Some of them, such as Infinispan, are tightly coupled to the server.
For final releases you can use patching to update an existing server. You just need to download the patch for the container you want to update.
First - does upgrading also patch?
Second - this is the main problem area, last time I tried upgrading magnento through the /downloader I lost my entire site and had to start from square one.
Most of my files are currently at the 1.9.1.1 version - and are needing to be upgraded to 1.9.2 - is there a specific order which these need to be upgraded in? What is the most efficient and effective way to get those upgrades on there.
Patching - We had our host dev try and patch our site with the SUPEE-6285 and he butchered that.. Any patches we try to do in addition to it now are useless and have no effect on our site. Is there a way to remove that patch and patch the with the newest one - being SUPEE-6482
About your first question: Yes.
About second one: always create a backup before updating and patching, and before test on a testing server never try to upgrade your shop on production server because there might be some extensions conflict.
And yes there is a specific order about patch files, if you want install all of them. because sometimes some of them are required to install a specific patch.
To revert an installed patch use this command:
sh patch-file-name.sh -R
To check installed patches history, check applied.patches.list located in app/etc/
For more information and to learn how to install and revert a patch check these links out:
http://devdocs.magento.com/guides/m1x/other/ht_install-patches.html
https://info2.magento.com/rs/magentoenterprise/images/Installing-a-Patch-for-Magento-Community-Edition.pdf
I just installed red5 on my server, and the install seems to work fine. As you can see here: http://onelifemedia.com:5080
I got this far by using this walkthrough: http://www.webhostingtalk.com/showthread.php?t=1046590
The /demos page gives me a 404 error. So I logged onto the server, and checked to see if the "demo" directory was already there. It was not.
The applications that I installed were a directory up from the root directory. I'm not sure if this is right or not.
Either way, my end goal is to actually get something working besides the main page. If I can get the demos to work, then hopefully I should be well on my way.
I guess my questions can be broken down like this:
Does anyone know how to get the demos working?
Should I forget about the demos, and try to start writing my own code?
If I should write my own code, how should I go about installing it? Since the installer is not properly installing the demos.
Thanks
The tutorial is good but you dont need the admin app. Use the installer link in the tutorial and install the demo you want to use. The content of the "demos" directory is only the swf files used to access the server demos which you use the installer app to install. For instance , select "oflaDemo" and then from the main page navigate to demos/oflaDemo et voila.
I know I'm biased being a core developer, but we've attempted to make the server as ez as possible to use.
I could install demos from the latest svn trunk, Checkout the source, use ant&ivy to build and run the server and you can install two sample apps(oflaDemo and SOSample).
You may need to use ivy commands resolve some of the common issues during installations.
E:\dev\red5\java\server\trunk>ant ivyclear dist
()Red5 user mailing list may help you, because this is not exactly problem with Red5 source.
()http://stackoverflow.com/questions/11156222/red5-demos-not-working/11935532#11935532
I could resolve the issue based on the information in Red5 users mailing list and comments by Mr.Mondain in one of the posts in Stackoverflow