Why is MAMP so slow to apply any change on my local dev sites? - mamp

I'm using MAMP (free version) to develop a website locally and it takes about 1 minute to apply any change (for instance, variable declaration). It takes the same time on Firefox, Safari or Chrome even if I load the page without the cache (CMD+SHIFT+R or SHIFT+refresh). Working with the "localhost/" url instead of a virtualhost doesn't change anything…
Does anybody have the same issue and have a solution?

To fix it try this: in your hosts file you need to list all your local dev sites in a space delimited row like so...
127.0.0.1 localhost localsite1.dev localsite2.dev localsite3.dev

Related

moodle accessing from intranet as well as internet

Good day everyone, I have been trying to put my moodle online so pcs from internet can access it, but until now, no luck at all. (Im using moodle 3.9 on ubuntu 20and apache2).
I tried to configure the moodle file config.php, setting the directive $CFG -> wwwroot = "my-public-ip/moodle". Then, when I access to moodle from the server, I can access it by "http://my-public-ip/moodle", when I try to access via localhost, its running.
when I try to access the server from an outside pc. When I type "http://my-public-ip/moodle" it is not running.it looks like the outside pcs are either ignoring it, or searching for another configuration file. I dont know what the hell is happening, this is very odd.

TYPO3 10.4 sometimes page rendering is very slow

System:
TYPO3: 10.4.22
PHP: 7.4.30
Apache 2.4.46
Windows Server 2019
X64
Hello!
I have the issue that sometimes the page rendering is absolutely slow. I added a simple page and "normal" page generation is about 200ms. But about each 10th load of the page it is very slow - about 20 seconds.
I checked the issue in the Admin Panel and if I look at the TS-Tree I have a very big value in the Script Start row (e.g. +21075 for a 21048ms run vs. +235 for a 205ms run).
I checked the performance (memory, network, cpu of the server itself and everything looks good). I did a test when no one else was working (it is a intranet installation) so I was the only one hitting the page and run into the same issue. If I do a reload after a slow load I get a fast load immediately.
Any ideas what is happing on these slow runs?
Thank you
Christian
Try '127.0.0.1' instead of 'localhost'
(in typo3conf/LocalConfiguration.php, 'DB' => 'Connections' => 'Default' => 'host')
The problem was an old File Storage Setting. The file storage was configured as local filesystem to a directory which was a symlink to a fileshare on another server. This server was switched off. The file storage was not in use anymore but the record in TYPO3 still existed and was set to "online". I have no clue why it slew down the page loading only each 5 or 8 time....

Raspberry webserver change website name

In my browser i can type 192.168.178.33:8000 to access the webpages on my raspberry or
http://raspberrypi:8000/
Somewhere must be set that the web browser translate http://raspberrypi:8000/ into 192.168.178.33:8000 I tried to find a nameserver but I've no idea what or where I can change this
Is there a simple way to change
http://raspberrypi:8000/ into http://whateverIWantHere:8000/
You can edit your hosts file. The location is different for each OS and may also be different for different versions of the OS. Note that you only need to do the changes on the computer where you want to translate it.
Windows 10:
C:\Windows\System32\Drivers\etc\hosts
Linux/Raspbian:
/etc/hosts
Add the following line to the end of the file:
192.168.178.33 raspberrypi
You may have to restart, I'm not sure if the changes will apply immediately. And you can now type 192.168.178.33:8080 in your browser.

Intalio Ajax Forms pointing to localhost

Anyone working with Intalio|BPMS?
I'm trying to implement a process using the Comunity Edition, and I'm having a problem I can't seem to solve.
The process has an AJAX Form and if I go to ui-fw in the server using localhost everything works, but if I try to access the server remotely using the url it doesn't.
The iframe for the AJAX Form is pointing to localhost and not the url.
From the very bad foruns at Intalio, I've checked /tried:
deploy from the designer using the url
finding every mention of localhost in the process deploy dir, and also in the var/conf
Still no luck.
Any ideas anyone??
Thanks in advance
Ricardo, IIRC the form is deployed according to the settings you use in the deployment manifest. I believe you can also set an other host name in the deployment manifest to deploy to localhost, but declare a different host name for the form and processes.

How to configure MAMP to serve perl CGI scripts (NOT localhost!)

I'm using MAMP-pro to serve my domain to the outside world.
I'm not a very experienced sys-admin, though I've slogged my way through a few basic things. I know what apache is, and I can read-most-of but not generate-without-guide related .conf files.
I've got a perl script which I've tested from the command line and it works (outputs as desired.)
When I try to access said script from the browser, I get 404.
I've tried placing the script at:
/Users/me/Sites/mydomain.com/htdocs/mycgi.pl
/Users/me/Sites/mydomain.com/cgi-bin/mycgi.pl
/Users/me/Sites/mydomain.com/htdocs/cgi-bin/mycgi.pl
and accessing it as:
http://www.mydomain.com/mycgi.pl
http://www.mydomain.com/cgi-bin/mycgi.pl
and all the various combinations, all to no avail (404.)
The script and its container directory have permissions 755.
So, what other steps am I missing? Are there any good set-up guides? I tried the MAMP-Pro manual, but it is filled with such information as "the cancel button cancels the current operation" and not really anything useful. Google turned up several hits that all seem to talk about how to make this work on localhost, but I'm trying to serve this to the outside world.
Any hints?
Thanks!
The official online documentation has a section on virtual hosts. When creating a host for www.mydomain.com you can choose the DocumentRoot which is called "Disk location" within MAMP PRO. If you still get a 404 error, take a look into the error_log for a more specific reason (i.e., where Apache tries to find the file in question).