File appearing in mac that should be deleted - macos

I am new to Apple products and I am following this tutorial http://coolestguidesontheplanet.com/set-virtual-hosts-apache-mac-osx-10-9-mavericks-osx-10-8-mountain-lion/ so I can get a virtual host setup. I installed MAMP fine. I also followed the vhosts setup and all seems to working ok but it doesnt work once i load the page i.e mysite.local
After some playing about I removed MAMP from my machine and ran sudo nano /etc/apache2/extra/httpd-vhosts.confit brings up the last file i did have although i cannot find it in finder as I have removed MAMP from my system.
Why is this happening?

MAMP stores its configuration files at /Applications/MAMP/conf/apache/extra/ (see http://foundationphp.com/tutorials/vhosts_mamp.php), not at the default system location (/etc/apache2/extra/). You uninstalled MAMP correctly, but the guide had you editing the default Apache files that came with OS X, not the ones that MAMP uses.

Related

How to install Typo3 in Windows 10 with XAMPP?

I have installed XAMPP in Windows, It is working perfectly. but when I installed Typo3 version 8 and it Showed some errors
PHP OpenSSL extension not working.
PHP extension soap not loaded.
Current directory is not within in the current path.
Low PHP Script Execution Time.
PHP max_input_vars very low.
Windows apache thread stack size.
But I can't able to fix the following:
PHP OpenSSL extension not working.
PHP extension soap not loaded.
Current directory is not within in the current path.
Windows apache thread stack size.
What should I do?
Thank you
Here is the full configuration for the Apache On windows server. This working fine with my windows 10 with SSL.
<script src="https://gist.github.com/GhanshyamBhava/41d3a34acc11cec2a4828b0d4b2c840f.js"></script>
Hope this will work for you.
Greetings!
The errors above are not something you have to worry about.
You don't need openSSL for development, it is working without soap (maybe this is used by TER), you have to paste all typo3 src in root path because windows doesn't support symlinks.
But if you want to make all things work you have to use vagrant or docker.
Vagrant requires VirtualBox or other Virtual machine tool.
But docker has a boilerplate ready to use: https://github.com/webdevops/TYPO3-docker-boilerplate

Copy db from xampp files, sytem not working

I have a question. My windows system stopped working and I would like to copy db data from xampp who was intalled on this system. I have only xampp files. Is it possible ?
Sorry for my english.
You can just copy complete XAMPP directory to another working Windows system and try to launch it as usual. Or, you can try to backup current xampp directory, reinstall xampp somewhere else, and then overwrite it with your backup.

MAMP not starting Apache server on El Capitan 10.11.1

So I've been using MAMP just fine for an Apache server on Yosemite for some time now. I only need one local host, so I'm using regular MAMP and not MAMP Pro. I am on MAMP 3.4
When I click the "start servers" button, it doesn't respond to the click. It just shows the colored spinner like the application froze, and then nothing happens. Only the SQL server will start but not the Apache.(I don't even use SQL)
I can click through the preferences window just fine, and I can click the quit button, but the start servers button just gives that error.
The Apache box in the top right isn't filled in, and wont let me fill it in either. SQL box is filled it, if that matters. No error message at all. Totally lost.
I ran into the same problem as well after upgrading Mavericks to El Capitan. Mysql did start, but Apache failed starting. I'm running MAMP 3.0.5 (regular version).
I managed to fix this issue by renaming a file in the folder /Applications/MAMP/Library/bin. Rename envvars to _envvars and restart Apache. This made Apache running again on my machine.
Ok im new here but i figured it out.
sudo apachectl stop
Just ran that command.
Try copying the pre update version of your httpd.conf file and restarting apache as recommended above.
sudo cp /private/etc/apache2/httpd.conf.pre-update /etc/apache2/httpd.conf
sudo apachectl restart
This worked for me. I had issues getting MAMP (Pro) to start Apache and when it was running it took a while to shutdown Apache, which is odd since it didn't start.
I blame El Capitan, always blame the captain if things go wrong. Except Captain Morgan, that's your own fault.
Reinstalling MAMP was the easiest way for me as terminal still scares me. But make sure you follow the steps below so you don't lose all of your files and databases!
1. Rename your MAMP folder in Applications/ to "MAMPOLD" so that you don't overwrite your htdocs and databases.
2. Downloaded and install a fresh copy of MAMP from https://www.mamp.info/en/.
3. Replace the 'htdocs' and 'db' folders in your newly installed MAMP with the ones from your "MAMPOLD" folder.
Note that for the db folder I just transferred any folders and files that didn't exist in the new db folder so I didn't replace anything important. This may not be necessary but I didn't want to risk it.
4. Finally when you launch MAMP again you may have to change the ports to default if it isn't working. I had them orginally set to 80 and 3306 which is no longer working so now I have to put up with seeing localhost:8888 which is annoying but at least it's working! If anyone can help me with this I would be grateful.
I found that the ServerRoot in http.conf used the path "/usr" Most Macs use "/users". Soon as I changed it and restart apache MAMP went live

PHP.ini Settings Are Ignored By PHP5.3.5 Running With Windows 7 And Apache 2.2.15

I did an install of PHP5.3.5 on Windows 7 Home Premium using the MSI installer download. I got it to overwrite a previous version of PHP5 in C:\php5\
When first testing it, the server failed to start. I fixed this by adding the path to PHP in the Apache2.2 httpd file where the installer had inserted 2 lines of coded pointing to the ini file directory and the PHP DLL but had left out the directory path. After doing this, the server starts ok and I can run phpinfo to view the PHP settings in my web browser on local host.
In the phpinfo it states that the loaded configuration file is C:\php5\php.ini as expected. But if I make any changes to the settings, and reboot the server, none of the changes are reflected in phpinfo. Yes, I do refresh the browser window.
If I rename the php.ini to something else to make it invisible phpinfo then correctly identifies that there is no php.ini file loaded.
So the settings in php.ini are being ignored and some default settings are being used (but I have no idea where these are derived from). As far as I can tell, there are no other php.ini files on my computer.
In phpinfo it states that the Configuration File (php.ini) Path is C:\Windows but this is the same as on a Windows XP computer that I work on. And in the windows folder I don't see any php.ini file.
In the windows registry, there is no mention of PHP5, and the PATH environment variable starts with C:\php5\;
So hopefully someone can suggest how I can get PHP5 to take notice of the C:\php5\php.ini settings. :)
You may have more than one php.ini file. If you do, and you don't realize that you do, you will be slowly driven insane [I speak from experience].
So, have you upgraded from a previous version of php to your current version? If so, delete all previous version php.ini files. Check your environment and system variable paths. Eliminate any references to previous versions.
You say youp're running Apache, but is MSII also running, or did you turn it off?
You may have to go into registry ( I no longer use MS OS so I don't know what or how VISTA or Sys7 implement Registry. I used XP when I had this problem and I had to manually eliminate Registry entries for previous versions of PHP.
Lots a luck!

After upgrading Fedora, why can I no longer change permissions of a file mounted via SMB

I had been running Fedora 9 for the last year --- I have a Windows box (actually a VM) that mounts a folder on the Fedora box using my own name/password. I do this so that I can run my version control program (Vault) on Windows. It has worked flawlessly for the last 6 months.
Yesterday, I upgraded Fedora from version 9 to version 11. Since doing so, I am no longer able to change file permissions from my Windows box. Nothing has changed, there's no firewall on the machine, SELinux is disabled (SELINUX=disabled in /etc/sysconfig/selinux), etc
I can still read the files. Any idea what has happened and how I might fix this?
Thanks,
David
P.S. The error I get is
An error occurred applying attributes to the file:
....my filename...
Access is denied.
P.P.S. I AM able to create a NEW file in the mounted folder. After doing so, I can change its properties to make it be read-only. BUT I then can NOT change its properties again to be writable. Hope this helps.
Turns out this would appear to be a bug in the latest version of Samba that you get when you install Fedora 11.
I manually built SAMBA 3.4.1 from source, installed it and my Windows machines work just fine with it.
(Just in case anyone else searches this site)

Resources