Bitnami Wapp stack: In the installation wizard, PhpPgAdmin is grayed out and I cannot be selected to enable it. Is there away around this? - stack

I am trying to use the phppgAdmin with the Bitnami Wapp Stack installer on a Windows 10 virtual machine. The installer seemed to install just fine except the option to include phppgadmin was grayed out and there was no way to enable it. Does anyone know of a solution to this issue?

I am resolving my own question here. I have downloaded another version that phpPGAdmin is enabled for wappstack-7.4.27-0. Downloaded and everything worked perfectly. Still, if there is another option for the above version I would like to know the solution or understand why it is disabled for the higher version of wappstack-8.x.xx-x.

Bitnami wapp stack ships with PHP version 8+.
It seems there is no PHP 8+ supported version of phppgadmin yet, see release on github: https://github.com/phppgadmin/phppgadmin/releases.

Related

How to properly install Hack and HHVM on Windows 7

I am trying to install and configure Facebook programming language Hack and HHVM on Windows, probably Windows 7. I could not find any solution on it. I saw a Bitnami link which suggest HHVM Installers.
source
I have downloaded the installer files HHVM installer files
but it cannot run on Windows due .run extension filename. How can I achieve this using HACK and HHVM installations on Windows 7.
Hack and HHVM do not support Windows. There was some work in 2015, but it doesn't seem to have continued since then.
Recent versions of HHVM do not support PHP. The Bitnami link mentions running phpmyadmin, so it looks like it's targeting an old HHVM release.
Hack and HHVM do not support Windows but you can try Building and Installing HHVM on Cygwin or Installation: Building From Source although not recommended because they are monumental tasks.
You can also take a look at Building and Installing HHVM.
I personally gave up and installed the supported package in my Mac where I'm using Visual Studio Code with the HackLang plug-in for development.

PyScripter always says: "Python could not be properly initialized. We must quit."

I've googled for a solution, and based on that, let me report a few details:
I've tried 32-bit PyScripter-v2.6.0-Setup.exe with 32-bit python-3.6.1.exe; and 64-bit PyScripter-v2.6.0-x64-Setup.exe with 64-bit python-3.6.1-amd64-webinstall.exe.
I'm on a 64-bit Windows 10 machine.
I uninstalled other versions of Python on the machine.
Tried unzipping rpyc in the \Lib\ folder, as someone suggested that here.
What else should I be looking at?
Here is a tested Solution
Remove old PyScripter
Install Python from Python website. I installed mine from:
http://www.python.org/ftp/python/3.3.2/python-3.3.2.amd64.msi (and it worked)
Now install PyScripter-v2.6.0-x64-Setup.exe from https://sourceforge.net/projects/pyscripter/files/
This should solve the problem.
I got this solution from https: //github.com/pyscripter/pyscripter/issues/715
You are using an old version of Pyscripter. Version 3.4 from https://sourceforge.net/projects/pyscripter/ provides support for all released python versions, virtual environments, conda distibutions and the ability to switch between them without exiting Pyscripter.

Visual Studio Mac Can't run ASP.NET Core Project

This may be very obvious in hindsight. When installing the new VS Mac, and creating an ASPNET Core project, I can't run it by clicking the run button in the top left.
I can run if I right click on the Web project, click 'Run With' then 'Custom Configuration'. Works great.
However, the run item is disabled and I can't figure any way to enable it: http://prntscr.com/f7rsgh
Try loading the solution using Jetbrains Rider. https://www.jetbrains.com/rider
This sounds like it may be the same issue:
https://developercommunity.visualstudio.com/comments/79790/view.html
If you expand the comments, someone says:
OK installing 2.1.0-preview1-006776 breaks VS Mac 7.0.1. I see the same problem that you are seeing. There is a NuGetFallbackFolder in the sdk folder and VSMac incorrectly uses that as the latest sdk folder. So for now you can fix this by removing the /usr/local/share/dotnet/sdk/NuGetFallbackFolder/ folder. Although that may break the 2.1 preview version of the dotnet cli if you are using it from the command line. VSMac seems to be OK running and debugging ASP.NET Core projects after removing that folder.
It seems to have fixed the OP's question from the forum thread. This is a bug with Visual Studio for Mac that's been fixed in a pending release, but the update doesn't seem to be out just yet. I hope this helps you out in the meantime.
Download and install the latest asp.net core
Download or upgrade to
the latest openSSL
This helped me

Aptana project types not available

I have recently installed the Aptana plugin for Eclipse as I wish to learn Ruby and Ruby on Rails, it doesn't seem to have changed anything. Usually when I install a plugin of the sort, there will be new project types under the "New Project" menu, but none appeared. I checked tutorials online and they suggest that there should be new project types as seen in the image below, taken from a tutorial.
Instead, I see the same options I did before.
I wondered if the plugin didn't install, but when I try to install it again, It says it's already installed. I am using Eclipse Juno Service Release 2 with a 64-bit Windows 7 operating system and the version of the plugin from the URL given on the Aptana website (http://download.aptana.com/studio3/plugin/install). Any help would be much appreciated.
I don't know why that's happening. Here's a suggestion for how to get around it.
You might be better off installing and running the standalone Aptana Studio product. It would be a separate installation on your desktop, and thus wouldn't have the same settings as any Eclipse installation you already had, and would be more space on your hard drive. But probably there isn't much you would share between Ruby/Rails development and other development, and it's not that much space.
I've done it both ways - installed Aptana into an Eclipse I've already got, and installed the standalone version - and now I would only do standalone.
I don't know what was wrong in the first place, but after I installed the Aptana plugin, I installed the PyDev plugin. I think this removed the Aptana plugin because of conflicting dependencies (I don't know why it wouldn't tell me, though). I tried installing the Aptana plugin again and it told me there was a conflicting dependency with the PyDev plugin, so I uninstalled it and reinstalled the Aptana plugin. It works now.

Problem with Aptana Studio & XULRunner 8.1

I recently installed Ubuntu Jaunty and I'm encountering a problem when I try to run Aptana Studio under it. Any interaction with the internal browser crashes the system. I checked the log and after some Googling came to the conclusion that it was crashing due to the incompatibilty with XULRunner 9.0 which is installed on my system. I followed a couple of solutions I came across and installed XULRunner 8.1 (to a different directory) and pointed the MOZILLA_FIVE_HOME enviornmental variable to that particular version, as suggested.
export MOZILLA_FIVE_HOME=/usr/lib/xulrunner-8.1
However, the problem persists! When I cd into the xulrunner-8.1 directory and perform a ./xulrunner -v it still lists it as being version 9! I can't uninstall 9.x as several other major packages depend on it, one of which is the version of Gnome I have installed.
This is my first time using Linux since I played around with RedHat 7.2 waybackwhen, so I'm probably forgetting to do something obvious. Can anyone help me out?
I run Aptana on Ubuntu Jaunty as well and met with similar problems as yourself. This thread solved my problem, and I always launch my Aptana from a startup script. Particularly, the post by 'stevewalker'. Just to post his startup script here:-
#!/bin/sh
MOZILLA_FIVE_HOME=/usr/lib/xulrunner
if [ $LD_LIBRARY_PATH ]; then
LD_LIBRARY_PATH=$MOZILLA_FIVE_HOME:$LD_LIBRARY_PATH
else
LD_LIBRARY_PATH=$MOZILLA_FIVE_HOME
fi
export MOZILLA_FIVE_HOME LD_LIBRARY_PATH
/usr/local/aptana/AptanaStudio $#
Hope this helps! =)

Resources