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
I am looking to stand-up a development/test WordPress website in Azure alongside our production site and am looking for any best practices I can find.
The idea is to keep the environments the same having both sites on the Azure PaaS but having different URL's to be able to access them. And having the databases be separate (to ensure we don't mess up anything in production)
Example...
Production -- http://companywebsite.com
Development -- http://test.companywebsite.com
Has anyone attempted something like this before? It would be fairly simple if the development was being done locally but we need multiple (non-developer) users to be able to access the WordPress admin panel on the test site and be able to install plugins and such to test.
Thanks in advance!
have you tried deployment slot?
When you deploy your web app to App Service, you can deploy to a
separate deployment slot instead of the default production slot when
running in the Standard or Premium App Service plan mode.
https://azure.microsoft.com/en-us/documentation/articles/web-sites-staged-publishing/
Update:
Seems like you can also config wordpress to aware of staging environment.
http://www.wpbeginner.com/wp-tutorials/how-to-create-staging-environment-for-a-wordpress-site/
I currently have a website running on Windows Server 2008 with MS SQL Server 2008 Web Edition.
I want to host a blog, tightly coupled to the site, and after reading a good few articles, decided that I would like to install WP in a folder off the website root, accessible like this?
http://www.mysite.com/blog
I've just upgraded to Web Platform 4.6, and this has returned a few different options with regard to installation. Here's what I have:
Standard WordPress installation
Brandoo WordPress
WebMatrix3
WordPress itself is not familiar (apart from using it of course), and wondered if anyone could shed any light on these options.
Brandoo Wordpress uses MS SQL or Azure SQL by default. If You want to install WordPress winth thos DB's, use Brandoo WordPress.
Read here and here. Since this is essentially a fork of Wordpress, security updates and whatnot may be delayed. To use the official Wordpress code, you'll have to install MySQL.
I’m looking for a way to build web site which uses PostreSQL to store web pages and allow users to modify them.
Admin user should able to create and changed pages using html editor from browser.
Site runs in Debian Squeeze x64 VPS using Apache. There are already Mono 2.8 and PostreSQL 9.1 applications running in this VPS.
There is no PHP installed but it can probably installed if software requires this.
Maintaining MySql in addition to PostreSQL in same server may be not reasonable so I'm looking for a way to use Postgres.
CMS should provide nice dark theme for web site so that web designer is not required for this.
WordPress PostreSQL plugin page http://wordpress.org/extend/plugins/postgresql-for-wordpress/
states this this plugin is not compatible with latest wordpress.
Also this plugin is not updated for a while.
Joomla! does not run in Postgres DBMS.
Drupal 7 seems to support it but comparing to WordPress Drupal usage is smaller.
There are mono ASP.NET applications running in this site so using some ASP.NET CMS seems best.
Latest Orchad does not run in Mono and PostgreSQL.
How to use latest WordPress with PostreSQL 9.1 ?
Which CMS software is best for PostreSQL?
Maintaining MySql in addition to PostgeSql in same server may be not reasonable
I'm not a professional sysadmin, but I'm not sure that's true. Here is a Server Fault question where it is claimed that operating both in parallel works fine: https://serverfault.com/questions/35934/installing-and-running-mysql-and-postgresql-8-4-side-by-side
mySQL is the quasi industry standard in the PHP world, so the biggest products all use it, and in the case of WP (and most others), it's the only database suppored. Adding Postgres support as a requirement seriously limits your options, so installing mySQL side-by-side with Postgres may be a good idea.
That said, Drupal is a perfectly fine, well-esteemed CMS framework and if its features and architecture work for your purposes, there is no reason not to choose it.
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?