FAQ | QUICK ACCESS
Right. It is. This is a deliberate choice of engageLively, to ensure that the interface is immediately understandable to Jupyter Notebook authors. We are extending it, using the standard JupyterLab extension architecture, and are contributing our extensions (such as Galyleo Presentation Studio) to the open-source community.
An environment is a set of pre-loaded libraries, to save you from having to “pip install” in every Notebook you create. We’ve picked several popular environments to pre-load; if there’s one you prefer, please let us know at support@engageLively.com.
A private server is getting cloned, with the environment you have selected. It will continue to run until you choose “Stop Server” from the control panel.
As many as you want. Note, however, that the memory and CPU caps are on a per-server basis, so multiple Notebooks will be consuming from a common pool of CPU and RAM.
Yes, just use the standard !pip install line in the notebook, or run pip from the built-in terminal.
If you log out, the server and all processes remain running. Next time you log in, instead of seeing the screen to Spawn a server, you’ll go right back into your running Notebook server. All Notebook tabs are lost, but if you reopen the Notebook you’ll see its state is retained. Please note that if no browser is connected, the Free tier server will timeout after 3600 seconds and the Lite tier will time out after 14400 seconds.
You can think of your server as a Linux computer in the Cloud, and it has all the standard Linux tools installed; in particular, wget, pip, git, and apt-get. Also, the upload button (2nd from the right above the menu bar) uploads files from your computer.
In the file view, right-click on the file you want to download and select “Download” from the popup menu. You can also export your Notebooks in a variety of formats using the “Export Notebook As…” selection on the File Menu.
Yes, pip is installed and can be used to instantiate libraries.
There is a GitHub extension for JupyterLab, which we’ll install soon. Until then, use your local device as an intermediary or install the git command-line tools in a Terminal to use those.
We do not explicitly add encryption layers. While data is only accessible to you, you should not upload sensitive data.
The standard Python libraries (urllib) are installed on the system. Also, the terminal has the standard wget utility to load into a local file.
Upload the appropriate credentials into the .ssh directory in your server, ensuring that the appropriate permissions are set. E.g.
$ ssh -i ~/.ssh/my_key.rsa foo@my_remote_system.com
We are working on solutions which will attach external file systems, object stores, private and public github repos to Galyleo Hubs. Until that is in place, we suggest you use upload/download. We will have this in place shortly, so keep watching this page!
The Galyleo Public Hub is administered by engageLively: engageLively chooses the environments, external file systems attached, users who can access the hub, login methods, etc. An enterprise Hub is configured by the local administrator on setup, which involves choosing the local environments, attaching file systems, adding users, configuring login methods, etc.
Your files will persist between sessions. However, we do not specifically back up the contents of your servers beyond what is possible at the cloud provider’s cluster level. Therefore it is up to you to maintain backups to guard against user actions such as accidentally deleting or overwriting your own files.
If you log out, the server and all processes remain running. Next time you log in, instead of seeing the screen to Spawn a server, you’ll go right back to your running Notebook server. All Notebook tabs are lost, but if you reopen the Notebook you’ll see its state is retained. Note that Servers do timeout (currently four hours) if no browser is connected.
Yes. However, you will need to ensure that any library dependencies are taken care of.
Yes. The dashboard studio and associated Python libraries are extensively documented at https://galyleo-user-docs.readthedocs.io. In addition, there is a repository of demos and tutorials at https://github.com/engageLively/galyleo-examples. A number of tutorials and videos have been posted at engageLively’s YouTube channel.
Both Galyleo Connect and Galyleo Studio are free and open-source; at the moment, only Galyleo Connect is available for free download. We are preparing the Galyleo JupyterLab extension and the Galyleo Studio Page for download and release.
Galyleo Connect’s initial client uses Jupyter’s internal messaging protocol. We will deploy a general socket.io client in the near future, and at that time the Dashboard studio can be used from any Python client (or any client that can use this Python library).
Soon we will offer products that allow you to have access to multiple hubs and cloud resources. So you will want the ability to log out of specific hubs but still remain logged in to enagelively to manage your account. Instead of removing the login button now and then adding it back shortly after when we roll out the other products, we’ve decided to leave both buttons as they are for now.
If you are at the Free, Lite, or Pro Tier, the upgrade is automatic. If you are already at the Gold tier and want to go to the unmetered tier, contact us at support@engageLively.com. We will respond very quickly.
You’ve stopped your server but a second browser window is open into it. Kill that browser window, and open up the page again. You’ll be directed to the start-server screen. We’re working on a workaround on this. Alternatively, clicking the refresh button may also work.
Google has set a cookie that enforces a same-origin policy on displayed pages. Remove cookies from this page (how do to this is browser-specific; for Chrome, click on the lock icon at the left of the address bar, select Cookies, then select all Cookie folders and hit “remove”.
3. Future Features
Yes. This is on the roadmap for future implementation.
Yes. We are expecting to add this functionality later.
Yes. This is on the roadmap.
We plan to write open-source R and Julia libraries for Galyleo Connect, but we don’t have firm dates for their availability. Since the libraries will be free and open-source, independent of who writes them, we’ll support anyone who wants to do this.
Please contact support@engageLively.com if you’re interested.
Yes. Some familiarity with OAuth will be required for the Hub Administrator to set this up.
Yes. We expect to offer Galyleo Bring Your Own Cloud in the near future. In this product, you will open a Google or AWS account and offer us IAM permission to bring up and operate your Galyleo Hub, for which we will charge a management fee.
Contact us at support@engageLively.com if you are interested.
We expect to offer an on-premises installed offering in the near future.
Yes. This is on the roadmap for the near term.
Yes. We’ll post a list, with dates.
4. Connecting with engageLively
First, thank you! Our goal is to make this a system you’ll love, and so we love to hear about feature requests! We don’t guarantee to be able to implement them all, but we guarantee to take each request very seriously.
Please send mail to support@engageLively.com.
Please send mail to support@engageLively.com with as much information as you can: environment, time, screenshots if you can manage it.
As with feature requests, we take these very, very seriously and will respond promptly.
Many. Galyleo offers JupyterLab from the Project Jupyter, and Project Jupyter has done an excellent job of documenting features.
We suggest starting at https://jupyterlab.readthedocs.io/en/latest/user/interface.html
Please see the examples at https://github.com/engageLively/galyleo-examples. This has a suite of demo examples and a number of Notebook and Dashboard tutorials. In addition, there is a full suite of documentation at https://galyleo-user-docs.readthedocs.io/.
Please send us a message if you have a question, need support or have a new feature request.