The following is a guide, step-by-step, to install a YAWS (Yet Another Web Server) on your Mac OSX machine.
It has been tested on 10.6.8 SL and worked flawlessly, although the server needs to be restarted if you start spamming F5.
Here are the steps for properly installing and testing a YAWS (Yet Another Web Server) on your Mac OSX machine:
Installation:
Go to http://yaws.hyber.org/download/
Get Latest source - e.g. 'yaws-X.XX.tar.gz'.
Unpack it (for this tutorial let's say /Users/Name/Desktop/yaws/ ).
Open Terminal (it can be found in Applications/Utilities).
Type: 'cd /Users/Name/Desktop/yaws/yaws-X.XX/' (without quotes).
Type: './configure' (without quotes) and wait.
Type: 'make' (without quotes) and wait.
Type: 'sudo make install' (without quotes).
Now you need to type your administrator password, the terminal will not display anything you are typing, so don't worry if it seems it is not working properly, and press Enter.
Now YAWS is installing, after it has finish type 'sudo yaws' (without quotes) to run the webserver (it might ask again for the password).
Testing:
Open your browser.
Go to 0.0.0.0.
You should see the yaws homepage: Congratulations! You have installed YAWS.
To start testing your pages just put them in '/tmp' and the just type in your browser 'localhost/pagename.yaws'.
Check this for more information and tutorials: http://yaws.hyber.org/
You can use brew: http://brew.sh/
brew install yaws
Related
I'm following the guide
and I am noticing that code tunnel -h in a ubuntu terminal window just launches the code UI.
Using the command palette to get the URI results in a tunnel to my Windows version of VSCode rather than the WSL:ubuntu (which is the one I care about)
How do I fix this?
It appears that, for now, you need to manually install the CLI in WSL in order for it to work. The downloads can be found here. Since you are on Windows, I would recommend the x64 CLI download. When you extract the tar.gz file, you will get a file named code. I would recommend moving it to your home directory for ease. To open the tunnel, run ./code tunnel (from wherever you put the code file) to force the new CLI. If you use code tunnel it will still use the Windows version.
Source: https://github.com/microsoft/vscode/issues/171196
My environment:
Ubuntu 20.04.3 LTS on Windows 10
-> https://www.microsoft.com/store/productId/9NBLGGH4MSV6
PhpStorm 2022.1 Build #PS-221.5080.224, built on April 13, 2022
My Problem:
I'm trying to export a PostgreSQL database inside the Database tab of PhpStorm.
To execute the export I right click the database in the list and click on the "Export with 'pg_dump'" option. This opens the Export window with all the options and command preview:
Inside of the window I get the error message "Path to executable is wrong" even tho the pg_dump file exists at the given path /usr/bin/pg_dump. This stops me from executing the export.
I have tried to manually install pg_dump in another directory and select it in the PhpStorm Export window, but it still won't detect the executable. The executable itself works fine.
The solution to this problem was to do a sudo apt-get install postgresql-client.
Apparently there is a general problem with the pg_dump executable of the "postgresql-client-common" package:
https://askubuntu.com/questions/501091/command-pg-dump-not-found
After installing the postgresql-client package, everything works fine in PhpStorm as well.
The code is pretty simple there: IDE checks that file exists and is executable, then run /path/to/pg_dump --version command and parse output looking for some keywords. Unfortunately there are no logs which can show exact reason, but I guess the issue that IDE can't get access to the file. Most likely due to WSL. The workaround is to install IDE and unpack PG binaries on Windows, then configure port forwarding to make PG server accessible from host OS.
I am in the process of setting up a Linux Based AMPPS LAMP box for local web development needs before the projects go live. I have been following this installation guide for AMPPS website, on a fresh install of CentOS: https://www.ampps.com/wiki/Installing_AMPPS_on_Linux#Important_Locations
The following is stated in the instructions:
First Run of AMPPS When you run AMPPS for the first time make sure your Internet connection is active. Note: AMPPS doesn't support proxy
yet. So you must have a Direct Internet Connection.
Now open /usr/local/ampps/Ampps from Explorer, this will take some
time as it is setting up AMPPS for your Linux. If you are using Ubuntu
OS then you have to start Ampps from terminal with sudo privilege.
cd /usr/local/ampps
sudo ./Ampps
Upon entering ./Ampps in as root, the terminal returns the following:
./Ampps: error while loading shared libraries: libXrender.so.1: cannot open shared object file: no such file or directory
I have done a little of a search and turned up basic fixes, such as:
yum install libXrender.so.1
Even with the libraries installed it throwing the same error.
Any help would be great,
Sorry if my post lacks anything its my first :)
Thanks in advance,
Jon
This seemed to do the trick guys, Thanks anyways :D
$ yum groupinstall "X Window System" "Desktop" "Desktop Platform" "Fonts"
Yesterday I installed Teamviewer 7 on my Centos 5.8 desktop. After a reboot, am not able to see the login screen. Only a blue color screen is visible.
I read https://superuser.com/questions/403548/os-x-stuck-at-blue-screen-after-installing-teamviewer-host-and-rebooting?rq=1
But how do I do that on Centos?
I know that to login to Single User Mode, we need to press a key while the os boots up. And then type single in the cmd. And then?
Once in Single User Mode, you can try to remove TeamViewer from your system.
For example, if you have installed TeamViewer by running the rpm -ivh teamviewer_linux.rpm command, you can run the rpm -e teamviewer_linux command to uninstall it.
I don't think that the Mac OS link you've referred to can be very useful in your case.
If you peek into the teamviewer_linux.rpm (for example by running the command rpm -qpl teamviewer_linux.rpm) you won't find any "Launch Agents and Daemons", since on CentOS TeamViewer is wrapped around a Windows Emulator (wine).
By default the TeamViewer files gets installed in the /opt/teamviewer folder; the only exception is the startup script /usr/bin/teamviewer7.
Finally, the rpm post-installation script does nothing more and nothing less than create a desktop icon and add a menu entry, so I can't really understand how the TeamViewer installation could have broken your system.
Here is my situation:
I am developing PHP CLI scripts on a distant server using Eclipse IDE with the RSE plugin (allows to edit files directly on the server).
Now I need to debug these scripts in a similar fashion than in Java (break points, show the variables content, ...).
I found something that could do the job: XDebug and PDT (Eclipse plugin). The problem is that when I try to launch the debug mode Eclipse says that there is no PHP debugger on the local machine. I guess it should be installed on the server machine.
I would like to know if it's possible to use PDT and XDebug to debug remote scripts and, if it's the case, how to configure them to do so. If not, I'd like to know if other solutions exist. It seems like XDebug uses TCP so it should be possible to debug remotely. I can change my IDE if necessary.
The server runs Ubuntu 10.04 with php5-cli and the dev machine with eclipse runs Win7 32bit.
Thanks
Yes this is possible, you need to enable xdebug in the remote server's PHP.ini file and make sure that the xdebug port (default 9000) is not blocked by any firewalls.
xdebug's page on setting up remote debugging.
Here is the complete procedure for the people who have the same problem:
First, install RSE by following the instructions on this website: http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.rse.doc.user/gettingstarted/g1installing.html
Follow the instructions on this HowTo to install XDebug on the server:
http://ubuntuforums.org/showthread.php?t=525257
Install PDT on Eclipse and do the following changes:
- under Windows/Preferences, go under PHP/Debug and change PHP Debugger to XDebug
- under Windows/Preferences, go under PHP/Debug/Installed Debuggers and configure XDebug. Change the field "Accept remote session (JIT)" to "any".
Open the Remote System Explorer perspective, select your scripts directories and create a project from them (Right Click, Create Remote Project). It will now appear in the PHP perspective.
Let Eclipse run and go to the server (e.g. via SSH). Run the script you want to debug. A Window will then appear on Eclipse proposing you to choose with which "local" (remote via RSE in our case) file you want to link the running script to. Normally, the default script proposed should be the correct one, because it is the one running on the server.
You should now have visual debugging with Eclipse for your PHP-CLI scripts!
Do you want to debug while being able to interact with the script on CLI or do you just want to start it and then step through the code? I guess your question is referring to the problem that you can't access the script directly through a URL. If that's your problem, then I guess the easiest solution would be to debug a usual PHP-web-site which requires your script. Then you can launch XDebug with that web-site initially and step into the script through the require/include-statement.
index.php:
<?php require_once("../../../../../dir1/[...]/cliscript.php");
Best regards
Raffael