![]() ![]() then you will see if you run php -ini again that it now sees your new file: Type: $ sudo cp /etc/ /etc/php.ini (and enter your password) You need to copy that file to the name php expects so that you can edit it, like this: this is because in /etc there is a file called /etc/ as an example and to show it is not in use. ini files in: /Library/Server/Web/Config/php Run php -ini at the prompt by typing it and pressing enter On OSX/MacOS do the following in a Terminal window: I made my changes to the php.ini file that was listed there, restarted apache, and re-ran the web page the new edits were shown there. Because I was interested in what the web server was using I knew that I should use the path returned from the web-page results. (the '2>&1' and 'grep' elements just restrict the output of the command to useful information, i.e. You can find all the possible php.ini files using this:įind / -name php.ini 2>&1 | grep -v "denied" | grep -v "directory" If you are interested in what PHP is being used by the web server, only use the information gathered from a web page that uses the 'phpinfo()' function.įor example, on my system the versions reported by the two different methods were:įor the php.ini file path things were different, too: ![]() If you have a system that has multiple PHP installations (like mine did) the results you get from using the command line tools MAY BE different than what is actually used by the web server. This does not necessarily imply that I intend to resolve any of them.This is rather old thread, but I would like to add a further clarification. Meanwhile, I have added a number of these requests as issues. Over the years, I got a lot of feature requests, but due to lack of time and motivation, I hardly implemented any of them. ![]() Probably, I will have almost no time for working on it (as it was the case in the last few years), so its future is currently unclear. Older versions are untested.įor pre-compiled binaries, see the Releases page. It should be able to compile the project with Xcode 9 out of the box. PASHUA FOR MAC OS X SOFTWAREDespite that, Pashua is still a valuable tool used all over the world (albeit not used by me …), which is why I released it as Open Source Software (3-clause BSD license). PASHUA FOR MAC OS X CODEIn other words: When inspecting the code, you will find generally mediocre code quality, lack of SOLID principles etc., and you should in no way use Pashua’s codebase as a reference for how macOS applications should be built. Most of the code was written between 20, and the codebase never experienced a major refactoring. Pashua was written by Carsten Blüm ( in Objective-C/Cocoa and should run on macOS/OS X 10.9 or later. See the Pashua Bindings repository for code and more information. Typically, it is used with languages that have none or only limited support for graphic user interfaces on macOS, such as AppleScript, Bash scripts, JavaScript, Perl, PHP, Python, Ruby, Tcl and others – and if your favourite language is not yet supported: writing the glue code for communicating with Pashua is pretty simple. PASHUA FOR MAC OS X WINDOWSPashua is a macOS application for creating native dialog windows from almost any programming language. Pashua: Native macOS dialogs for scripting languages ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |