this might sounds silly but I am super confused.
I want to install drupal on localhost but I need to install a SQL database for it too.
Which database package do I get (for free) ?
I went to MySQL website but I do not understand which one I need to download, or if mysql at all.. ?
I have win 7 32 bit and I only care that drupal is installed on my machine and for me to see, don't care about outside world, don't want to webhost.
I found an excellent video on installing Drupal on your home windows machine for personal use. It uses XAMPP and it works GREAT. XAMPP installs and configures WAMP environment for you, one click, no hastle. Wow, this made everything so simple and easy, one click! (and a very long wait for file extraction XD )
If you just want to get Drupal up and running, you should take the Aquia stack installer, it will install all the things you need, so you want have to deal with the fuss of installing MySQL and all the other things needed. It only works for 32 bit windows, but that's no issue for you.
Edit to clarify mac's misunderstanding
Aquia stack installer installs what acquia calls DAMP. Drupal Apache MySQL PHP. It also installs phpmyadmin and few other things. The perfect 1 click drupal install on a clean box.
Aquia Drupal is a package including Drupal core and the most used contrib modules like CCK, Views, Date and many more. This package is tested to make sure all modules integrate and if a bug is introduced in a module they will usuallly either fix it or use a bugfree version. This is like a normal drupal install and requires a stack like WAMP, LAMP, MAMP or alike.
Acquai is started by Drupal's creator, so their staff has some of the best Drupal experts.
Download the mysql community server.
http://dev.mysql.com/downloads/mysql/5.1.html
You should look at a tutorial to install Drupal because you'll need also a web server(Apache) and php.
Good luck!
Related
I am developing a modue for a DNN website and i would like to make a little tool that is able to perform the installation process without having to go trough the CMS and install it with the extension installer.
This would probably be a lot faster. For this i need to know all the steps the installation follows and convert this to code. However Google does not seem to help me out here so far.
Does anyone have any information or code regarding this?
Read this and the referenced links:
http://mitchelsellers.com/blogs/2009/10/14/dotnetnuke-bulk-extension-installation.aspx
Might anyone be able to tell me how to uninstall CakePHP 3.0 from a Windows 7 machine? I have searched their docs and the Web--CakePHP's forum is on FreeNode which seems like it would take all day to figure out how to use. I installed it in the wrong place (not under XAMPP, but parallel), could not find how to uninstall it so re-installed it in the right place (htdocs), but the new installation is corrupted with missing files. I would like to take it all out and start over.
I am working on consolidating DNN portals from various versions of DNN to the newest install I have at this time.
How do I take a DNN portal on DNN 5 (or even DNN4) and import into a DNN 7.3 host? Will the skin be supported? break? content? These are mostly content-rich portals so i want to move the portal content and skin over to the new host so its easier to maintain and have fewer installs that are outdated. Please let me know
This is not something that will be easy to do. You'd probably be best served by doing the following.
Backup the DNN 5 site (files and database)
Restore the backup to a new IIS website/database
Upgrade that DNN 5 site to 7.3
Export a Portal Template from the upgraded site
Import that portal template into your production 7.3 environment.
Even that won't be guaranteed, you'll likely have modules that won't work, and the skin almost definitely won't work.
I would simply upgrade the site to 7.3 and fix what is necessary myself.
I think that you have to do step by step. First backup both the code and the data base, after that upgrade to the last version 5.x, then to the first stable 6.x then to the last stable 6.x then to the first 7.x and then to the 7.4.
Good luck
As Chris said "Even that won't be guaranteed, you'll likely have modules that won't work, and the skin almost definitely won't work.
I would simply upgrade the site to 7.3 and fix what is necessary myself."
A tutorial suggest the best way to install Drupal is to install the acquia drupal stack but I already have wamp installed. I don't know if I should remove wamp( I don't know how best to do that) or have them both installed or what. I currently have mysql 5.5.24 and php 5.3.13.
Drupal is a web-application composed of PHP scripts that access MySQL. WAMP is a platform that runs PHP scripts using Apache and MySQL.
So it's up to you if you want to use a general WAMP stack such as Xampp, WampServer, or Wamp-Developer Pro, create a website with it, and install Drupal in that website... Or if you want to use a specifically tailored WAMP distribution that already comes with Drupal pre-installed.
Both have their upsides and downsides. Using Acquia Drupal stack might be quicker, but there will be more general options available otherwise with Wamp-Developer or Xampp.
One is geared for a very specific use, the others for many uses.
i want to build a website in dnn 5. i have studied dnn5, its installation, starter-kit installation, built-in modules (both of Host and Admin), installing a custom module (from module extension), creating packages.
I had rather still some doubts left in my mind.
1.How should i progress if i need to built my custom module in some new website (& not in dotnetnuke.com website)
2.How is deployment done at client side? Is it done by creating packages or what, i dont know.please suggest some possible solution
3.I want to create a document module to satisfy my client requirements. This module is already built by dotnetnuke.com as an extra module. What should be done to include this module in my new website so that only my requirements could be reflected instead of creating the module entirely from scratch?
thanks
I'm not entirely sure about what you're looking to do, but I'll answer as much as I can.
I would suggest setting up a DotNetNuke website on your local machine, using the Source package. You can then create a new module (starting it either through the website itself, or by using a Visual Studio template). I strongly suggest using a Web Application Project for the module, keeping it in the website's DesktopModules folder (so that you're only dealing with the module's code, and don't have the entire website open in your project). Also, make sure you use the module and any other extension points to implement your functionality, rather than making changes to the actual DNN core code (since any changes to the core will make it that much more difficult to upgrade to newer versions of DNN).
I strongly suggest getting some automated packaging in place (the template that I linked to has a NAnt build script with it that you can use to package your module). It is so much easier to deploy modules as installable packages than trying to migrate individual files.
You can get the source version of the Documents module from its Codeplex project. It's licensed under the MIT license (like DNN itself), so you're free to use it as a starting point for your own module. Just download the source package and install it into your development site. The install will include all of the source and also includes a Visual Studio project that you can use. After installing, I would suggest that your first step be to rename the namespace (so that you're differentiated from the core module).
UPDATE
To deploy the website, I would suggest installing DNN on the server using the main DNN Install package. Then, once that is installed, you can install the module into the website using the package that you have created. A default installation of DNN will only have the Text/HTML module, in addition to administrative modules, so you shouldn't have very many extra, unused functionality present in the site.
Leave me a comment & update your question (or start a new question) if there's anything else you need to know.
It sounds like you are looking to use DotNetNuke as a development environment to write code that won't be deployed in a DotNetNuke site. While I love DNN, there's absolutely no reason to do this. Only use DNN for developing DNN stuff.
To address point #1, if the functionality you want is somewhere else you could use an IFRAME module. Check out: http://www.dotnetnuke.com/Community/Extensions-Forge/view/ProjectDetail/project/dnniframe.aspx