As the question suggests, I am facing the mentioned error while running drupal on mac (not containerized), I found similar questions but with different environments (python / windows / debian / docker / etc ..)
environment details are as follows:
postgres version : 10.22
php version : 7.4
libpq.pc ver : 9.3
The solution I was thinking about is to replace the libpq with newer version but not sure how (I am relatively new to mac)
Any suggestions on:
1- how to get later libpq.pc version?
2- is it safe to just replace the existing with it?
3- any other solution for this specific environment setup?
Related
I read that it was impossible to install yii2 on a standard hosting platform (redhat, centos...) without deleting the AssetManager.
And install is lock with it. Access refused, permission denied.... Despite the rights 777 on the assets folder.
And in default way, hack code, disable control like (is_writable) to allow continued the install process to congratulation, but without css ....
But I can't modify all the code , to use it?
They're a lot of issue about assetmanager.
I tried yii1 few years ago, and it was wonderful framework... But everything is permitted under windows. Someone tried to install it under redhat, fedora, Centos.
There is a specific configuration ... Or yii2 not builted and designed for theses environments ?
Because i found tuto about laravel 5.1, Zend 2 since 2013... But nothing about Yii2, and only one... about Yii1... on this hosting OS.
Yii2 is ready for professionnel standard hosting environnement or is just for hobbist with Wamp under Windows ? (Online tuto is in majority on this OS, with Wamp...).
And maybe for that, it's work fine... like i test under windows
Thank you for the links. I had read
Finally I found the answer, which is never explained in the tutorial above (because often disabled and the module is not present in Ubuntu or Debian)
It's SELinux security. To install Yii2 there are the following commands:
semanage fcontext -a -t httpd_sys_rw_content_t 'each folder writable'
setsebool -P httpd_unified 1
Without this open rignt, you can't install Yii2
All what Yii 2.0 requires is a Web server supporting PHP 5.4 or above.
( currently not PHP 7 due to reserved word conflict that will be solved in future releases )
And yes 5 stables versions ready for production has been released, currently Yii 2.0.5
Here is a quick example about how to install Yii2 with CentOS6 which has nothing different from what is already described in the official docs.
If you know any CentOS related issue please post them and we will discuss answers, because sincerely i just did few searches and didn't found any besides few wrong apache or nginx configurations or missing packages like this CentoOS7 case. Otherwise if you need a pre-configured & working VM with Yii2 and CentOS 7, then you may check this vagrant repo.
I am using zimbra 8.02, need to update to 8.5 without losing my mail box and other setups.
Could you guys please help me out and provide me some steps
What Operating system are you using?
You can follow this instructions if you are using Ubuntu -
http://www.jorgedelacruz.es/2014/08/27/zimbra-upgrade-zcs-8-0-7-a-zcs-8-5-0-sobre-ubuntu-12-04-lts/
And then
https://www.jorgedelacruz.es/2014/08/27/zimbra-upgrade-ubuntu-12-04-a-ubuntu-14-04-y-update-de-zcs-8-5-0/
Best regards
Are you using ZCA 8.0.2 OR ZCS 8.0.2?
If ZCS 8.0.2, This can be upgraded directly to (the latest release at the time) ZCS 8.6.0.
(1) wget the correct version you require from here http://www.zimbra.com/downloads/ to your server in question
(2) untar -xvf zcs-***
(3) run the ./install.sh
When trying to get local data to Heroku, I am encountering a version mismatch between two different versions of pg_dump.
Specifically, I am getting this message:
pg_dump: server version: 9.2.2; pg_dump version: 9.1.4
pg_dump: aborting because of server version mismatch
I have found others with this problem, but do not know enough to implement the proposed solutions. (I am new to Ruby on Rails, PostgreSQL, Heroku, and the Mac! Very much at the stage of playing around the picking things up as I go.)
I was thinking I might simplify my life if I uninstalled all PostgreSQL on my local machine and started again with a clean install of PostgreSQL 9.2.2 from http://postgresapp.com/, but I don't know how to go about doing the uninstall.
I'm running Mac OS X Mountain Lion 10.8.2.
OS X 10.8 comes with pg_dump version 9.1.4 in the /usr/bin directory, along with psql and other programs that are client-side PostgreSQL tools. It does not mean that PostgreSQL as a server is installed (unless you have OS X Server Edition).
So you don't have to uninstall PostgreSQL because it's not installed and it's better not to remove these postgres client tools in /usr/bin because they belong to the system as shipped by Apple. They just need to be side-stepped.
The package provided by postgres.app comprises both the PostgreSQL server and the client-side tools of the same version as this server. These tools get installed in /Applications/Postgres.app/Contents/MacOS/bin
To use these instead of the 9.1 ones from Apple when you work in a Terminal, postgres.app documentation says to do:
PATH="/Applications/Postgres.app/Contents/MacOS/bin:$PATH"
and put it in your .profile file.
Once you have done that and you run pg_dump, you should no longer get the error that's it's the wrong version, because it would be the one that ships with postgres.app (currently 9.2.2).
I have this setup and it works OK for me.
If you only need to upgrade your pg_dump to the latest version and you have homebrew and mac, if the app has the latest version and your local pg doesn't:
brew upgrade postgresql
If you're using postgresapp 9.3.x, the path is different. The following worked for me (courtesy of http://sigmyers.com/blog/2013/3/12/postgres-pgdump-version-mismatch-error-postgresapp-postgresappcom)
export PG_BIN_PATH="/Applications/Postgres.app/Contents/Versions/9.3/bin/"
PATH=$PG_BIN_PATH:$PATH
Check here for the latest path: http://postgresapp.com/documentation/cli-tools.html
I'm running Mountain Lion Server. My PostgeSQL server is at version 9.2.1 and the default tools are at 9.1.5.
I had to use:
PATH="/Applications/Server.app/Contents/ServerRoot/usr/bin:$PATH"
to make it work.
Yep, sometimes if you run Postgres.app this may happen after upgrade. Make sure you restart your Postgres.app - it will update your PATH.
In my case I have postgresql installed via homebrew and the executables are here: /usr/local/opt/postgresql#9.6/bin
Or you copy the dump and restore executions to the /Applications/Postgres.app/Contents/SharedSupport folder
or in PdAgmin you point the PG bin Path (in properties -> binary Path) to the path of the executables of your postgre
I want to upgrade database postgresql from version 8.3 to 9.0 on Jira application.
Which RPM should be used to work with Suse SLES10.3 64bit?
How to install Postgresql 9.0 in parallel to Postgresql 8.1?
The best bet to find packages for SUSE distributions is the openSUSE Build Service. The direct links there are a bit of a pain, so please look for yourself.
Parallel installation of multiple major PostgreSQL versions is not yet possible using SUSE RPMs. If you need to do that, you will probably need to build from source.
I would like to install Ruby1.9.2/Rails3.0.3 on my Windows Vista machine with PostgreSQL 9.0 as my database.
I have seen many different instructions on the web as to what works and what does not work.
Can anybody tell me which gem(s) I must install to get Ruby1.9.2/Rails 3.0.3 to drive PostgreSQL 9.0 on Windows Vista?
I appreciate any help you can give me.
I made a how-to for exactly this topic on:
http://netpie.wordpress.com/2011/03/17/setting-up-rails-3-with-postgresql-on-windows/
Please let me know if it worked for you and tell me where you had problems so that I can improve this how-to.
Best regards
Here you can get the Ruby 1.9.2 installer
http://rubyforge.org/frs/?group_id=167
Just click on it and it does all the work, after that go for Rails
Rails is easy, just download and follow the site instructions
http://rubyonrails.org/
About PostGre, you are on your own because I never used it...
But if you follow the instructions on the Rails web site you should be fine, they point the right ways to connect to several DBs