I installed MEAN stack using Bitnami installer https://docs.bitnami.com/installer/infrastructure/mean/
It is installed with all ok status. But while creating a sample project as specified in https://docs.bitnami.com/installer/infrastructure/mean/get-started/get-started/, I am getting error with express sample.
I am trying in my local machine [MacBook].
Is there any specific thing I am missing while setting up stack?
Bitnami developer here,
Try this:
Load the environment (by default, installdir is /Applications/meanstack-VERSION):
cd installdir
./use_meanstack
Create a new MEAN project:
mkdir projects
cd projects
express sample
cd sample
npm install
I hope it helps
Related
While creating a new sfdx project in VS Code I am getting an error saying error resulted in the command.
I have installed all the necessary extension packages in VS code. Both Salesforce CLI and VS code are up to date.I uninstalled both salesforce CLI and VS code and installed it again, yet the issue is unresolved. Kindly help me with this issue.enter image description here
This is probably because the SFDX CLI installed is in a local instance and not a global instance.
On your Command or Terminal Window try:
npm install --global sfdx-cli
I'm trying to install a typo3(v10) extension with composer under XAMPP in the C:\xampp\htdocs\typo3\public\typo3 folder. I'm on Windows 10, I use cmd in admin to install with composer.
With cmd, I accessed my TYPO3 folder using the following command: cd C:\xampp\htdocs\typo3 then I started composer. I typed the command:
composer require typo3/cms-introduction
I get a message that told me the extension is installed. Following the instructions, I must now enter the following commands:
./vendor/bin/typo3 extension: activate bootstrap_package
./vendor/bin/typo3 extension: activate introduction
But cmd returns me the following message (an english translation from the message i get in french)
'.' is not recognized as an internal order or external, an executable
program or a batch file.
How can I activate those 2 extensions?
(De-)Activating TYPO3 extensions is always possible via the extension manager module in the TYPO3 backend.
Side note:
Maybe you want to check out DDEV-local as local development environment instead of XAMPP. DDEV uses Docker and is an awesome powerful tool but easy to use. And it provides a native shell for commands like yours above.
A big plus is the very helpful community. If you have problems, register an account at my.typo3.org, request your TYPO3 Slack invitation and go to the #ddev Slack channel.
This works on Windows:
vendor\bin\typo3 extension:activate <EXTKEY>
Note: You have to solve dependencies manually, but you will be warned and the extension will not be activated if dependencies are absent.
I am installing devspace in my local windows machine using npm
npm install -g devspace
after installed, it needs to Finish installation of DevSpace CLI, in which the following request is failed
Error requesting URL: https://github.com/devspace-cloud/devspace/releases/download/v5.1.0/devspace-windows-amd64.exe
I think it's because of my machine is using the company's proxy. However, I don't know how to config proxy in devspace (just like git, for example).
DevSpace maintainer here. Instead of using npm, you can also download the release binary manually from GitHub: https://github.com/devspace-cloud/devspace/releases/
You can just do this:
Download the devspace-windows-amd64.exe for a release
Rename the downloaded file to devspace.exe
Save the devspace.exe file in a folder (and add this folder to your PATH environment variable) => You may need to restart after changing the PATH variable
That's basically what the npm installer does as well but it seems like it is unable to download the binary from GitHub. This may be because of a proxy or because of anything related to GitHub (your company may hit the rate limit or something else).
I'm trying to create an installer for a python based scientific application. We use Anaconda as a python distribution and I found https://github.com/faph/NSIS-Conda-Macros to help me setup an installer for conda packages.
However, downloading the miniconda installer failed. I was able to solve that with the help of:
Download of file during NSIS installer run freezes at "connecting"
But I found no way to make the updating of packages work. They use:
ExecDos::exec /DETAILED '"$CONDA" update -y -q conda' "" ""
conda then tries to connect over https to get the most recent packages from their server. The connection always times out. When i run the same code directly in cmd it runs fine.
So my question:
Is it even possible to access https in ExecDos::exec? Does anyone have an idea to work-around the issue?
My PHP project uses PGSQL. It runs successfully from Homestead on my dev machine. As soon as I add hhvm: true to my project in homestead.yaml, and provision -- my web app throws a PDOException with a driver is not found. The exception goes away as I remove the hhvm:true and re-provision homestead.
Obviously HHVM's config does not include the PGSQL driver.
How do I correct that?
You don't give a lot of details about your setup, so it's not clear if you have the Postgres driver installed. Postgres isn't supported right out of the box. You have to build and/or install it yourself.
Facebook has an "official" list of HHVM extensions. PGSQL is not (yet) integrated into HHVM proper, but Facebook's page points to the external GitHub project, which is here:
Postgres Extension for HHVM
Below is a summary of the project instructions; you can read them yourself in the README.md files.
Build from source
If you want to build it from source, you will need the hhvm-dev and libpq-dev packages to be installed. Once they have been installed, the following commands will build the extension:
$ cd /path/to/source
$ hphpize
$ cmake .
$ make
This will produce a pgsql.so file, the dynamically-loadable extension. Copy this file to /etc/hhvm/pgsql.so.
Pre-built binaries
If you don't want to build it, there are pre-built binary versions for some of the popular distros in the separate "releases" branch here: Releases.
Again, copy the downloaded pgsql.so file to /etc/hhvm/pgsql.so.
Configuration
Whether you build from source or install binaries, you need to tell HHVM where to find it. Edit your config file (generally /etc/hhvm/php.ini) and add these if they're not present:
extension_dir = /etc/hhvm
hhvm.extensions[pgsql] = pgsql.so
You can check that everything is working by running
hhvm --php -r 'var_dump(function_exists("pg_connect"));'
If everything is working fine, this will output bool(true).
You may need to restart HHVM to have the server pick up the extension.