How to move Open edX from one machine to another - openedx

I am setting up Open edX to the wrong machine. I want to Open edX move to another machine. Can it possible?
And Help needed to choose the right version of Open edX to install?

Not really possible with the currently open-sourced set of scripts. You will have to do another installation on the target machine.
The right version of OpenEdx install depends on the kind of users you're planning to serve.
For a minimal, production-like installation, you could try the native installation
For a quick testing, you could try the devstack installation
For an even quicker devstack installation experience, you can give tutor a try
For a one-click installation without much dependence on the internet, you could try the Bitnami installation
If you want to customize everything and install different components on different servers, you could refer to this repo and move ahead from there.

Related

OpenEDX development procedure

I'm currently trying to make my own platform based on OpenEDX and I'm working with devstack to do that. Am i right that I need to install fullstack on my server and make them share a git repository for update or is that not a right way to do that?
P.S. Sorry if it's not a right place for the question but I couldn't find a better one.
Basically you need to do Native installation on the server. And then share the git repository. Here is the link if you want to deploy all the services on the single instance, But if you want to setup a multi tier architecture then you need to deploy all the services separately using edx-ansible.

How to set-up vicidial in local system?

I want to set-up vicidial in my local computer server any information or a document for that?
I googled but I can't find exact resource.
I googled below links.
Link 1
Link 2
Thanks in advance.
Vicidial is an Open Source Predictive AutoDialer based on Asterisk with PHP/MySQL/Perl coding.
Installation of Vicidial is only viable on a Linux machine.
There are several locations with Scratch Install instructions for Ubuntu and CentOS. In fact, the Vicidial Wiki has a list of a few of them: http://wiki.vicidial.org/index.php/VICI:Installation
Most are quite old except for the Goautodial.com which has instructions for CentOS installation by adding the goautodial repositories and then just upgrading the OS to get all the necessary packages.
If you're not using CentOS or Ubuntu and none of those instructions work for your purpose, beware that Vicidial installation is not easy. It is MUCH better to dedicate a machine to the purpose by installing from Vicibox.com's .iso image which will wipe the computer clean. The installation becomes easy and then you need only argue with configuration.
If you can not dedicate a machine to this purpose, you should take the earlier suggestion of a Virtual server (vSphere or Virtualbox both work for Vicibox.com's .iso installer), but beware that you'll only be able to have one or two agents on the virtual dialer at the most. Luckily, if you do get the virtual vicidial working, it is possible to backup the virtual server's database and install it on a hardware based server later to bring everything with you without having to do it all over.

Advanced Installer - Install or Maintenance

I am using Advanced Installer and would like to know where do I configure when it needs to take the Installation process and when it need to take the Maintenance process. I am not sure if it is configurable. If not I would like to know how Windows decides which process to perform. help is very appreciated.
There is no need to configure that, the packages created by Advanced Installer know exactly when to go to install or maintenance phase, this is controlled by Windows Installer on each machine where you install the package. Try the simple installation tutorial to see how it works.
Basically, each package has guide, the product code, that is registered on the system by Windows Installer when you run it first and install your app. The second time you launch the same MSI Windows Installer will see the product code is registered as installed and automatically enter maintenance, showing the appropriate dialogs.
If you don't want a package to be enter maintenance phase, i.e. run only the install phase (every time you launch it) just go to Product Details page in your project and untick the option "Register product with Windows Installer".

Deploying a Rails app offline and with all dependencies intact

My goal is to deploy an existing Rails app on a machine. Oh, and the machine is on a handful of terminals in a remote community in the north of Australia. Oh, and I can't rely on there being Internet access for troubleshooting or admin purposes.
I'd like to package the app with a fresh copy of Rails and all of the apps dependencies (some of which must be built natively) so that the server can be run and a browser used as the front-end. The remote machines are modern Macs, and I should be able to replicate the configuration for testing here.
I've spotted some projects like Locomotive and Joyent Slingshot, as mentioned in this thread, but both of those projects seem to have been abandoned, and this link is Windows-specific.
Does anyone have any guidance as to what the modern way of doing this is? A community project thanks you in advance :)
Well, assuming those remove machines have Ruby available, you could use Bundler to freeze all your gems in your project:
bundle package
Read more at getbundler.com

Uninstall before installing a windows service

I am reading about how you can create an .exe that will install a windows service to the server.
Say I already have the windows service installed and I want to perform an update. Is there a way for the installer to uninstall (stop the service, delete it, uninstall it) the currently running service and then install the updated version?
Don't be that drastic -- if possible, just stop the service, replace the files you need to, and then (optionally) restart the service.
If you delete the service from the SCM, you lose any post-install configuration done by the user -- custom logon credentials, the settings that dictate what to do when the service crashes, etc.
You shouldn't need to create an exe to do this, the "sc" command can uninstall, update, and install services on Windows for you. See:
Using SC.EXE to Develop Windows NT Services
How to create a Windows service by using Sc.exe
If you still really want to do this by creating your own executable you certainly can, if you can let us know what language you're working in code samples can be provided.

Resources