dogi / ole--vagrant-vi Goto Github PK

1.0 6.0 8.0 47 KB

Batchfile 40.04% PowerShell 59.96%

ole--vagrant-vi's Introduction

Installation

ole--vagrant-vi gives you the ability to install your own community BeLL (Basic e-Learning Library), including all its dependencies, on your system. To install it, please follow the directions for your OS.

Windows

We wrote two different scripts to install the community BeLL and its dependencies on your computer. They are equivalent, so if you run Windows 8.1 or above, you can use either of the two. If you like, you can also try both and provide us with feedback on which one worked better for you. It is not required to try both, but we would be grateful if you decide to do so.
To run the script, just copy and paste one of the lines below in a Command prompt opened as administrator.

Windows 8.1 and above

@powershell -Command "(New-Object Net.WebClient).DownloadFile('https://raw.githubusercontent.com/dogi/ole--vagrant-vi/master/windows/install.ps1', 'install.ps1')" && @powershell -NoProfile -ExecutionPolicy Bypass -Command ".\install.ps1"

Windows 7 and above

powershell -Command "(New-Object Net.WebClient).DownloadFile('https://raw.githubusercontent.com/dogi/ole--vagrant-vi/master/windows/install.bat', 'install.bat')" && start install.bat && exit

To run your community BeLL at the end of the installation, please, find the MyBeLL icon on your desktop and double click on it. It will open a Firefox browser and take you directly to your community BeLL webpage.

Dependencies

These programs will be automatically installed on your computer:

Chocolatey
Chocolatey is a package manager for Windows that we use to install/uninstall all the other programs in a simple and reliable way.
Bonjour
Bonjour is used to implement zero-configuration networking on your computer.
Git
Git is an open source version control system that we use for communication and management for our software. More specifically, we use gitter.im for communication and github.com for software management.
VirtualBox
Virtualbox allows you to install a software virtualization package as an application on your OS.

Note: if you already have VirtualBox installed on your computer and have existing VMs on virtualbox already, running the command above to reintall VirtualBox won't affect/wipe out your existing VMs; it will just add the OLE VM to the ones you have.

Vagrant
Vagrant is an open source tool for building development environments.
Firefox
Firefox is a popular browser, which is guaranteed to work nicely with your community BeLL.

MacOS(X)

Open your Terminal. We assume that brew is already installed.

    brew install git 
    brew cask install vagrant
    brew cask install virtualbox

Ubuntu

    sudo apt-get install git
    sudo apt-get install virtualbox
    sudo apt-get install vagrant

MacOS(X) and Ubuntu ONLY

Install a communityBeLL on your OS

In your Terminal or Command Prompt, type:

git clone https://github.com/dogi/ole--vagrant-vi.git
cd ole--vagrant-vi
vagrant up

You now have a working communityBeLL on your OS.
It is advisable to use Firefox to access your community BeLL, so if you don't have it already on your system, you may want to download it.

ole--vagrant-vi's People

Contributors

Stargazers

Watchers

Forkers

aberdean fanisgk lmmrssa hikaruit15 waryhermit jmgamer12 sarvanivadali sarah-lu102

ole--vagrant-vi's Issues

Command Prompt(Admin) for Windows 8.1 Script

OS: Windows 10 Pro

For the Command Prompt Script for Windows 8.1 and above, I had to run Command Prompt(Admin) in order for it to work. If i ran the script in the normal Command Prompt, my script would just stop at this position:

Should i go ahead and make the changes? something like:

Note:
You might be required to run Command Prompt(Admin) for the line below to work properly.

define important information explicit as variables

... so that they can be easily changed

port
repository

did I forget something?

Install fails to detect virtualization when Hyper-V is enabled and doesn't properly disable hyper-V

The installer script thought my CPU was not supported. SecondLevelAddressTranslationExtensions and VirtualizationFirmwareEnabled were listed as False. I other virtualization programs block you from even checking. I think you could fix this by rearranging the Hyper-V check before the VT-X check in the script, because when I ran the command "bcdedit /set hypervisorlaunchtype off" and restarted my computer it said I had VT-x.

But then when I ran the install script it said

Hyper-V is enabled on your computer. BeLL App cannot run with Hyper-V enabled. Disabling Hyper-V…

Hyper-V has been disabled. Please, reboot your computer, then install BeLL App again.

However it gave me the Hyper-V message again even after restarting. When I ran the command "Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All" in power shell and restarted it the script worked. I don't know why it didn't work when the script tried to turn it off.

vagrant version

– @dogi: need more investigation

An intern raised issue open-learning-exchange/open-learning-exchange.github.io#1367, claiming the latest version works fine.

Also related to #25

issues with take-home

I was not able to follow intructions of http://open-learning-exchange.github.io/#!pages/takehome.md in pairing the android app with community

After discussing with @dogi, we figured out that reason was this change

He also told that we had changed this because vagrant update from version 1.9.3 to 1.9.4 had broken our Vagrantfile on Windows'es only

after changing it back it manually everything worked fine on my Mac ;)

support for win7

Currently, there are some problems running the install scripts on Windows 7.
Specifically:

install.bat - check for virtualization gets bypassed and the script continues regardless of whether or not virtualization is actually supported or enabled
install.ps1 - several issues, some of which can be solved by upgrading PowerShell 2 to PowerShell 4 in Windows 7, and others that cannot, as follows,
- Don't work on Posh4
  - admin privileges
  - check for virtualization
- Work on Posh4
  - pause command
  - firewall rules
  - scheduled job

Task not propery created by powershell script.

The task is created OK, but it looks for the job/script information in ..\AppData\Local\Microsoft\Windows\PowerShell which was not present. But when I deleted the task and created it again using the exact code given in the install script it did create the information in the proper location. I read that Register-ScheduledJob only creates it for the current user, perhaps the install script runs as a different user somehow?

A potential work around would be to make the icon point to a powershell script that starts vagrant and then loads the URL so it only starts vagrant when people actually want to use it. Then no task is needed.

Consider signing install script or installer program

People should be reluctant to run unsigned scripts on their system. For now we can just point them to the script and them them decide if it is safe for themselves, but in the future it would be nice to have it signed so people don't have to change their execution policy to something unsafe to install the software.

Wrong Port for BeLL on Local

At the end of README.md,
It seems wrong port for BeLL on Local.

http://127.0.0.1:5984/apps/_design/bell/MyApp/index.html

should be

http://127.0.0.1:5985/apps/_design/bell/MyApp/index.html

comparing firewall part between bat and ps1

... made me realize that I favor the bat approach, which deletes the before created script.

Wonder if the approach of ps1 which is add a block rule is working as well

Please test