Seasonal greetings to you all,
I'm new to moodle and have created a moodle site (version 3.3.2) on a local windows 7 machine. I now have to demo the site to 30 students as part of my final project at uni. How do I migrate the site from a windows machine to say a virtual windows machine that the student can all access?
Moodles own site seems to just cater for Linux machines so its not much help
While the command line examples may be Linux specific, the steps on https://docs.moodle.org/34/en/Moodle_migration are relevant whatever your OS
1.1 Turn on maintenance mode *(front end UI)*
1.2 Backup the Moodle database on the old sever *(can be done in phpmyadmin or mysqlworkbench or whatever other relevant database management software you use and depending on the database you are using)*
1.3 Restore the database backup to the new server *(as above)*
1.4 Copy moodledata from the old server to the new server *(while rsync is a useful tool, this can be done with any copy/paste tool or ftp etc - just be prepared to take time if you are copying between servers or via an external medium)*
1.5 Copy the Moodle code from the old server to the new server *(as above - copy/ftp or just reinstall the code and then copy your config.php)*
1.6 Update config.php with the URL of the new server
1.7 Test the copied site
1.8 Update links containing wwwroot in the database *(you may want to do this as part of the migration above - using a search and replace on the text of the export before re-importing it)*
1.9 Take the site out of maintenance mode
Related
Downloaded source package of DotnetNuke and I am new in dotnetNuke. Can anyone help me to clarify the process of installing DotnetNuke.
I am following this Install DNN
I've got a tutorial on installing DNN8 found here.
You can also follow this text tutorial
Setting up your development environment can vary based on what your
end goal is. If you are doing module development for your own use, and
within your own DNN environments, you can ignore a few of the settings
below. If you are doing module development with the idea that you
might turn around and give the modules away, or sell them, then you
will likely want to follow the guidelines set forth below to support
the widest array of DNN installation environments.
I recommend that each developer have their own local development
environment, with a local IIS website running DotNetNuke, and a SQL
Server 2008/2012 (not express, though you can use it) database for the
website. Having an individual development environment makes group
module development far easier than if you share
environments/databases.
Choosing a DotNetNuke Version Choosing a version of DotNetNuke is
important when you start your development for couple of reasons. For
modules that you are developing for yourself, you need to ask, what is
the minimum version of DotNetNuke that you have in production. Are you
running DNN 5.6.1? Are you running 6.2.6, 7.0.0, 7.0.6? Based on the
answer you can determine what version of DNN you should setup as your
development environment. You shouldn't be developing on a newer
version of DNN than what you have running in production. As with
everything there are ways around this, but I am not going to go into
the details on that in this tutorial.
As a developer working to create modules and release those, you might
have production sites that are running on the latest and greatest
version of DNN, but what about your customers? Or your potential
customers? You have to ask yourself, do you want to provide support
for really old versions of DotNetNuke? From a development perspective
you will probably say no, but from a business perspective, you might
say yes, and here’s why. Not everyone upgrades DotNetNuke websites as
they should, and often times you will find that some people never
upgrade. While I don’t advise taking that approach to managing a
DotNetNuke website, it is a fact of life that people don’t always
upgrade and there are thousands of people, if not tens of thousands,
that have sites that aren’t running on the latest version of DNN. You
should take that into account when you are doing your module
development, if you compile your module against an older version of
DNN then your module should run on newer versions of as well, for
example. If you compile your module against DotNetNuke 6.2.6 it will
likely run on every version of DNN released since then. Though there
are extended cases where this won’t always work, DNN strives to
maintain backwards compatibility, this isn't always possible.
You might also want to use features that are only available starting
with a specific version of DotNetNuke, such as the workflow
functionality found starting in DNN 5.1, in that case you may choose
not to support older versions of the platform out of necessity. This
will minimize the market in which you can sell your modules, but also
can make for less support and an easier development cycle due to the
features that DNN provides.
Choosing a Package Now here’s one that may baffle you a bit. I’m going
to recommend that you use the INSTALL package for whatever version of
DotNetNuke that you download. What? The INSTALL package? What about
the SOURCE package? Well you can use the source, but you don’t need
it. The module development that I’m setting you up for doesn't require
the DNN source, and using the INSTALL package makes your development
environment cleaner. We aren't going to be opening the DotNetNuke
project when we do our module development, so why have the files
sitting around for nothing? Also, if you've ever tried to use the
SOURCE package for anything, you'll know it isn't easy.
The steps for setting up your development environment will apply to
both the Community and Professional editions of DotNetNuke.
Installation Configuration Once you have the version selection out of
the way you can go through the installation process. While I’m not
going to walk you through the minutest of details of each step of
installing DotNetNuke in this post, I will at least try to point you
in the right direction for each step.
Download the INSTALL package of the version of DotNetNuke you want to
use in your development environment.
Extract the files in the INSTALL package to a location of your
choosing, this location is where you will point IIS (the web server)
when we can configure the website. In my environment I typically use
c:\websites\dnndev.me\ (One item of note: you may need to right click
on the ZIP file and choose Properties before extracting, on the
properties window if you have an UNBLOCK option, click that. Some
versions of Windows have started blocking files within the DotNetNuke
ZIP files, which will cause you problems later during the actual
install.)
Setup IIS IIS is the web server that comes with Windows computers. DNN
7 requires IIS 7 or later (7,7.5,8.0), so you will need at least
Windows Vista, Windows 7, Windows 8, or Windows Server 2008 R2,
Windows Server 2012.
In IIS you should create a new website (Note: If you use an existing
website in IIS be sure to add the HOST binding for DNNDEV.ME), and
point to the folder where you extracted the INSTALL package.
Note: With DotNetNuke 7.0+, .NET Framework 4.0 is required, so be sure
that your application pool is configured to run under 4.0, and not
2.0.
Set File Permissions Setting up the file permissions for your DNN
install is often the step that causes the most trouble. You should
right click on the FOLDER in which you extracted DNN
(c:\websites\dnndev.me) and choose properties. Choose the Security
tab. You need to add permissions for the account in which your
website's application pool is running under. You will want to setup
the permissions to give the account Full or Modify permissions for the
DNNDEV.ME folder. Which account you will use will vary based on your
version of IIS, here’s a simple list of some of the default accounts
based on the version of IIS.
IIS Version Operating System Account IIS 7 Windows Vista, Windows
Server 2008 localmachine\Network Service IIS 7.5 Windows 2008 R2,
Windows 7 IIS AppPool\APPPOOLNAME IIS 8 Windows 2012, Windows 8 IIS
AppPool\APPPOOLNAME
Note: If you are using IIS7.5/8.0 you’ll notice in the above table
that we have APPPOOLNAME in the identity, this is because when you
setup a new website in IIS a new application pool is created. In place
of you should type in the name of the application pool that was
created. You can also bypass this and configure your application pool
to use the Network Service account instead of a dynamic account if you
would like.
Database Configuration In SQL Server you should go through and create
a new database. I always create a database with the same name as the
website, so in this case DNNDEV.ME. Once you have created the
database, create a user that can access that database. I always use
SQL authentication, turn off the enforce password requirements, and
give the user DB Owner and Public access to the DNNDEV.ME database.
Remember the username and password you create here as you will need
them when you walk through the Installation screen for DotNetNuke.
DotNetNuke Installation Screen Populate the installation screen with
the standard DNN information, Host username, password, etc. For the
Database option, choose Custom and configure your database connection,
providing the Server IP/Name, the Database name (dnndev.me). For the
database authentication you'll want to choose the option that allows
you to enter the username/password for the database user that you
created previously.
Now there are two additional options you can configure, normally I
would tell you not to modify these, but from a development environment
perspective I do recommend that you change the objectQualifier
setting. It should be blank by default, you should type in “dnn”
(without quotes), this will prepend “dnn_” to all of the objects that
get created by DNN such as Tables and Stored Procedures. This is not
something I recommend from a production stand point, but if you are
developing modules for sale, then supporting objectQualifier in your
development is recommended. It will save you time down the road if you
have a customer who has an objectQualifier defined on their production
databases.
Follow the following video and it has total two parts one and two part links are givenbelow
Part one
Part two
I'm extremely new to building websites. I'm attempting to create a website using Joomla (and a Joomla template) and plan to use a webhost, bluehost.com. Do I still need to download XAMPP if I'm using bluehost? What's the point or use of XAMPP?
No, you don't need it. The likes of Xampp and Wamp are offline development environments that allow you to develop on your computer/localhost. So rather than making any changes to a live website that might result in the site breaking, you can simply take a backup, set it up on your localhost and testing your changes there. Be sure that you configure your localhost to use the same server settings as your live host as there might be some potential differences that may prevent things from working.
Seeing as you're new to web development, my advice would be to set up a local environment using either Xampp or Wamp, build your site on there, then move it to your live host when you feel ready to.
Charette,
Just have Bluehost install joomla for you. Install the free Akeeba backup yourself, and then start playing around with the demo content.
http://www.bluehost.com/joomla
Ask specific questions in the joomla forum:
http://forum.joomla.org/
Have fun
Trying to install Redmine on Windows 8 on this tutorial. Getting this errors:
Tried Bitnami's installer too, but I already have IIS Web Server and don't need the bundled Apache webserver. The installer doesn't give me to choose it's components. It installs Apache by default. So, Bitnami's Redmine is not for me.
What am I missing?
Is there any other good bug & request tracking software? Please don't Google and advise me to some random results. Advise something that you used and really good as Redmine
Once you get the error above, make sure that new WebSite's AppPool has write access to site's folder on the harddrive to complete the install process.
Then open the website in a browser and the installation will complete.
Set security accordingly after the install completes.
Use WebIssues multi-platform bug & request tracking software that fits all your needs instead of Redmine.
WebIssues is an open source, multi-platform system for issue tracking and team collaboration. It can be used to store, share and track issues with various attributes, comments and file attachments. It is easy to install and use but has many capabilities and is highly customizable.
Main features:
The Desktop Client application can run natively on Windows, Linux
and OS X
The Web Client can be used to access the system using a web browser
The server can be installed on any host with PHP 5.2 or newer and
MySQL, PostgreSQL or SQL Server
Issues can be filtered using public and personal views with
configurable filtering criteria
Email notifications can be sent and the Desktop CLient can
periodically check for new and modified issues meeting various
criteria
Various reports can be printed directly from the Desktop Client or
exported as HTML and PDF documents
I have recently installed subversion and nginx server on my machine (macbook pro). I'm fairly new to subversion as a whole and have just built a single webpage through this version control system, and now I'm faced with the task of testing it in all of the relatively modern web browsers. My biggest concern, as far as browser compatibilty is concerned, is Internet Explorer which, in order to test, I need Windows. I have Windows 7 installed on my mac via Virtual Box, and herein lies my problem.
I have not committed the new page I've just created to the repository, by the request of the client. Because of this, as far as I know, I have no URL to use for testing in IE Tester, Firefox for Windows, etc. How can I test this 1 page site's browser compatibility with without having committed any changes to the repository?
I can test it easily on my machine using MacOS, by just typing in local.*.org and it shows up. Again, windows is my issue. This project is due this Thursday (5/24/12), so you're help is greatly appreciated.
1) Developing and testing your web page is different from managing your web page source. In other words, testing web pages != using SVN.
2) If you've not actually been able to use SVN yet - and if your client has no preferences - then please try TortoiseSVN:
http://scplugin.tigris.org
3) Please post back any specific questions you have about installing/using SVN.
If the site uses any scripting languages like PHP, and/or databases, you need to get those setup correctly first. If your website consists of just HTML/CSS/JS... then you can access the website via either of these methods:
Enable Web Sharing (System Preferences > Sharing > Web Sharing). Then type in the IP shown there into your browser in VirtualBox and it should load. (This is probably easier than trying to get nginx configured, though it might very well load if you just type in your machine's IP.)
In VirtualBox, select your VM (powered off), Settings > Shared Folders. Add your website's root directory. Launch the VM, then browse to it within the VM and open up your files there for testing.
My current environment is setup like this:
- Local dev machine with git & SVN
- Remote DB server
- Remote web server
- Web server mounts local dev machine's www folder as a volume and serves the PHP pages from there
- Load web browser in VMs or any other machines. Edit hosts file if need be for local routing.
I am trying to install Moodle 1.9 using XAMPP on a virtual machine running Windows Server 2008 Enterprise edition.
I can initially access the install.php installer script fine but after I progress past the third page the webpage times out.
If I go to http://localhost/, no webpage is downloaded and the browser just times out.
I have tried to run the install script with IE7 and Chrome to see if it was a browser problem, but the same thing occurs.
Any help would be greatly appreciated.
Thanks,
Ashley
Windows servers are notorious for causing problems with Moodle installations. Here's a few things to try:
Check the dirroot is set correctly your config.php file. Windows requires complete, absolute file names.
Has the failed install created some/all database tables, and populated them? If only some, look for the last successful table, then check for any corrupted or modified code related to that table that could be causing the install to hang. E.g. is the last successful table is forum, check your mods/forum files. It might be worth downloading a fresh weekly build of Moodle.
Your mysql memory_limit might be set too low (Moodle Docs recommend at least 40mb for Moodle 1.8 and higher).
Is this an upgrade, or a clean install? If it's an upgrade, don't try jumping too many versions, and (if possible) uninstall any third-party modules or activities that might cause trouble whilst updating the tables.
There's lots more info in the Moodle Docs, particularly:
http://docs.moodle.org/en/Unexpected_installation_halts
http://docs.moodle.org/en/Installation_FAQ