https://docs.moodle.org/37/en/api.php?action=feedcontributions&feedformat=atom&user=Colchambers 2026-04-18T20:26:55Z User contributions MediaWiki 1.43.5 https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=52049 2009-03-05T08:59:38Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle_Create_Installer|Creating an Offline Moodle Installer]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle2/course/view.php?id=22 as a central place to find out about current developments and get involved in the development process.<br /> <br /> I've just come across this fascinating article by Adobe on the [http://www.adobe.com/devnet/devices/articles/mobile_ecosystem.pdf current mobile environment]. The environment is constantly evolving and this is quite a recent and in depth exploration of the topic. I discovered it while reading about [http://www.jolongo.org/ Jolongo], another [http://moodle.org/mod/forum/discuss.php?d=98877#p437085 Offline Moodle] being developed by a team in Latin America.<br /> <br /> ==Why do we need an offline version of Moodle?==<br /> There are many opinions for and against an offline version. I put some of my thoughts into a blog article to put my thoughts in print and invite comments. <br /> http://colchambers.blogspot.com/2008/06/is-offline-moodle-really-worth-hassle.html<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=49373 2009-01-26T09:33:52Z

<p>Colchambers: /* Create the Database and Assign a User */</p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> This article is designed to help you replicate the Offline Moodle Environment that is being used within Offline Moodle. Currently we have focused on distributing to machines using the Windows operating system. In time we expect to add advice for other operating systems. We have tried to cover everything that's required to setup the entire environment so that this process it as simple as possible.<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> First of all you need to create an environment that meets the basic requirements of Moodle. This includes:<br /> * A web server: To server internet files<br /> * A database server: To handle data records<br /> * A PHP distribution: Moodle runs under php so you need this installed. <br /> <br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> <br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues<br /> <br /> ===Portable Menu===<br /> The latest addition to the mix is to provide a portable menu system(Pegtop PStart) that provides easy access to key components of Offline Moodle. Thanks for identifying this feature go to John Attwood and Pete Simson who have been developing his own Portable Moodle application similar to Offline Moodle. You can read more at [http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141 http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141].<br /> <br /> Again the xml config file the portable menu creates is too large to add here. The links are extremely easy to create within the menu itself and you'll probably want to customise it to your needs.<br /> <br /> The main links we have included so far are:<br /> * readme: links to readme.htm<br /> * Offline Moodle: Links to the Offline Moodle.url shortcut created earlier<br /> * Start Offline Moodle: Links to the file xampp_start.exe <br /> * Stop Offline Moodle: Links to the file xampp_stop.exe <br /> * Reconfigure Offline Moodle: Links to the file setup_xampp.bat <br /> <br /> We also added a group named 'resources' to contain links to extra components that may come in useful such as:<br /> * Restart Offline Moodle: Links to the file xampp_restart.exe<br /> * Is Offline Moodle Running?: Links to the file xampp-portcheck.exe</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=38076 2008-06-23T09:22:16Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle_Create_Installer|Creating an Offline Moodle Installer]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> I've just come across this fascinating article by Adobe on the [http://www.adobe.com/devnet/devices/articles/mobile_ecosystem.pdf current mobile environment]. The environment is constantly evolving and this is quite a recent and in depth exploration of the topic. I discovered it while reading about [http://www.jolongo.org/ Jolongo], another [http://moodle.org/mod/forum/discuss.php?d=98877#p437085 Offline Moodle] being developed by a team in Latin America.<br /> <br /> ==Why do we need an offline version of Moodle?==<br /> There are many opinions for and against an offline version. I put some of my thoughts into a blog article to put my thoughts in print and invite comments. <br /> http://colchambers.blogspot.com/2008/06/is-offline-moodle-really-worth-hassle.html<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=37220 2008-06-09T09:55:30Z

<p>Colchambers: /* Where can I find out more? */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle_Create_Installer|Creating an Offline Moodle Installer]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> I've just come across this fascinating article by Adobe on the [http://www.adobe.com/devnet/devices/articles/mobile_ecosystem.pdf current mobile environment]. The environment is constantly evolving and this is quite a recent and in depth exploration of the topic. I discovered it while reading about [http://www.jolongo.org/ Jolongo], another [http://moodle.org/mod/forum/discuss.php?d=98877#p437085 Offline Moodle] being developed by a team in Latin America.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Installer&diff=37039 2008-06-04T14:19:52Z

<p>Colchambers: </p> <hr /> <div>To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> =What You’ll Need=<br /> <br /> Firstly you'll need an Offline Moodle environment to go inside your installer in the first place. For details on how to create one check out [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]].<br /> <br /> Once you have a working environment you want to begin creating a distributable package, the installer. The easiest way to do this is to use a ready made tool that'll create the installer for you. The best we've found that's free is the [http://nsis.sourceforge.net/Main_Page NSIS installer] since it provides a customisable installer package that runs on the windows platform and it’s free. It’s very easy to create an installer using the wizard provided in the nsis edit at http://hmne.sourceforge.net/ <br /> <br /> =Creating an Installer=<br /> Ok, you should now have a working Offline Moodle environment. The next step is to package it up and distribute it. <br /> <br /> First you have to decide on the installer you want to package this up with. We chose the NSIS installer from Nullsoft because it’s highly configurable and it’s free. Unfortunately it only works on windows.<br /> <br /> ==Creating an NSIS script==<br /> Once you have installed the nsis editor go to ‘file\new script from wizard’ click next <br /> <br /> ===Application Information===<br /> then enter the request values. Note that the Application Website field will be used to create an internet shortcut and placed in the same folder as Offline Moodle. It will have the same name as the Application name. We already have an internet shortcut named Offline Moodle that points to http://localhost/moodle which takes a user to Offline Moodle on their machine. So you might want to leave this empty to avoid overwriting the current file.<br /> <br /> Click next<br /> <br /> ===Setup Options===<br /> Leave all settings at default. Setup file can be something like Offline Moodle Setup 0.3.exe<br /> Setup Lang defaults to English<br /> <br /> Click next<br /> <br /> ===Application directory and License===<br /> Leave with default values except for license file. We use the apache license file at xampp\licenses\apache\LICENSE.txt in the absence of a specific file for Offline Moodle<br /> <br /> Click next<br /> <br /> ===Application Files===<br /> This part takes a while because we can’t find away to import all the necessary files without letting the nsis installer run through each one. This can take quite a while. <br /> <br /> Delete the two example files using the x (Remove file) icon above the file window. Then click the add directory tree icon. It will open a dialogue box titled EditDirectory<br /> <br /> Enter the path to the xampp folder containing the xampp and moodle installation you wish to use (Copy and pasting from windows explorer is easiest I find). Leave the defaults and click ok.<br /> <br /> The dialogue box will then close and begin importing the many files necessary into the install script you are creating. The program will look as if it is not doing anything and has hung but check your hard drive activity light and you should see a lot of activity. <br /> <br /> Once all the files have been imported to the script the file area will list all the files included in the xampp install.<br /> <br /> Click next<br /> <br /> ===Application Icons===<br /> Enter the Application Start Menu Folder Name.<br /> <br /> Leave the defaults. <br /> Remove the first two shortcuts since we want users to use the portable start menu. <br /> Change the help.lnk shortcut to point to the readme.htm file <br /> <br /> Click next<br /> <br /> ===Execute after setup===<br /> You can use these values<br /> Program: $INSTDIR\setup_xampp.bat<br /> Readme: $INSTDIR\readme.htm<br /> <br /> Click next<br /> <br /> ===Uninstaller===<br /> Accept the defaults<br /> <br /> Click next<br /> <br /> ===Wizard Finished===<br /> Check the save script and compile boxes. Click finish<br /> <br /> Enter the path to where you wish the script to be saved and the installer to be created.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Installer&diff=37038 2008-06-04T13:57:13Z

<p>Colchambers: </p> <hr /> <div>To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> =What You’ll Need=<br /> <br /> ==Create an Environment==<br /> Source files<br /> Xampp: xampplite-win32-1.6.6.exe<br /> Provide environment to run Offline Moodle web server, database server etc<br /> Moodle: moodle-1.9.4 zip release version ideally with offline moodle enhancements. Unzipped to htdocs/moodle<br /> Moodle Data folder created in root folder of xampp<br /> Portable Start menu: pstart available at http://www.pegtop.de/start/<br /> <br /> To put it all together follow the separate document titled Environment Creation<br /> <br /> ==Create an installer==<br /> Once you have a working version begin creating a distributable package. We use the NSIS installer http://nsis.sourceforge.net/Main_Page since it provides a customisable installer package that runs on the windows platform and it’s free. It’s very easy to create an installer using the wizard provided in the nsis edit at http://hmne.sourceforge.net/ <br /> <br /> =Creating an Installer=<br /> Ok, you should now have a working Offline Moodle environment. The next step is to package it up and distribute it. <br /> <br /> First you have to decide on the installer you want to package this up with. We chose the NSIS installer from Nullsoft because it’s highly configurable and it’s free. Unfortunately it only works on windows.<br /> <br /> ==Creating an NSIS script==<br /> Once you have installed the nsis editor go to ‘file\new script from wizard’ click next <br /> <br /> ===Application Information==<br /> then enter the request values. Note that the Application Website field will be used to create an internet shortcut and placed in the same folder as Offline Moodle. It will have the same name as the Application name. We already have an internet shortcut named Offline Moodle that points to http://localhost/moodle which takes a user to Offline Moodle on their machine. So you might want to leave this empty to avoid overwriting the current file.<br /> <br /> Click next<br /> <br /> ===Setup Options===<br /> Leave all settings at default. Setup file can be something like Offline Moodle Setup 0.3.exe<br /> Setup Lang defaults to English<br /> <br /> Click next<br /> <br /> ===Application directory and License===<br /> Leave with default values except for license file. We use the apache license file at xampp\licenses\apache\LICENSE.txt in the absence of a specific file for Offline Moodle<br /> <br /> Click next<br /> <br /> ===Application Files===<br /> This part takes a while because we can’t find away to import all the necessary files without letting the nsis installer run through each one. This can take quite a while. <br /> <br /> Delete the two example files using the x (Remove file) icon above the file window. Then click the add directory tree icon. It will open a dialogue box titled EditDirectory<br /> <br /> Enter the path to the xampp folder containing the xampp and moodle installation you wish to use (Copy and pasting from windows explorer is easiest I find). Leave the defaults and click ok.<br /> <br /> The dialogue box will then close and begin importing the many files necessary into the install script you are creating. The program will look as if it is not doing anything and has hung but check your hard drive activity light and you should see a lot of activity. <br /> <br /> Once all the files have been imported to the script the file area will list all the files included in the xampp install.<br /> <br /> Click next<br /> <br /> ===Application Icons===<br /> Enter the Application Start Menu Folder Name.<br /> <br /> Leave the defaults. <br /> Remove the first two shortcuts since we want users to use the portable start menu. <br /> Change the help.lnk shortcut to point to the readme.htm file <br /> <br /> Click next<br /> <br /> ===Execute after setup===<br /> You can use these values<br /> Program: $INSTDIR\setup_xampp.bat<br /> Readme: $INSTDIR\readme.htm<br /> <br /> Click next<br /> <br /> ===Uninstaller===<br /> Accept the defaults<br /> <br /> Click next<br /> <br /> ===Wizard Finished===<br /> Check the save script and compile boxes. Click finish<br /> <br /> Enter the path to where you wish the script to be saved and the installer to be created.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=37037 2008-06-04T13:53:35Z

<p>Colchambers: /* Articles */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle_Create_Installer|Creating an Offline Moodle Installer]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=37036 2008-06-04T13:53:11Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Installer]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle:_Incremental_Backups&diff=35462 2008-04-30T11:16:08Z

<p>Colchambers: </p> <hr /> <div>=Current work on Incremental Backups=<br /> One of the first features that on Offline Moodle requires from Moodle is to be able to get updates from a central Moodle in a small, efficient package rather than a large download. The only reliable method for getting the required information in and out of Moodle at the moment is using the backup/restore feature that's built into Moodle and thus Offline Moodle. This works well enough but can easily create large files which will cause problems when a user just wants to update quickly before they go to work for example. <br /> <br /> The answer to this is to enhance the backup component to offer smaller incremental updates aswell as the standard full backup. To achieve this the Open University (UK) have teamed up with Catalyst to develop this functionality and get it into the core of Moodle. We believe that not only is this functionality a necessary feature for Offline Moodle but that it will benefit many sections of the community particularly those responsible for managing Moodle installations. <br /> <br /> ==Latest Work==<br /> If you'd like to check our progress you can download Moodle 1.9.4 with the latest incremental backup code at http://git.catalyst.net.nz/gitweb?p=moodle-r2.git;a=shortlog;h=refs/heads/mdl19-incrementalbackup .<br /> <br /> We aim to put some text up here explaining in more detail how it all works and how to get a server and client work, how to automate it etc. For now just be aware that the backup work is well under way but the restore work is not. It's being developed against the postgres db and then ported to mysql so there are a couple of outstanding mysql issues. <br /> <br /> You can try it out by creating a course with a little content. Then selecting backup from the course admin menu, make sure you select generate incrementals from the form provided. It's at the bottom of the list of drop down menus about half way down the form. Then generate the backup.<br /> <br /> You can report a bug at http://tracker.moodle.org log it as part of the 'non core components' under the 'Offline Moodle' component and please include 'Incremental Backup:' in the bug title to help us identify it. Assign it to Colin Chambers. <br /> <br /> If you wish to get in contact then please email me at c.chambers@open.ac.uk</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=35461 2008-04-30T10:55:24Z

<p>Colchambers: /* Articles */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> * [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> * [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=35460 2008-04-30T10:55:10Z

<p>Colchambers: /* Articles */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> <br /> [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=35459 2008-04-30T10:54:51Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> [[Development:Offline_Moodle: Incremental Backups|Work on Incremental Backups]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=35115 2008-04-23T11:00:08Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Articles==<br /> [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35114 2008-04-23T10:15:30Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> This article is designed to help you replicate the Offline Moodle Environment that is being used within Offline Moodle. Currently we have focused on distributing to machines using the Windows operating system. In time we expect to add advice for other operating systems. We have tried to cover everything that's required to setup the entire environment so that this process it as simple as possible.<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> First of all you need to create an environment that meets the basic requirements of Moodle. This includes:<br /> * A web server: To server internet files<br /> * A database server: To handle data records<br /> * A PHP distribution: Moodle runs under php so you need this installed. <br /> <br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues<br /> <br /> ===Portable Menu===<br /> The latest addition to the mix is to provide a portable menu system that provides easy access to key components of Offline Moodle. Thanks for identifying this feature go to John Attwood who has been developing his own Portable Moodle application similar to Offline Moodle. You can read more at [http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141 http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141].<br /> <br /> Again the xml config file the portable menu creates is too large to add here. The links are extremely easy to create within the menu itself and you'll probably want to customise it to your needs.<br /> <br /> The main links we have included so far are:<br /> * readme: links to readme.htm<br /> * Offline Moodle: Links to the Offline Moodle.url shortcut created earlier<br /> * Start Offline Moodle: Links to the file xampp_start.exe <br /> * Stop Offline Moodle: Links to the file xampp_stop.exe <br /> * Reconfigure Offline Moodle: Links to the file setup_xampp.bat <br /> <br /> We also added a group named 'resources' to contain links to extra components that may come in useful such as:<br /> * Restart Offline Moodle: Links to the file xampp_restart.exe<br /> * Is Offline Moodle Running?: Links to the file xampp-portcheck.exe</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35113 2008-04-23T10:13:03Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> First of all you need to create an environment that meets the basic requirements of Moodle. This includes:<br /> * A web server: To server internet files<br /> * A database server: To handle data records<br /> * A PHP distribution: Moodle runs under php so you need this installed. <br /> <br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues<br /> <br /> ===Portable Menu===<br /> The latest addition to the mix is to provide a portable menu system that provides easy access to key components of Offline Moodle. Thanks for identifying this feature go to John Attwood who has been developing his own Portable Moodle application similar to Offline Moodle. You can read more at [http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141 http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141].<br /> <br /> Again the xml config file the portable menu creates is too large to add here. The links are extremely easy to create within the menu itself and you'll probably want to customise it to your needs.<br /> <br /> The main links we have included so far are:<br /> * readme: links to readme.htm<br /> * Offline Moodle: Links to the Offline Moodle.url shortcut created earlier<br /> * Start Offline Moodle: Links to the file xampp_start.exe <br /> * Stop Offline Moodle: Links to the file xampp_stop.exe <br /> * Reconfigure Offline Moodle: Links to the file setup_xampp.bat <br /> <br /> We also added a group named 'resources' to contain links to extra components that may come in useful such as:<br /> * Restart Offline Moodle: Links to the file xampp_restart.exe<br /> * Is Offline Moodle Running?: Links to the file xampp-portcheck.exe</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35112 2008-04-23T10:08:21Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues<br /> <br /> ===Portable Menu===<br /> The latest addition to the mix is to provide a portable menu system that provides easy access to key components of Offline Moodle. Thanks for identifying this feature go to John Attwood who has been developing his own Portable Moodle application similar to Offline Moodle. You can read more at [http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141 http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141].<br /> <br /> Again the xml config file the portable menu creates is too large to add here. The links are extremely easy to create within the menu itself and you'll probably want to customise it to your needs.<br /> <br /> The main links we have included so far are:<br /> * readme: links to readme.htm<br /> * Offline Moodle: Links to the Offline Moodle.url shortcut created earlier<br /> * Start Offline Moodle: Links to the file xampp_start.exe <br /> * Stop Offline Moodle: Links to the file xampp_stop.exe <br /> * Reconfigure Offline Moodle: Links to the file setup_xampp.bat <br /> <br /> We also added a group named 'resources' to contain links to extra components that may come in useful such as:<br /> * Restart Offline Moodle: Links to the file xampp_restart.exe<br /> * Is Offline Moodle Running?: Links to the file xampp-portcheck.exe</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35111 2008-04-23T09:59:21Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues<br /> <br /> ===Portable Menu===<br /> The latest addition to the mix is to provide a portable menu system that provides easy access to key components of Offline Moodle. Thanks for identifying this feature go to John Attwood who has been developing his own Portable Moodle application similar to Offline Moodle. You can read more at [http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141 http://hawk.aos.ecu.edu/moodle/mod/forum/discuss.php?d=141]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35110 2008-04-23T09:51:30Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from:<br /> * The XAMPP Apache, Mysql and PHP Environment can be obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> * Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/ http://download.moodle.org/windows/]<br /> * Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/ http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35108 2008-04-23T09:49:46Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35107 2008-04-23T09:49:26Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [[http://www.apachefriends.org/en/xampp-windows.html#646 http://www.apachefriends.org/en/xampp-windows.html#646]]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35106 2008-04-23T09:48:02Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [[http://www.apachefriends.org/en/xampp-windows.html#646|http://www.apachefriends.org/en/xampp-windows.html#646]]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35105 2008-04-23T09:47:15Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646|http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35104 2008-04-23T09:46:42Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===<br /> Following the practise of many application manufacturers we created an html readme file. this way it's more presentable than a plain text file and matches the web based approach of Moodle. <br /> <br /> We added the files <br /> readme.htm<br /> system-requirements.htm<br /> <br /> The full contents of these files are too large to add here and are changing as the project develops. The main contents of readme.htm cover basic points such as <br /> * Quick Start<br /> * Run On Another Machine<br /> * Troubleshooting<br /> * Improvements<br /> * Known Issues</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35103 2008-04-23T09:42:15Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> We looked at ways to package up Offline Moodle into one file, create batch files that automate all the processes necessary to configure and start xampp each time and many other options but each, while possible, would require more time, effort and expertise than we currently have to devote. they would also add complexity to the approach we are taking. At this point we just decided to go for the simplest solutions of creating shortcuts and readme files and adding a portable menu since these are very simple to create and degrade gracefully across environments thus ensuring we cater for the lowest common denominator.<br /> <br /> ===Internet Shortcuts===<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location<br /> <br /> ===Readme Files===</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35102 2008-04-23T09:38:01Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> ==Internet Shortcuts<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and .url extension and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> We created the following files<br /> Offline Moodle.url, URL=http://localhost/moodle <br /> Offline Moodle at the Open University.url, URL=http://www.open.ac.uk/offlinemoodle<br /> <br /> The last link we created to give the user context of what Offline Moodle is. You'll probably want to create your own to guide your own users appropriately.<br /> Location</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35101 2008-04-23T09:35:29Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: Admin<br /> Password: m00dl3<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add a student account====<br /> We've left out some of the compulsory value since you'll want to enter your own<br /> Username: student<br /> Password: testing<br /> <br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> ==Improve Usability==<br /> Now we should have a fully installed and working Moodle environment that can work from any folder you move it to. What we need to do now is make it a little easier for the average user to use. We're technical guys that know how to configure these things but many students and lecturers won't have our technical skills so we want to remove any barriers there are to them just starting there machine, clicking start Offline Moodle and clicking a shortcut that opens Offline Moodle in a browser for them. Basically what are the fewest number of steps that we can achieve this in? <br /> <br /> ==Internet Shortcuts<br /> Let's create a couple of shortcuts to save the user the trouble of typing urls. Once made the user just has to click these shortcuts to load a brwoser and see the site. That's two or three steps eliminated. <br /> <br /> There are many ways to create shortcuts and feel free to choose your own. I thought I show you how to create a shortcut directly since that's what you'll end up with and you'll have more control this way. <br /> <br /> Create a text file with the appropriate name and open it in a text editor. Notepad, vim, eclipse, whatever.<br /> add the following lines<br /> <br /> [InternetShortcut]<br /> URL=http://localhost/moodle<br /> <br /> Save the file and double click it in the file system. You browser should open and go to the url. It's that simple. Or it is in windows XP. If it's different for other versions of windows then please let me know. <br /> <br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35100 2008-04-23T09:23:47Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create the Database and Assign a User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> === Unzip Moodle===<br /> Unzip the Moodle installation to the folder c:\offline\htdocs\moodle<br /> create the folder c:\offline\moodledata so Moodle knows where to store its data<br /> <br /> ===Create the config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> ===Generate the Database tables and load data===<br /> Now you're past the point of editing files. Everything from this point should be done through a web browser since php is now running, you have a database setup and Moodle knows where it is and which account to use. <br /> In a web browser go to http://localhost/moodle and follow the install process<br /> <br /> Here are the initial values we chose if you just want to copy and paste.<br /> <br /> ====Setup up initial data====<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> ====Front Page settings====<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> ====Setup session handling====<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> ====Add student account====<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35099 2008-04-23T09:16:17Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server, database server and php distribution, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp makes this simple by providing a form to enter the required details. to reach this form choose security from the left hand menu then half way down the page should be a link http://localhost/security/xamppsecurity.php. Follow the link and enter the necessary values. <br /> <br /> we have left the default values in place and added passwords to the root accounts both for the database and web server directories. This won't affect access to the htdocs folder itself where Moodle runs from. It simply protects the xampp configuration that's accessible through a browser with the password you've set. This protects your xampp installation from malicious users.<br /> <br /> ==Install Moodle==<br /> Now that we have a web server and database architecture working we need to install Moodle to get a VLE up and running. <br /> <br /> ===Create Database and Assign User===<br /> First we have to create a database within the database server for Moodle to reside in and then create a user with access to this database.<br /> <br /> I'll assume you know how to run sql commands against the database to follow the next points.<br /> <br /> <br /> Run the following sql on the database<br /> Creates the moodle database<br /> create database `moodle` character set utf8;<br /> <br /> Creates the User and assigns permission to the database<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> <br /> ===Create config file===<br /> The first part of installing Moodle creates the configuration file which tells Moodle where it is on your device and what it can do. <br /> <br /> There are two ways to do this. We recommend the first step as it creates a file that references files relative to your moodle installation. The wizard unfortunately uses paths that are absolute. They point exactly to the location Moodle is installed. This means that if you copy the xampp folder to another machine you will have to change these paths in the config. <br /> <br /> if you do use the wizard then simply replace part of the file path for $CFG-&gt;dirroot and $CFG-&gt;dataroot with dirname(__FILE__) to let php determine where Moodle is installed and make it easy to move Offline Moodle around.<br /> <br /> the two processes are described here.<br /> <br /> <br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> Generate Database tables and load data<br /> <br /> Got to http://localhost.moodle and follow the install process<br /> <br /> Setup up initial data<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Front Page settings<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> Setup session handling<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> Add student account<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35098 2008-04-23T08:59:59Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ==Create the Environment==<br /> ===Install The Architecture===<br /> I could say install xampp because that's what we'll be doing but it's important to remember that xampp is simply a web server and database server, among other things, that is freely available and works on different operating systems. There are other solutions you could use and we've worked to ensure you could Switch it to these instead of xampp if you so desired. <br /> <br /> Since we're using xampp the install is very simple. Just run the exe and chose where to unzip the files. No registry settings should be changed and no other operating system changes will be made. This is important to the overall concept of Offline Moodle in that it can be run from the folder it is unzipped to. All that you need to do is reconfigure xampp to recognise it's new location, thankfully a handle utility setup_xampp.bat does this for you so you just need to click it. Then start xampp with xampp_start.exe and xampp should start. If you're using windows xp you may notice firewall warnings. This is what firewalls do, basically xampp starting means a database and web server start. Each on needs to access the network and provide data over the network. That's why your firewall asks if this is ok with you. So just choose unblock when prompted. <br /> <br /> When prompted chose where to unzip the xampp files to. We'll choose c:\offline for this tutorial but I normally nest it much further where I'm used to keeping project files. <br /> <br /> ===Start the Architecture===<br /> This should be as easy as explained above reconfigure xampp to recognise its new location using setup_xampp.bat and then start it using xampp_start.exe. When you want to stop it just use the corresponding xampp_stop.exe file. <br /> <br /> You'll get a black command prompt window pop up telling you xampp and it's services starting. Now open a web browser on your machine and type http://localhost into the address bar and press enter. You should be taken to the xampp home page. If you're not then wait a short while and try again in case xampp was still starting. If xampp won't start then check the xampp site for advice on how to fix the error. My main problem was forget to reconfigure it when I move the xampp folder or install it. <br /> <br /> So there you go. There is another way to get xampp running using the xampp-control.exe but I'll levave you to play around with that. At this point we're not planning to promote use of this in our Offline Moodle installs simply because it presents the webserver and database as separate applications. Which while correct we don't want users to have to worry about this complexity. We just want them to start and stop Offline Moodle as they would any application. <br /> <br /> ===Secure XAMPP===<br /> We have taken some small steps to secure the database and web server directories using standard approaches. Xampp <br /> <br /> ==Install Moodle==<br /> <br /> Secure the mysql root password using the values below<br /> <br /> Create the moodle database<br /> Run the following sql on the database<br /> create database `moodle` character set utf8;<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> <br /> ==Create config file==<br /> There are two ways<br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> Generate Database tables and load data<br /> <br /> Got to http://localhost.moodle and follow the install process<br /> <br /> Setup up initial data<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Front Page settings<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> Setup session handling<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> Add student account<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35060 2008-04-22T16:27:12Z

<p>Colchambers: </p> <hr /> <div>=Creating an Offline Moodle Environment=<br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> ==Source files==<br /> The environment comprises the following libraries<br /> Xampp: xampplite-win32-1.6.6.exe obtained from [http://www.apachefriends.org/en/xampp-windows.html#646]<br /> Moodle: moodle-1.9.zip latest version obtained from [http://download.moodle.org/windows/]<br /> Portable Menu: PStartSetup211.exe obtained from [http://www.pegtop.de/start/]<br /> <br /> ===Install Moodle===<br /> <br /> Secure the mysql root password using the values below<br /> <br /> Create the moodle database<br /> Run the following sql on the database<br /> create database `moodle` character set utf8;<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> <br /> ==Create config file==<br /> There are two ways<br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> Generate Database tables and load data<br /> <br /> Got to http://localhost.moodle and follow the install process<br /> <br /> Setup up initial data<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Front Page settings<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> Setup session handling<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> Add student account<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35059 2008-04-22T16:23:08Z

<p>Colchambers: /* Install Moodle */</p> <hr /> <div><br /> <br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> Environment Generation<br /> Source files<br /> Xampp: xampplite-win32-1.6.6.exe<br /> Moodle: moodle-1.9.zip release version<br /> <br /> ===Install Moodle===<br /> <br /> Secure the mysql root password using the values below<br /> <br /> Create the moodle database<br /> Run the following sql on the database<br /> create database `moodle` character set utf8;<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> <br /> ==Create config file==<br /> There are two ways<br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> Generate Database tables and load data<br /> <br /> Got to http://localhost.moodle and follow the install process<br /> <br /> Setup up initial data<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Front Page settings<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> Setup session handling<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> Add student account<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle_Create_Environment&diff=35058 2008-04-22T16:22:44Z

<p>Colchambers: </p> <hr /> <div><br /> <br /> To ensure a standard approach to developing offline moodle environments it is important to record and maintain details<br /> <br /> Environment Generation<br /> Source files<br /> Xampp: xampplite-win32-1.6.6.exe<br /> Moodle: moodle-1.9.zip release version<br /> <br /> ===Install Moodle===<br /> <br /> Secure the mysql root password using the values below<br /> <br /> Create the moodle database<br /> Run the following sql on the database<br /> create database `moodle` character set utf8;<br /> grant all on `moodle`.* to 'moodle'@'localhost' IDENTIFIED BY 'm00dl3';<br /> <br /> <br /> Create config file<br /> There are two ways<br /> 1) Create the file directly<br /> create a file using the following values in the root of the moodle directory called config.php<br /> <br /> &lt;?php /// Moodle Configuration File <br /> <br /> unset($CFG);<br /> <br /> $CFG-&gt;dbtype = 'mysql';<br /> $CFG-&gt;dbhost = 'localhost';<br /> $CFG-&gt;dbname = 'moodle';<br /> $CFG-&gt;dbuser = 'moodle';<br /> $CFG-&gt;dbpass = 'm00dl3';<br /> $CFG-&gt;dbpersist = false;<br /> $CFG-&gt;prefix = 'mdl_';<br /> <br /> $CFG-&gt;wwwroot = 'http://localhost/moodle';<br /> $CFG-&gt;dirroot = dirname(__FILE__);<br /> $CFG-&gt;dataroot = dirname(__FILE__).'\\..\\..\\moodledata';<br /> $CFG-&gt;admin = 'admin';<br /> <br /> $CFG-&gt;directorypermissions = 00777; // try 02777 on a server in Safe Mode<br /> <br /> require_once(&quot;$CFG-&gt;dirroot/lib/setup.php&quot;);<br /> // MAKE SURE WHEN YOU EDIT THIS FILE THAT THERE ARE NO SPACES, BLANK LINES,<br /> // RETURNS, OR ANYTHING ELSE AFTER THE TWO CHARACTERS ON THE NEXT LINE.<br /> ?&gt;<br /> <br /> 2) Use the install wizard <br /> Got to http://localhost.moodle<br /> Enter the values from above as they are requested. Once the config file is created change the values for $CFG-&gt;dirroot and CFG-&gt;dataroot as shown above to ensure they are dynamic paths that will work as the code is moved around. <br /> <br /> Generate Database tables and load data<br /> <br /> Got to http://localhost.moodle and follow the install process<br /> <br /> Setup up initial data<br /> Username: Admin<br /> Password: m00dl3<br /> Email: testofflinemoodle@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Front Page settings<br /> Full site name: Offline Moodle<br /> Short name for site: OfflineMoodle<br /> Front Page Description: Welcome to Offline Moodle<br /> <br /> Setup session handling<br /> So that we don’t conflict with other moodles change the session to be unique.<br /> Go to Server&gt; Session Handling. In the Cookie prefix box enter ‘offlinemoodle’ and save changes. You will now have to log back in. <br /> <br /> Add student account<br /> Username: student<br /> Password: testing<br /> Email: offlinestudent@open.ac.uk<br /> Email Activated: Hide my email address from everyone<br /> City/Town: Milton Keynes<br /> Country: United Kingdom<br /> <br /> Create root support files<br /> Pre configured help files<br /> Readme.htm<br /> system-requirements.htm<br /> Help folder and contents<br /> <br /> <br /> Internet Shortcuts<br /> Offline Moodle.lnk<br /> Offline Moodle at the Open University.lnk<br /> Location<br /> <br /> Security<br /> passwords are available on request to [c.chambers@open.ac.uk]<br /> Database:<br /> User: root<br /> Password: <br /> <br /> Directory protection:<br /> Will create a .htaccess file for password protection over http<br /> <br /> User: root<br /> Password:</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=35057 2008-04-22T16:19:46Z

<p>Colchambers: /* Where can I find out more? */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process.<br /> <br /> [[Development:Offline_Moodle_Create_Environment|Creating an Offline Moodle Environment]]<br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28456 2007-11-05T10:58:27Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Developer_notes&diff=28455 2007-11-05T10:46:47Z

<p>Colchambers: /* Other */</p> <hr /> <div>&lt;p class=&quot;note&quot;&gt;'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing &lt;code&gt;Development:&lt;/code&gt; before the new page name i.e. &lt;code&gt;&lt;nowiki&gt;[[Development:New page name]]&lt;/nowiki&gt;&lt;/code&gt;.&lt;/p&gt;<br /> <br /> This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Development:Developer documentation|Developer documentation]] page.<br /> <br /> ==Core code==<br /> <br /> *[[Other lang issues|Language issues]] <br /> *[[Datalib Notes]]<br /> *[[Application/session variables]]<br /> *[[Filters schema]]<br /> *[[Filterall support]]<br /> *[[Groups documentation for module developers]]<br /> *[[Development:Plan to improve ability to delegate administrator tasks to course category level|Plan to improve ability to delegate administrator tasks to course category level]]<br /> *[[Development:Stealth mode and nested activities|Stealth mode and nested activities]]<br /> <br /> ==Modules and other recognised plugin types==<br /> <br /> ===Lesson===<br /> <br /> *[[Adding_question_types_to_lesson|Adding question types to lesson module]]<br /> *[[Development:New lesson navigation | New lesson navigation]]<br /> *[[Development:Adding blocks to lesson | Adding blocks to lesson]]<br /> <br /> ===Quiz &amp; question types===<br /> <br /> *[[Calculated question development]]<br /> *[[Development:quiz_navigation | Quiz navigation]]<br /> *[[Numerical question units and intervals]]<br /> *[[Development:Plans for adaptive mode|Plans for adaptive mode]]<br /> *[[Development:Quiz UI redesign prototype | Quiz UI redesign prototype]]<br /> *[[Development:Open_protocol_for_accessing_question_engines|Open protocol for accessing question engines]]<br /> *[[Development:Implementation of true negative marks in MC-type questions]]<br /> <br /> ===Other activity modules===<br /> <br /> *[[Forum development|Forum functional upgrade]]<br /> *[[Wiki development|Wiki module development]]<br /> <br /> ===Other===<br /> <br /> *[[Blogs and forums|Blogs, forums and the nature of discussion]]<br /> *[[Conditional activities]]<br /> *[[Improved Payment Plugin]]<br /> *[[Development:Moodle-specific customisations to the HTML editor]]<br /> <br /> ==Other==<br /> <br /> *[[MoodleDocs development]]<br /> *[[Usability]]<br /> *[[Document Management API]]<br /> *[[wikindx|Possible integration of WIKINDX with Moodle]]<br /> *[[Quiz and quesions community testing day]]<br /> *[[Development:Snapshot - flat HTML export of complete course]]<br /> *[[Development:Offline Moodle | Development:Offline Moodle - A Moodle that runs on a mobile device with the internet]]<br /> <br /> ==Archive: past proposals==<br /> <br /> ===Things that got implemented===<br /> <br /> *[[Roles]] - in Moodle 1.7<br /> *[[Moodle forms library]] - in Moodle 1.8<br /> **[[Martin form notes]]<br /> *[[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Plans for enhancing the question bank]] - in Moodle 1.9<br /> *[[Development:Email notification when a quiz is submitted|Email notification when a quiz is submitted]] - in Moodle 1.9<br /> *[[Development:Plans for enhancing import/export in questiontype plugins]] - in Moodle 1.9<br /> <br /> [[Category:Developer]]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28453 2007-11-05T10:44:44Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28452 2007-11-05T10:44:21Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28451 2007-11-05T10:43:54Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28450 2007-11-05T10:43:22Z

<p>Colchambers: /* Assumptions of Offline Moodle */</p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> ;test<br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28449 2007-11-05T10:41:04Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> '''The information from the client or the server must be verified and checked at all times before being used.''' Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> '''Information must pass through filters before being sent or used.''' Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> '''The host device must be able to run Offline Moodle with as little modification as necessary.''' Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> '''The Offline Moodle files must all be contained in one place.''' Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> '''Offline Moodle runs in its own self contained environment.''' Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> '''It must be very easy to backup and restore the entire Offline Moodle'''. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> '''It must be very simple to reinstall.''' Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> '''It must be very simple for a helpdesk or faculty to support.'''<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28448 2007-11-05T10:37:31Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> ==Where can I find out more?==<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> ==Assumptions of Offline Moodle==<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> The information from the client or the server must be verified and checked at all times before being used. Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> Information must pass through filters before being sent or used. Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> The host device must be able to run Offline Moodle with as little modification as necessary. Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> The Offline Moodle files must all be contained in one place. Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> Offline Moodle runs in its own self contained environment. Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> It must be very easy to backup and restore the entire Offline Moodle. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> It must be very simple to reinstall. Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> It must be very simple for a helpdesk or faculty to support.<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28447 2007-11-05T10:36:51Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> '''Where can I find out more?'''<br /> <br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> <br /> '''Assumptions of Offline Moodle'''<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> The information from the client or the server must be verified and checked at all times before being used. Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> Information must pass through filters before being sent or used. Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> The host device must be able to run Offline Moodle with as little modification as necessary. Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> The Offline Moodle files must all be contained in one place. Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> Offline Moodle runs in its own self contained environment. Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> It must be very easy to backup and restore the entire Offline Moodle. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> It must be very simple to reinstall. Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> It must be very simple for a helpdesk or faculty to support.<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28446 2007-11-05T10:36:14Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> '''Where can I find out more?'''<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> Assumptions of Offline Moodle<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> The information from the client or the server must be verified and checked at all times before being used. Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> Information must pass through filters before being sent or used. Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> The host device must be able to run Offline Moodle with as little modification as necessary. Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> The Offline Moodle files must all be contained in one place. Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> Offline Moodle runs in its own self contained environment. Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> It must be very easy to backup and restore the entire Offline Moodle. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> It must be very simple to reinstall. Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> It must be very simple for a helpdesk or faculty to support.<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28445 2007-11-05T10:33:55Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> Where can I find out more?<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> Assumptions of Offline Moodle<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> The information from the client or the server must be verified and checked at all times before being used. Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> Information must pass through filters before being sent or used. Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> The host device must be able to run Offline Moodle with as little modification as necessary. Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> The Offline Moodle files must all be contained in one place. Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> Offline Moodle runs in its own self contained environment. Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> It must be very easy to backup and restore the entire Offline Moodle. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> It must be very simple to reinstall. Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> It must be very simple for a helpdesk or faculty to support.<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Offline_Moodle&diff=28444 2007-11-05T10:33:23Z

<p>Colchambers: </p> <hr /> <div>Offline Moodle is a joint project between the Open University (UK) and Intel. We presented our current developments at the Moodle Moot 2007 and were able to demonstrate a working proof of concept that downloads Moodle courses from a remote server on to a mobile device which runs an Offline version of Moodle. <br /> <br /> The Offline Moodle concept aims for simplicity in all aspects as so a lot of thought has gone into ensuring it is as easy to develop and maintain as it is to use. We have a lot to say and will endeavour to add to this wiki as the project progresses. In the meantime please visit the other places that we have been using to get everyone involved and explain what we're trying to achieve. <br /> <br /> Where can I find out more?<br /> The project was introduced to the Moodle community in the forums at http://moodle.org/mod/forum/discuss.php?d=71136<br /> <br /> A Moodle course has been set up at http://hawk.aos.ecu.edu/moodle/ as a central place to find out about current developments and get involved in the development process. <br /> Assumptions of Offline Moodle<br /> An Offline Moodle represents, among other things, significant security and privacy challenges. For this reason we have defined a set of assumptions we are using to guide our development to ensure the application and its supporting processes maintain a high level of security and privacy where appropriate.<br /> <br /> The information from the client or the server must be verified and checked at all times before being used. Why?<br /> *Cross site scripting<br /> *Trojans, viruses<br /> *Machines altering data in the middle of it’s transfer<br /> *Ip spoofing<br /> <br /> Information must pass through filters before being sent or used. Why?<br /> *Data protection: passwords, contact details<br /> *Copyright issues<br /> *Security issues<br /> <br /> The host device must be able to run Offline Moodle with as little modification as necessary. Why?<br /> *Ease of use: plug and play functionality leads to convenience and simplicity<br /> *Ease of support: The less changes made the less there is to go wrong<br /> <br /> The Offline Moodle files must all be contained in one place. Why?<br /> Ease of support: reinstallation becomes much easier<br /> <br /> Offline Moodle runs in its own self contained environment. Why?<br /> *users can make changes to their Offline Moodle and underlying files but this is at their own risk.<br /> <br /> It must be very easy to backup and restore the entire Offline Moodle. Why?<br /> *Protection of work stored in Offline Moodle<br /> *Makes for a simple reinstall<br /> *Portability of content<br /> <br /> It must be very simple to reinstall. Why?<br /> *Reduces support overhead<br /> *Backup, reinstall, restore is simple for users to follow and fix issues themselves<br /> <br /> It must be very simple for a helpdesk or faculty to support.<br /> *To reduce support headaches the recommended procedure for the majority of technical issues should be backup existing data, reinstall Offline Moodle, restored data. <br /> *Standard pre written Moodle documentation should be used to educate users on effective Moodle use. The need for extra documentation must be minimised.</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Developer_notes&diff=28443 2007-11-05T10:32:52Z

<p>Colchambers: /* Other */</p> <hr /> <div>&lt;p class=&quot;note&quot;&gt;'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing &lt;code&gt;Development:&lt;/code&gt; before the new page name i.e. &lt;code&gt;&lt;nowiki&gt;[[Development:New page name]]&lt;/nowiki&gt;&lt;/code&gt;.&lt;/p&gt;<br /> <br /> This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Development:Developer documentation|Developer documentation]] page.<br /> <br /> ==Core code==<br /> <br /> *[[Other lang issues|Language issues]] <br /> *[[Datalib Notes]]<br /> *[[Application/session variables]]<br /> *[[Filters schema]]<br /> *[[Filterall support]]<br /> *[[Groups documentation for module developers]]<br /> *[[Development:Plan to improve ability to delegate administrator tasks to course category level|Plan to improve ability to delegate administrator tasks to course category level]]<br /> *[[Development:Stealth mode and nested activities|Stealth mode and nested activities]]<br /> <br /> ==Modules and other recognised plugin types==<br /> <br /> ===Lesson===<br /> <br /> *[[Adding_question_types_to_lesson|Adding question types to lesson module]]<br /> *[[Development:New lesson navigation | New lesson navigation]]<br /> *[[Development:Adding blocks to lesson | Adding blocks to lesson]]<br /> <br /> ===Quiz &amp; question types===<br /> <br /> *[[Calculated question development]]<br /> *[[Development:quiz_navigation | Quiz navigation]]<br /> *[[Numerical question units and intervals]]<br /> *[[Development:Plans for adaptive mode|Plans for adaptive mode]]<br /> *[[Development:Quiz UI redesign prototype | Quiz UI redesign prototype]]<br /> *[[Development:Open_protocol_for_accessing_question_engines|Open protocol for accessing question engines]]<br /> *[[Development:Implementation of true negative marks in MC-type questions]]<br /> <br /> ===Other activity modules===<br /> <br /> *[[Forum development|Forum functional upgrade]]<br /> *[[Wiki development|Wiki module development]]<br /> <br /> ===Other===<br /> <br /> *[[Blogs and forums|Blogs, forums and the nature of discussion]]<br /> *[[Conditional activities]]<br /> *[[Improved Payment Plugin]]<br /> *[[Development:Moodle-specific customisations to the HTML editor]]<br /> <br /> ==Other==<br /> <br /> *[[MoodleDocs development]]<br /> *[[Usability]]<br /> *[[Document Management API]]<br /> *[[wikindx|Possible integration of WIKINDX with Moodle]]<br /> *[[Quiz and quesions community testing day]]<br /> *[[Development:Snapshot - flat HTML export of complete course]]<br /> *[[Development:Offline Moodle - A Moodle that runs on a mobile device with the internet]]<br /> *[[Development:Offline Moodle | Development:Offline Moodle - A Moodle that runs on a mobile device with the internet]]<br /> <br /> ==Archive: past proposals==<br /> <br /> ===Things that got implemented===<br /> <br /> *[[Roles]] - in Moodle 1.7<br /> *[[Moodle forms library]] - in Moodle 1.8<br /> **[[Martin form notes]]<br /> *[[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Plans for enhancing the question bank]] - in Moodle 1.9<br /> *[[Development:Email notification when a quiz is submitted|Email notification when a quiz is submitted]] - in Moodle 1.9<br /> *[[Development:Plans for enhancing import/export in questiontype plugins]] - in Moodle 1.9<br /> <br /> [[Category:Developer]]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Developer_notes&diff=28438 2007-11-05T10:17:13Z

<p>Colchambers: /* Other */</p> <hr /> <div>&lt;p class=&quot;note&quot;&gt;'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing &lt;code&gt;Development:&lt;/code&gt; before the new page name i.e. &lt;code&gt;&lt;nowiki&gt;[[Development:New page name]]&lt;/nowiki&gt;&lt;/code&gt;.&lt;/p&gt;<br /> <br /> This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Development:Developer documentation|Developer documentation]] page.<br /> <br /> ==Core code==<br /> <br /> *[[Other lang issues|Language issues]] <br /> *[[Datalib Notes]]<br /> *[[Application/session variables]]<br /> *[[Filters schema]]<br /> *[[Filterall support]]<br /> *[[Groups documentation for module developers]]<br /> *[[Development:Plan to improve ability to delegate administrator tasks to course category level|Plan to improve ability to delegate administrator tasks to course category level]]<br /> *[[Development:Stealth mode and nested activities|Stealth mode and nested activities]]<br /> <br /> ==Modules and other recognised plugin types==<br /> <br /> ===Lesson===<br /> <br /> *[[Adding_question_types_to_lesson|Adding question types to lesson module]]<br /> *[[Development:New lesson navigation | New lesson navigation]]<br /> *[[Development:Adding blocks to lesson | Adding blocks to lesson]]<br /> <br /> ===Quiz &amp; question types===<br /> <br /> *[[Calculated question development]]<br /> *[[Development:quiz_navigation | Quiz navigation]]<br /> *[[Numerical question units and intervals]]<br /> *[[Development:Plans for adaptive mode|Plans for adaptive mode]]<br /> *[[Development:Quiz UI redesign prototype | Quiz UI redesign prototype]]<br /> *[[Development:Open_protocol_for_accessing_question_engines|Open protocol for accessing question engines]]<br /> *[[Development:Implementation of true negative marks in MC-type questions]]<br /> <br /> ===Other activity modules===<br /> <br /> *[[Forum development|Forum functional upgrade]]<br /> *[[Wiki development|Wiki module development]]<br /> <br /> ===Other===<br /> <br /> *[[Blogs and forums|Blogs, forums and the nature of discussion]]<br /> *[[Conditional activities]]<br /> *[[Improved Payment Plugin]]<br /> *[[Development:Moodle-specific customisations to the HTML editor]]<br /> <br /> ==Other==<br /> <br /> *[[MoodleDocs development]]<br /> *[[Usability]]<br /> *[[Document Management API]]<br /> *[[wikindx|Possible integration of WIKINDX with Moodle]]<br /> *[[Quiz and quesions community testing day]]<br /> *[[Development:Snapshot - flat HTML export of complete course]]<br /> *[[Development:Offline Moodle - A Moodle that runs on a mobile device with the internet]]<br /> <br /> ==Archive: past proposals==<br /> <br /> ===Things that got implemented===<br /> <br /> *[[Roles]] - in Moodle 1.7<br /> *[[Moodle forms library]] - in Moodle 1.8<br /> **[[Martin form notes]]<br /> *[[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Plans for enhancing the question bank]] - in Moodle 1.9<br /> *[[Development:Email notification when a quiz is submitted|Email notification when a quiz is submitted]] - in Moodle 1.9<br /> *[[Development:Plans for enhancing import/export in questiontype plugins]] - in Moodle 1.9<br /> <br /> [[Category:Developer]]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:Developer_notes&diff=28437 2007-11-05T10:16:51Z

<p>Colchambers: /* Other */</p> <hr /> <div>&lt;p class=&quot;note&quot;&gt;'''Note:''' New developer documentation pages should be added to the ''Development namespace'' by typing &lt;code&gt;Development:&lt;/code&gt; before the new page name i.e. &lt;code&gt;&lt;nowiki&gt;[[Development:New page name]]&lt;/nowiki&gt;&lt;/code&gt;.&lt;/p&gt;<br /> <br /> This area is for developers to work on various bits of code and documentation as necessary. Once material has matured it should be linked to from the main [[Development:Developer documentation|Developer documentation]] page.<br /> <br /> ==Core code==<br /> <br /> *[[Other lang issues|Language issues]] <br /> *[[Datalib Notes]]<br /> *[[Application/session variables]]<br /> *[[Filters schema]]<br /> *[[Filterall support]]<br /> *[[Groups documentation for module developers]]<br /> *[[Development:Plan to improve ability to delegate administrator tasks to course category level|Plan to improve ability to delegate administrator tasks to course category level]]<br /> *[[Development:Stealth mode and nested activities|Stealth mode and nested activities]]<br /> <br /> ==Modules and other recognised plugin types==<br /> <br /> ===Lesson===<br /> <br /> *[[Adding_question_types_to_lesson|Adding question types to lesson module]]<br /> *[[Development:New lesson navigation | New lesson navigation]]<br /> *[[Development:Adding blocks to lesson | Adding blocks to lesson]]<br /> <br /> ===Quiz &amp; question types===<br /> <br /> *[[Calculated question development]]<br /> *[[Development:quiz_navigation | Quiz navigation]]<br /> *[[Numerical question units and intervals]]<br /> *[[Development:Plans for adaptive mode|Plans for adaptive mode]]<br /> *[[Development:Quiz UI redesign prototype | Quiz UI redesign prototype]]<br /> *[[Development:Open_protocol_for_accessing_question_engines|Open protocol for accessing question engines]]<br /> *[[Development:Implementation of true negative marks in MC-type questions]]<br /> <br /> ===Other activity modules===<br /> <br /> *[[Forum development|Forum functional upgrade]]<br /> *[[Wiki development|Wiki module development]]<br /> <br /> ===Other===<br /> <br /> *[[Blogs and forums|Blogs, forums and the nature of discussion]]<br /> *[[Conditional activities]]<br /> *[[Improved Payment Plugin]]<br /> *[[Development:Moodle-specific customisations to the HTML editor]]<br /> <br /> ==Other==<br /> <br /> *[[MoodleDocs development]]<br /> *[[Usability]]<br /> *[[Document Management API]]<br /> *[[wikindx|Possible integration of WIKINDX with Moodle]]<br /> *[[Quiz and quesions community testing day]]<br /> *[[Development:Snapshot - flat HTML export of complete course]]<br /> *[[Development:Offline_Moodle - A Moodle that runs on a mobile device with the internet]]<br /> <br /> ==Archive: past proposals==<br /> <br /> ===Things that got implemented===<br /> <br /> *[[Roles]] - in Moodle 1.7<br /> *[[Moodle forms library]] - in Moodle 1.8<br /> **[[Martin form notes]]<br /> *[[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Plans for enhancing the question bank]] - in Moodle 1.9<br /> *[[Development:Email notification when a quiz is submitted|Email notification when a quiz is submitted]] - in Moodle 1.9<br /> *[[Development:Plans for enhancing import/export in questiontype plugins]] - in Moodle 1.9<br /> <br /> [[Category:Developer]]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:MoodleMoot_2007_HackFest&diff=28139 2007-10-23T08:47:55Z

<p>Colchambers: /* Offline Moodle (and particularly synchronisation issues) */</p> <hr /> <div>The main part of the [http://moodlemoot.org/ 2007 UK Moodle Moot] is on Wednesday and Thursday 24th and 25th October. The day before, on the Tuesday, there will be a HackFest for developers to meet, talk and write code.<br /> <br /> ==Practical arrangement==<br /> <br /> You need to get [http://maps.google.co.uk/maps?ll=52.025356,-0.710997&amp;spn=0.001005,0.001904&amp;t=k&amp;z=19 right here]. This is the centre of the Open University's Campus:<br /> <br /> [http://www3.open.ac.uk/contact/ The Open University]&lt;br /&gt;<br /> Walton Hall&lt;br /&gt;<br /> Milton Keynes&lt;br /&gt;<br /> [http://maps.google.co.uk/?q=mk7+6aa&amp;ie=UTF8&amp;om=1&amp;f=d MK7 6AA]<br /> <br /> The area we are meeting in is called the Christodoulou Meeting Rooms. The entry is under an archway, and if you go in and up the stairs you should find us in Meeting Room 15, or the open foyer area just outside it. We will be there from about 10:00am to about 5:30pm, and lunch will be provided. We also have rooms 1, 2 and 7 available if people want to form smaller groups at any time. (Also, in meeting room 11, there will be a separate group of people taking about online equation editors, which may interest some people.)<br /> <br /> If you are registered for the MoodleMoot, wireless network sign-in information should be available on arrival.<br /> <br /> ==Programme for the day==<br /> <br /> In keeping with Moodle's open source philosophy, the day will be self-organising. You can turn up and talk to other developers about anything you like. However, within that general free-for-all, we will have a number of pre-announced discussions on particular topics at particular times. We have a number of other rooms available for these break-out sessions, but I don't know the room numbers right now.<br /> <br /> Please feel free to add your own suggestions below.<br /> <br /> Naturally, not all developers will be able to come, so it might be a good idea to start discussing some of these topics in the [http://moodle.org/mod/forum/view.php?id=55 General Developer Forum] now. And if anything significant comes out of the discussions, we should try to record it on the wiki.<br /> <br /> ==Particular discussions==<br /> <br /> These are significant topics, where it might be worth getting about 5-10 interested developers into a break-out room for a focussed discussion on one topic, or a demonstration of a particular idea.<br /> <br /> Irrespective of these sessions, there will be other developers around talking about whatever interests them all day.<br /> <br /> ===Repository API===<br /> The aim is to develop some consensus on how it can work so that a spec can be started.<br /> {|<br /> |-<br /> | Time: || 10:30 - 11:20<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Martin Dougiamas<br /> |}<br /> <br /> ===Social Networking tools===<br /> {|<br /> |-<br /> | Time: || 11:20 - 12:00<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Jenny Gray<br /> |-<br /> |} <br /> <br /> The aim is to discuss recent user tagging in Moodle and how it can be used; to think about what else can be tagged (courses, resources, activities etc); and to think about how Moodle can be made more social. Here are some suggestions made to me recently:<br /> <br /> * Learning twitter<br /> * Learning shared to do <br /> * Offering self-organising groups of learners their own activity areas (forums etc)<br /> * shared activity reports<br /> <br /> === Accessibility demonstration ===<br /> My colleague Chetz Colwell and I would like to give a brief demonstration of assistive technologies to developers, particularly core developers, and discuss future accessibility work on Moodle. We'll hopefully have a screen reader JAWS (Thunder?), screen magnifier, do a keyboard-only demo, and possibly speech recognition.<br /> {|<br /> |-<br /> | Time: || 12:00 to 12:40<br /> |-<br /> | Room: || CMR15<br /> |-<br /> | Suggested by: || Nick Freear<br /> |}<br /> <br /> ===Quiz developments===<br /> {|<br /> |-<br /> | Time: || 1:40 to 2:20<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Tim Hunt<br /> |}<br /> We can discuss some things that have happened recently:<br /> * The implication of [[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Jamie's recent changes to the question bank]],<br /> * Improvements to the question type API, especially [[Development:Plans_for_enhancing_import/export_in_questiontype_plugins|Howard's recent changes]],<br /> some things that will probably happen soon:<br /> * The OU's quiz navigation changes, that we hope to put into Moodle 2.0,<br /> * The OU's [[Development:Plans_for_adaptive_mode|changes to adaptive mode]] that we hope to put into Moodle 2.0,<br /> * Tony Gardner-Medwin's plans to introduce certainty-based marking,<br /> known problems with the quiz architecture that no-one is working on right now:<br /> * ... suggestions welcome ...<br /> and anything else you want to raise.<br /> <br /> Of course, you can talk to me about the quiz at any time time during the day too, if you have a more specific issue.<br /> <br /> ===ePortfolios===<br /> {|<br /> |-<br /> | Time: || 2:20 to 3:00<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Thanh Le<br /> |}<br /> A quick overview of the Open University electronic portfolio tool and describing its technical underpinning to provide more background information.<br /> <br /> From the session, I am keen to:<br /> * gauge people's interest in the tool;<br /> * discuss how the tool can integrate with other Moodle tools around the concept of personal data storage;<br /> * gather interest and collaboration;<br /> <br /> ===Conditional Activities===<br /> The aim is to develop some consensus on how it can work so that a spec can be started.<br /> {|<br /> |-<br /> | Time: || 3:00 - 3:40<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Martin Dougiamas<br /> |}<br /> <br /> ===Offline Moodle (and particularly synchronisation issues)===<br /> Offline Moodle reuses the core components on Backup and mNet(Moodle Network) and adds a synchronisation component to take care of tasks that Moodle doesn't already cater for. <br /> <br /> The components are used because they are core components. They already offer functionality that we require and as they evolve the Offline Moodle feature will be able to take advantage of the extra features, functionality and reliability they provide. <br /> <br /> Because this is a new feature I'll explain a little about how we use the comments and then jot a few questions down that have come up:<br /> Backup and restore is used to get information in and out of Moodle in a standardised format well understood by Moodle. It is supported by most modules and features and is likely to be fixed quickly as changes to modules effect the backup process.<br /> * Will the backup tool scale effectively<br /> * Will changes for Offline Moodle harm the backup code? <br /> <br /> Moodle Network is used to provide web service functionality. <br /> * is Moodle Network the best option for this? <br /> * has the web service been implemented correctly?<br /> <br /> Synchronisation (Synch) Component<br /> This component is really the main controller of synchronisation whic is the key feature of Offline Moodle at this time. We've spent a lot of our time developing code to get the content in and out of Moodle and transferred between Moodles in a reliable and well managed fashion. The synch component brings all this together. <br /> <br /> So far we've proven that we can reliably get course content and related module content from Moodle Server to Offline Moodle. For forums we can get it back again. We've investigated lots more but haven't code it yet. <br /> <br /> We would like the communities input. The plan is to improve it by adding functionality such as: <br /> * merging content: this is a key feature. For example merging a forum discussion with posts from the Offline Moodle and the Moodle Server. Our original proof of concept proved this is possible for forums but the code has not been written for Offline Moodle<br /> * filtering content: passwords, copyrighted material and other sensitive data all need to be removed at certain points through out the process<br /> * security: checks for hacking, viruses and trojans, making sure the data doesn't get changed in transit. These are all key issues that need to be addressed.<br /> <br /> {|<br /> |-<br /> | Time: || 3:40 - 4:20<br /> |-<br /> | Room: || CMR07<br /> |-<br /> | Suggested by: || Colin Chambers<br /> |}<br /> <br /> ==Other things people want to do during the day==<br /> <br /> === PGP Keysiging ===<br /> If any developers would like to exchange PGP Keys and expand their web of trust then this could be done during the Developer day. <br /> <br /> I think it would be good to follow the [http://www.debian.org/events/keysigning Debian guidlines] for this.--[[User:Dan Poltawski|Dan Poltawski]] 18:03, 10 October 2007 (CDT)<br /> <br /> ===Enrollment 'Groups'===<br /> I would like to discuss the concept of enrollment groups and thoughts on the reasons for such a feature to be incorporated into Moodle. It would be a useful opportunity to discuss approaches with developers. This is with the intention of implementing a solution and offering it for inclusion into core when I work on this in the coming months. --[[User:Dan Poltawski|Dan Poltawski]] 16:46, 16 October 2007 (CDT)<br /> <br /> ===Bug fixing prize?===<br /> <br /> Should we offer a prize for the person who fixes most bugs during the day?--[[User:Tim Hunt|Tim Hunt]] 03:46, 14 October 2007 (CDT)<br /> <br /> Sorry I won't be there,<br /> Ok if you mean somebody submitting the larger number of proposals approved by at least one of the participants, on how to solve various bug. No real code please, if you don't want to create new ones...[[User:Pierre Pichet|Pierre Pichet]] 18:34, 19 October 2007 (CDT)<br /> <br /> ==See also==<br /> <br /> * [[Developer conferences]]<br /> * [http://moodle.org/mod/forum/view.php?id=55 General Developer Forum]<br /> <br /> [[Category:Developer]]</div>

Colchambers https://docs.moodle.org/37/en/index.php?title=Development:MoodleMoot_2007_HackFest&diff=27927 2007-10-18T11:09:29Z

<p>Colchambers: /* Offline Moodle (and particularly synchronisation issues) */</p> <hr /> <div>The main part of the [http://moodlemoot.org/ 2007 UK Moodle Moot] is on Wednesday and Thursday 24th and 25th October. The day before, on the Tuesday, there will be a HackFest for developers to meet, talk and write code.<br /> <br /> ==Practical arrangement==<br /> <br /> You need to get [http://maps.google.co.uk/maps?ll=52.025356,-0.710997&amp;spn=0.001005,0.001904&amp;t=k&amp;z=19 right here]. This is the centre of the Open University's Campus:<br /> <br /> [http://www3.open.ac.uk/contact/ The Open University]&lt;br /&gt;<br /> Walton Hall&lt;br /&gt;<br /> Milton Keynes&lt;br /&gt;<br /> [http://maps.google.co.uk/?q=mk7+6aa&amp;ie=UTF8&amp;om=1&amp;f=d MK7 6AA]<br /> <br /> The area we are meeting in is called the Christodoulou Meeting Rooms. The entry is under an archway, and if you go in and up the stairs you should find us in Meeting Room 15, or the open foyer area just outside it. We will be there from about 10:00am to about 5:30pm, and lunch will be provided.<br /> <br /> If you are registered for the MoodleMoot, wireless network sign-in information should be available on arrival.<br /> <br /> ==Programme for the day==<br /> <br /> In keeping with Moodle's open source philosophy, the day will be self-organising. You can turn up and talk to other developers about anything you like. However, within that general free-for-all, we will have a number of pre-announced discussions on particular topics at particular times. We have a number of other rooms available for these break-out sessions, but I don't know the room numbers right now.<br /> <br /> Please feel free to add your own suggestions below.<br /> <br /> Naturally, not all developers will be able to come, so it might be a good idea to start discussing some of these topics in the [http://moodle.org/mod/forum/view.php?id=55 General Developer Forum] now. And if anything significant comes out of the discussions, we should try to record it on the wiki.<br /> <br /> ==Particular discussions==<br /> <br /> These are significant topics, where it might be worth getting about 5-10 interested developers into a break-out room for a focussed discussion on one topic, or a demonstration of a particular idea.<br /> <br /> Irrespective of these sessions, there will be other developers around talking about whatever interests them all day.<br /> <br /> === Accessibility demonstration ===<br /> My colleague Chetz Colwell and I would like to give a brief demonstration of assistive technologies to developers, particularly core developers, and discuss future accessibility work on Moodle. We'll hopefully have a screen reader JAWS (Thunder?), screen magnifier, do a keyboard-only demo, and possibly speech recognition.<br /> {|<br /> |-<br /> | Time: || 10:00 to 10:40<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Nick Freear<br /> |}<br /> <br /> ===Repository API===<br /> The aim is to develop some consensus on how it can work so that a spec can be started.<br /> {|<br /> |-<br /> | Time: || 10:40 - 11:20<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Martin Dougiamas<br /> |}<br /> <br /> ===Social Networking tools===<br /> {|<br /> |-<br /> | Time: || 11:20 - 12:00<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Jenny Grey<br /> |}<br /> <br /> ===Quiz developments===<br /> {|<br /> |-<br /> | Time: || 1:40 to 2:20<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Tim Hunt<br /> |}<br /> We can discuss some things that have happened recently:<br /> * The implication of [[Development:Plan_to_Improve_Flexibility_of_Question_Category_Sharing_and_Permissions|Jamie's recent changes to the question bank]],<br /> * Improvements to the question type API, especially [[Development:Plans_for_enhancing_import/export_in_questiontype_plugins|Howard's recent changes]],<br /> some things that will probably happen soon:<br /> * The OU's quiz navigation changes, that we hope to put into Moodle 2.0,<br /> * The OU's [[Development:Plans_for_adaptive_mode|changes to adaptive mode]] that we hope to put into Moodle 2.0,<br /> * Tony Gardner-Medwin's plans to introduce certainty-based marking,<br /> known problems with the quiz architecture that no-one is working on right now:<br /> * ... suggestions welcome ...<br /> and anything else you want to raise.<br /> <br /> Of course, you can talk to me about the quiz at any time time during the day too, if you have a more specific issue.<br /> <br /> ===ePortfolios===<br /> {|<br /> |-<br /> | Time: || 2:20 to 3:00<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Thanh Le<br /> |}<br /> <br /> ===Conditional Activities===<br /> The aim is to develop some consensus on how it can work so that a spec can be started.<br /> {|<br /> |-<br /> | Time: || 3:00 - 3:40<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Martin Dougiamas<br /> |}<br /> <br /> ===Offline Moodle (and particularly synchronisation issues)===<br /> Offline Moodle reuses the core components on Backup and mNet(Moodle Network) and adds a synchronisation component to take care of tasks that Moodle doesn't already cater for. <br /> <br /> The components are used because they are core components. They already offer functionality that we require and as they evolve the Offline Moodle feature will be able to take advantage of the extra features, functionality and reliability they provide. <br /> <br /> Because this is a new feature I'll explain a little about how we use the comments and then jot a few questions down that have come up:<br /> Backup and restore is used to get information in and out of Moodle in a standardised format well understood by Moodle. It is supported by most modules and features and is likely to be fixed quickly as changes to modules effect the backup process.<br /> * Will the backup tool scale effectively<br /> * Will changes for Offline Moodle harm the backup code? <br /> <br /> Moodle Network is used to provide web service functionality. <br /> * is Moodle Network the best option for this? <br /> * has the web service been implemented correctly?<br /> <br /> Synchronisation (Synch) Component<br /> This component is really the main controller of synchronisation whic is the key feature of Offline Moodle at this time. We've spent a lot of our time developing code to get the content in and out of Moodle and transferred between Moodles in a reliable and well managed fashion. The synch component brings all this together. <br /> <br /> So far we've proven that we can reliably get course content and related module content from Moodle Server to Offline Moodle. For forums we can get it back again. We've investigated lots more but haven't code it yet. <br /> <br /> We would like the communities input. The plan is to improve it by adding functionality such as: <br /> * merging content: this is a key feature. For example merging a forum discussion with posts from the Offline Moodle and the Moodle Server. Our original proof of concept proved this is possible for forums but the code has not been written for Offline Moodle<br /> * filtering content: passwords, copyrighted material and other sensitive data all need to be removed at certain points through out the process<br /> * security: checks for hacking, viruses and trojans, making sure the data doesn't get changed in transit. These are all key issues that need to be addressed.<br /> <br /> {|<br /> |-<br /> | Time: || 3:40 - 4:20<br /> |-<br /> | Room: || ??<br /> |-<br /> | Suggested by: || Colin Chambers<br /> |}<br /> <br /> ==Other things people want to do during the day==<br /> <br /> === PGP Keysiging ===<br /> If any developers would like to exchange PGP Keys and expand their web of trust then this could be done during the Developer day. <br /> <br /> I think it would be good to follow the [http://www.debian.org/events/keysigning Debian guidlines] for this.--[[User:Dan Poltawski|Dan Poltawski]] 18:03, 10 October 2007 (CDT)<br /> <br /> ===Enrollment 'Groups'===<br /> I would like to discuss the concept of enrollment groups and thoughts on the reasons for such a feature to be incorporated into Moodle. It would be a useful opportunity to discuss approaches with developers. This is with the intention of implementing a solution and offering it for inclusion into core when I work on this in the coming months. --[[User:Dan Poltawski|Dan Poltawski]] 16:46, 16 October 2007 (CDT)<br /> <br /> ===Bug fixing prize?===<br /> <br /> Should we offer a prize for the person who fixes most bugs during the day?--[[User:Tim Hunt|Tim Hunt]] 03:46, 14 October 2007 (CDT)<br /> <br /> ==See also==<br /> <br /> * [[Developer conferences]]<br /> * [http://moodle.org/mod/forum/view.php?id=55 General Developer Forum]<br /> <br /> [[Category:Developer]]</div>

Colchambers