I've previously had a Drupal installation set up in WAMP. It's still in my www folder.
I want to start work on another (Wordpress) site. I made a new folder in WAMP and set the Drupal folder to Drupal.old so that it wouldn't use it, but I could still keep it there.
Now when I go to PHP My Admin in WAMP it just displays a 404 error.
What am I doing wrong? I just need to install WP on my local machine
Francesca,
You should never put anything of yours in the www folder. That belongs to WAMP and is basically the localhost site. So by renaming it you have deleted the loclahost site and therefore phpmyadmin with is an alias off your now lost localhost site.
You should either create subfolder below the www folder for your sites like
c:\wamp\www\drupal1
c:\wamp\www\wordpress1
But that is not the best solution.
It is better to create Vistual Hosts, one virtual host for each of your sites.
Pop over to the WAMPSERVER Forum
Do a search on 'Vistual Host HOWTO' and you should find a tutorial on how they are setup.
Related
I'm new to Django and Apache, so apologies if my terminology is a bit off.
I have a Django app that I'm serving with Apache using mod_wsgi. I used this guide, and just switched to Apache from the Django dev server. In my 000-default.conf file I have this line
WSGIScriptAlias / /home/ubuntu/Projects/myapp/wsgi.py
Everything works fine and the homepage of my app is example.com. However, I find now that there are images (a few tilesets) that I was previously accessing at example.com/tiles which are now not accessible, because they are actually stored at /var/www/html/tiles.
I understand why the paths aren't working, but I'm wondering if there's a way I can keep running the django site from example.com while also serving the tiles from a different directory.
I think if you add a preceding configuration directive:
Alias /tiles /var/www/html/tiles
... it should fix it.
Please note that order of Apache configuration directives may matter. More information about Apache and Alias.
My wamp 2.0 is using around more than 100 large database and a lot of projects.I also made around more than 50 virtual host. Now I need to upgrade wamp 2.0 to 2.5.
I got some suggestion on internet that take back up of database and files , then uninstall wamp 2.0 and install 2.5 then set up every thing again, but it seems it is not a right way.
What is the best way ?
Usually I follow following steps to do it easily.
Stop Wamp Service
Rename the wamp folder to wamp-backup
Download latest version of wamp and install it
Rename the data folder of mysql with some different name
(C:\wamp\bin\mysql\mysql5.5.20)
copy data folder of mysql from wamp-backup and paste it to new
install wamp mysql folder (C:\wamp\bin\mysql\mysql5.5.20)
Rename new httpd-vhosts.conf file to httpd-vhosts-backup.conf.
Copy old httpd-vhosts.conf and paste to new installed wamp
(C:\wamp\bin\apache\Apache2.2.21\conf\extra)
In apache 2.4, the directive Allow was dropped in favor of new
directive Require. So change the settings from Order Deny,Allow
Deny from all Allow from all to Require all granted
From
Order Deny,Allow
Deny from all
Allow from all
to
Require all granted
9.The old www folder in wamp needs to be copied into the new one.
Let me know whether it's working or not.
you should do this , I recently updated it , first of all I took my Wamp directory back, then uninstall Wamp not remove the www directory , After that install the latest wamp on the same location , after this copy the folder named data inside the old wamp bin\mysql\mysql5.5.24 and paste that folder inside your new wamp on the same location then run your projects after starting the wamp services.
Note: folder version of db may be different and also latest wamp is based on virtual host so create v hosts also
Thanks
You may directly Upgrade Wampserver from Secondary repository of Wampserver files.
There are various options present on the site:
Install Wampserver full version
Wampserver Update
Addons-
Applications
Apache
PHP
MySQL
MariaDB
Also, one could directly download Tools and Visual C++ packages from here.
So, my suggestion would not be to make any changes in any file in the wamp, nor uninstall the present wamp, and download the latest version. Simply update your wampserver from this website.
There will be no change to the Apache, PHP, MySQL, and MariaDB
settings and versions used; your local sites and databases will not be
affected. This update will be necessary to be able to install the last
addons Apache, PHP, MySQL or MariaDB
Quoted from the site itself.
NOTE: Before uptading, you may just make a copy/backup of your "wamp folder" somewhere on your local machine. In case there is some issue in the update, you won't lose any file and always be able to restore your previous work.
Hope this answer helps someone, if it does kindly upvote. All the best!
To update to latest wamp version safely, use http://wampserver.aviatechno.net/
You can update complete wamp or install newer php/apache versions.
The problem I am facing is that I just upgraded to Win 7 64-bit and installed Wamp server with VC++ and it works fine.
But I can't access subdirectories in the web directory (C:\wamp\www), I can access the files although.
Please guide me through.
It is now strongly advised that you create Virtual Hosts for all your project, even those that you store in the \wamp\www\project1 folder structure.
WampServer now assumes that you have done this, and that is why you get this issue.
Here is a previous answer Project Links do not work on Wamp Server
I've been struggling with a 403 error on my WordPress site. All of the suggestions I found involved modifying the httpd.config of the apache server, particularly
(located: C:/Wamp/bin/Apache/apache2.2.22/config/httpd.conf)
# onlineoffline tag - don't remove
Order Deny, Allow
Deny from all
Allow from 127.0.0.1
</Directory>
to
# onlineoffline tag - don't remove
Order Allow, Deny
Deny from all
Allow from all
</Directory>
However this didn't work for me. I changed it back to the original settings and restarted WAMP - Now WAMP's icon goes orange instead of green.
I've seen a lot of people saying it's skype. I do not have skype installed. Wamp was working earlier today but it stopped after I made changes.
(Note, to find the httpd.config file I did a search of the folder of Apache. he first result was for a file with the same name located in: c:/wamp/bin/apache/apache2.2.22/conf/original/httpd.config) I mistakenly modififed this file initially but once i realised it was wrong I reverted it to it's original form).
Point 1.
Use the wampmanager icon in the system tray, left click menus, to access config files and lots of other things. Then you will be editing the correct files.
Point 2.
What did you think the effect of
Deny from all
Allow from all
Was going to be?
Question:
Where did you install your wordpress site? ie what folder?
Just back up you www directory along with your database tables, then uninstall WAMP totally. After uninstall, delete the WAMP folder. Then reinstall WAMP
I am very new to apache and django, so execuse me if this question is simple. I am trying to deploy an existing site to an apache server. For the time being, the site is still in development so I am only deploying it as a virtualhost on my local machine.
I am using Django's WSGI module in the deployment. In my site's config file, I have the following aliases:
Alias /media/ /home/tester/Desktop/siteRootDir/media
Alias /content/ /home/tester/Desktop/siteRootDir/content
WSGIScriptAlias /c /home/tester/Desktop/siteRootDir/deploy/site.wsgi
When I run apache and go to localhost/c I was getting the (13)PermissionDenied error in the apache log. To get around that error, I (admitedly stupidly) ran
chmod -R 777 /home/tester/Desktop/siteRootDir
I know that is not the way to deal with the issue, but I just wanted the site to work so I can continue its development.
So my question is, what are the correct permission settings to the siteRootDir directory and its sub-directories such that the site will run and I do not expose unnecessary files in the directory.
Also, I realize that this is not an ideal set up and I will likely run into problems when I deploy the site in production. Can anyone please suggest a better organizational approach to this?
Thanks!
The tightest permissions possible would be 0600 for files and 0700 for dir's and as a owner the user owning the apache processes. This user differs per OS and flavor (e.g. for OSX it's www, for Debian/Ubuntu it's www-data).
This would probably too tight for a development server. At least would you like to be able to modify all your files through your IDE of text editor, so either you should add ACLs for yourself (i.e. the user that edits the Django files, templates and static files).
Also, in a production server you want the apache user to be able to write to directories that hold web uploaded content. That would be somewhere in your static files section (or on a different dedicated static files server).