the steps for installing compser on windows 10 - composer-php

Some settings on your machine may cause stability issues with Composer.
If you encounter issues, try to change the following:
The Windows OneDrive folder is not supported on PHP versions below 7.2.23 and 7.3.10.
Upgrade your PHP (7.3.5) to use this location with Composer.

If you have WAMP(or XAMP or MAMP) just desinstall it and then re-install the lastest version. You should be able to have php 7.4.0 and 7.3.12 and then you could install Composer.

Related

How to upgrade pgAdmin 4 on windows?

I installed pgAdmin 4 as part of the postgres installer for Windows. pgAdmin is now telling me there is a newer version (4.8, > 4.5 which I have). However, there is no built in upgrade functionality that I can see, and when I went to download and run the pgAdmin 4 installer to upgrade, it installed itself in the wrong place, leading to problems.
At first I tried installing it to the default location (C:\Program Files (x86)\pgAdmin 4\v4), which was incorrect, because the previous installation (from the postgres installer) went to a different location (C:\Program Files\PostgreSQL\11\pgAdmin 4).
The second time, I pointed it to my existing install of postgres (C:\Program Files\PostgreSQL\11\pgAdmin 4), but it installed itself to a subdirectory there instead (C:\Program Files\PostgreSQL\11\pgAdmin 4\v4), rather than upgrading the existing installation, once again yielding to duplicated installations and problems arising from that. I assume if I go download the postgres installer, it will just reinstall version 4.5 of pgAdmin, though I have not tested this.
What is the correct method for upgrading a pgAdmin instance originally installed by the postgres Windows installer?
I think the best option is to go to Program and files -> Select PostgreSQL and "Uninstall".
Uninstaller will ask you if you want to uninstall the whole application or only individual components. Select individual components and then select pgAdmin.
This will uninstall pgAdmin from PostgreSQL directory.
From now, install the latest version pgAdmin only from official website which will install it into: C:\Program Files (x86)\pgAdmin 4\v4
If you Download the installer from here https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.8/windows/
It should automatically install the 4.8 version in (C:\Program Files (x86)\pgAdmin 4\v4)
overwriting any existing 4.x version but keeping your server connections and setting.
In your case, the previous install was in a different place, therefore, you ended up having 2 versions.
What I suggest to you is go to control panel and uninstall from there all the versions you have. After that go to the above link, download and install the v4.8 in the default location. Every time there is a new version available just install it and let the installer install it on the default location.
Please note that your pgadmin server connections can be found in %appdata%\pgAdmin.
Note that I have personally just upgraded from v4.5 to v4.8 using this method (installing it in the default location) and it worked like a charm.
Not sure the best approach here.
If you update directly pgadmin from: https://www.postgresql.org/ftp/pgadmin/pgadmin4/v4.10/windows/ the installation goes into
"C:\Program Files (x86)\pgAdmin 4\v4\runtime\pgAdmin4.exe"
Wheras the installation of the whole EnterpriseDB Installer from:
https://www.enterprisedb.com/downloads/postgres-postgresql-downloads is installed here:
"C:\Program Files\PostgreSQL\11\pgAdmin 4\bin\pgAdmin4.exe"
This looks like a wholly undesirable conflict? And leads to the problem identified by #Anomaly ?
To anyone finding this post (like me), before uninstalling your current pgAdmin 4, be aware that there may be limits on compatible versions based on your version of PostgreSQL. Following the instructions by Claudio Corchez, I removed my existing pgAdmin 4 and downloaded the latest 6.15. When I attempted to install it, the installer informed me that this version was not compatible with my version of PostgreSQL 10.3. So, I headed back and downloaded 4.30, which is now running. Unfortunately, it warns me each time I run it that a newer version is available. I just need to upgrade my entire PostgreSQL installation.
I had the same issue previously, and had to manually select the path.
Apparently now (v. 4.25) it auto-detects the path and updates correctly.
I had to download from the website, there was no update button embedded in pgAdmin itself

How to install sqlsrv for xampp mac os version

I used XAMPP 7.1.11 for Mac OS. I could not find the extensions directory to install SQLSRV extension I try so many way to solved this problem about 2 Weeks. Is there anyone every setup PHP like this. Let discus together.

Install multiple versions of XAMPP on a mac

I want to install multiple XAMPP versions.
In the answer from NivF007 to the question how-to-install-multiple-xampp-versions-or-multiple-php-versions-on-mac-os-x-10-7 it is said
Install each instance of XAMPP in it's own folder
But how can you do this? (Because you can't change the installation directory)
And when you rename the XAMPP folder after installing the manager doesn't work.
Use the portable versions, there you can chnage the path:
https://sourceforge.net/projects/xampp/files/

Joyent Node.js The software is missing from your system. You may also have to configure it after installation

i have installed nodejs manually and from visual studio 2015 installation , but every time i check for apache cordova dependency cheker i get
Joyent Node.js The software is missing from your system. You may also have to configure it after installation
Same issue. I had installed Node.js version 6.9.1 manually. After uninstalling via Windows (Control Panel->Programs and Features->NodeJs->Uninstall), I was able to go to Control Panel->Programs and Features->VS2015->"Change"->"Modify" and was given the option to install the Joyent version. Prior to the uninstall, Joyent nodejs was not an option when trying to Change/Modify VS2015.

When installing Appcelerator CLI, appc setup command throws error

I am trying to install the appcelerator cli but keep running into an issue that I haven't been able to find a fix for.
When running the "appc setup" command I get the error "cannot find module 'C:\cyclic.js'"
link to full screen capture of error
I am running windows 7 64 bit and am following the directions here https://web.appcelerator.com/product/cli
*Edit: If you are facing this same issue. Uninstall Node, and Appcelerator. Then make sure you install JDK 32 Bit (if using windows). DELETE the NPM and Appcelerator folders in your C:\Users[username]\AppData\Roaming\ directory. Then reinstall Node (I had success with 32 bit) and the Appcelerator CLI. That worked for me.
Hello make sure you have node.js and JDK installed and environment variable set properly. For reference http://docs.appcelerator.com/platform/latest/#!/guide/Installation_and_Configuration. Now, As you already tried "appc setup". You need to delete all cache of previous installation try and try reinstalling again. Run,
sudo rm -rf ~/.appcelerator
sudo npm uninstall -g appcelerator
appc use latest
appc setup
To setup the Appcelerator CLI, install Node.js, install the appcelerator module using the NPM CLI, then run the appc setup command to download and setup the latest CLI package. You can follow the guide here. Also you can check this link, if you experience an issue installing any of the npm packages.
If still not solved, I suggest you to start from scratch. I see you work on Windows, true?:
Remove install of NodeJS from "Uninstall programms" of control pannel
Remove install of Appcelerator from "Uninstall programms" of control pannel
Remove any folder from C:\Program Files or your user's folder referencing "node" "npm" or similar.
Go to your user's folder and remove any .app or .appcelerator folder (could be hidden, so look it well)
Don't forget to look in C:\Users\[username]\AppData\Roaming (probably will be hidden)
Now you have only Java JDK installed (I'm using 1.8).
Proceed with a new appcelerator.EXE install, it must detect that you don't have Node and will download by itself the proper Node version.

Resources