can I easily move my drupal installation from Apache to Microsoft server, or I do need to run the install.php script and reinstall all modules ?
I'm having troubles to connect it to the database, that's why I'm asking. (I get technical problems without specific error messages)
thanks
The technical differences you will encounter are the ones between Apache and IIS. For example, there is no mod_rewrite in IIS, you have to get ISAPIRewrite to play along. You also need the Windows Server to be running MySQL. You may also have .htaccess pathing issues.
Related
I am trying to create a web server with XAMPP to host an ASP.NET website. However, I am unable to do so. As I understand it, ASP.NET apps cannot be served out-of-the-box with XAMPP. I have found that in order to get Apache to work through XAMPP that mod_aspdotnet needs to be installed and configured. I am following the instructions for mod_aspdotnet by Shehroz Kaleem at https://xehroz.tumblr.com/post/43884721903/how-to-run-aspnet-on-xampp, but I am running into issues. First off, the current version of mod_aspdotnet (https://sourceforge.net/projects/mod-aspdotnet/files/latest/download) is in a zip file that does not include an installer inside of it (or at least, I can't find one). This makes installing it a problem. So, in order to fix that issue, I have resorted to attempting to use the previous version (2.2.0.2006) that is not a zip file, but a directly installable .msi. The problem with this installer, however, is that it does not recognize C:\xampp\apache as a "valid path to an installed instance of Apache." This install location from XAMPP is suggested in the aforementioned instructions by Shehroz Kaleem. Does anyone have any experience setting up a web server for ASP.NET using XAMPP? Is there something that I am doing wrong?
I have planned to learn WordPress. I just want to know what will be core difference between functionality and features if I install it on WAMP that is local host and a web server?
My preference was WAMP but I am not yet sure.
When doing web development on your local machine using a localhost, there are a few things you need to be aware of.
You need to ensure that it is same as the versions of the products on your actual web server or close to it (MySql, Apache, Php, etc.)
You need to be aware of the urls you use compared to the urls when deployed to the server (in Wordpress, you need to edit the main web urls in your mysql dump file before uploading to your webhosting)
WAMP actually is easy to configure, other alternative is XAMPP for local development
Wordpress updates a lot and usually so is there requirements, so in order for wordpress functions to work properly, your local server must be updated to their requirements or at least close to it
This may be the dumbest question but I have a small problem I am using windows7 and recently I had an issue with my outlook as a result I had to recreate my profile on windows.
since that moment I can't see IIS7.5
I have also tried to use control pannel add windwos feature and I can only find IIS6
The strange thing about this is that I have files hosted in IIS7.5 and when I browse to the web Url(I use custom host) I can go there but creating a new website is impossible as I can't go to IIS 7.5
also browsing to Localhost gives me the indication that IIS7 is installed
What can I do?
I have tried also using the script from Microsoft site link but that wasn't successful and I am wondering what to do really.
also when I type Localhost on any browser I get the big image with IIS7 on it what suggest it is installed.
Just today using manage mycomputer(Win 7), service and application and restarted the IIS Admin service and now I can see the IIS7.5 as per the , but not sure why I can't see it in the accessories on when I do a search for IIS
Thanks
You could always download IIS 7.5 express from Microsoft
There is a similar post in super user forum discussing about the posted issue.
https://superuser.com/questions/752946/iis-manager-disappeared-from-start-menu-and-administrative-tools
Copied from there:
Your system is behaving in an abnormal manner, and it is hard to diagnose that error. It seems like it is caused by some system corruption.
The following tools can diagnose and fix errors in Windows :
sfc /scannow
Scans the integrity of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible.
System Update Readiness Tool for Windows
Scans for Windows corruption errors that prevent Windows updates and service packs from installing.
Windows 7 Upgrade Advisor
Scans hardware, devices, and installed programs for known compatibility issues, giving guidance on how to resolve potential issues found, and recommends what to do.
Windows Update fixit or Reset Windows Update components
then try again to turn off the IIS Windows feature, reboot, reinstall, reboot.
Full antivirus scan by your current product and in addition at least Malwarebytes Anti-Malware.
If running these tools gives no hint as to the problem, the next step is a Repair Install to Fix Windows 7, which fixes the current installation of Windows while preserving user accounts, data, programs, and system drivers.
The last resort, to reinstall Windows from scratch, is not to be taken lightly unless really necessary.
I am just trying to get node and websockets running alongside an ASP.NET MVC project.
I am running on Server 2012, IIS8, latest node.js and iisnode. Websockets are enabled for IIS and .NET 4.0 MVC project runs fine. Also, I can run websockets on node independent of IIS just fine (on a separate port).
I downloaded the faye websocket and the dante example project and installed it.
When I do not have websockets disabled, I get
Unable to establish WebSocket connection to ws://localhost/dante/server.js
When I disable websockets, whether in dante or wwwroot, I get
This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
I tried to specify overrideMode="Allow" in the wwwroot webconfig and that didn't seem to work.
I have also tried removing the wwwroot web.config and it seems to make no difference. I also tried turning off the firewall on the server (just for kicks) and that didn't change anything.
Thanks for any help and assistance. I am open to using anything (socket.io, for example) but would like to keep running ASP.NET MVC and node on the same port to eliminate firewall issues and prevent having to use multiple servers/domains/etc.
EDIT:
Running
c:\windows\system32\inetsrv\appcmd.exe unlock config -section:system.webServer/webSocket
Made the IIS error go away, but now I still receive this:
Unable to establish WebSocket connection to ws://localhost/dante/server.js/ws
WebSocket connection is closed.
I've opened an issue here.
EDIT 2: I had installed iisnode from the Web Platform Installer. Apparently, the version from WebPI is old. I needed to get the latest from the github site here under Installing for IIS 7.x/8.x. Once I installed the latest version, IT WORKS!
This is fantastic! Thanks to tjanczuk! :)
iisnode added support for websockets starting from version 0.2.0. Make sure you install the latest iisnode using links from https://github.com/tjanczuk/iisnode.
Can WampServer be used successfully in production? Is this a bad idea?
So everyone knows, and I don't see how this mattered, we've paid for a windows dedicated box and we have existing IIS apps. We just wanted to use a PHP based CMS which installs easier on apache (since it has some dependencies). So, as the title indicated, windows, apache, php, and mysql are requirements.
Additionally, I'm talking specifically of the WampServer flavor of WAMP.
If you're not going onto the internet, there isn't any reason really not to. Of course you'd have to look at all the normal caveats - backups etc.
Instead of using an already made one, why not try to do your own? It would be a good learning experience and really they aren't that hard to get working together.
WAMP is approriate for production of an Intranet. We developed a solution with FLEX (front END) /PHP/MYSQL (BACKEND) and it's been working very well for a year now. You just have to secure the Server on which WAMP runs. WAMP is just a tool for configuring APACHE/PHP/MYSQL on a Windows plateform with ease.
WampServer themselves says they are not appropriate for production, only for development. Security issues, load balancing, etc., are definitely part of it... plus, deploying Apache on Windows is just a nightmare.
Use LAMP. Alternatively, use IIS... if you're going to deploy a Windows production server (don't), use IIS.
LAMP is more stable, but i have wamp running intranet-sites succesfully in two organisations with over a 1000 users.
I don't see why not, but why use Apache on Windows when you can quite easily install PHP on IIS?
I love how the only guy who answered the actual question by paying attention to the fact that the OP was asking about the all in one product that is WampServer has a -1 rating. To reiterate what he said though, yes it would be a bad idea to use it in a production environment.
I'm using WAMP over Windows Server 2003 as a production server for an Intranet. accesing MySQL and SQL Server toghether.
We are not too many users, but I had no problem so far.
Easy configuration, easy maintenance, posibility to autenticate domain users in Apache...
Perhaps with heavy load environments it's not so good, but for me is the perfect sollution by now.
YES, it can be used in production under condition that you install the secure WAMP distro. And yes it can run on Internet and not just intranet.
Here is a link to a secure WAMP for production where you can customize the security level and other settings to suit production environment.
http://securewamp.org/en/
Windows and WAMP can be successfully used in production even on high traffic websites however you will need to make changes and switch from mod_php to FCGID.
Why not just use LAMP? PHP code is portable. I used WAMP for development, LAMP for production.
WAMP would probably work for production, but why not just use LAMP?