I have been setting up some IPython Notebooks on public servers for training purposes.
Once logged in, you are taken to the default landing page where you can choose the Notebook you want, create a new one and since IPython 2.0 navigate directories.
I would however like to serve a default Notebook upon logging in. This would make it possible for the student to log in and automatically be taken to a notebook that was set up with some instructions.
Of course he/she could just click on the link but it would just make it easier and better looking if it could start with a default page.
On pre 2.0 IPython clicking on a notebook link took you to a temporary kernel address (e.g. http://127.0.0.1:8889/10327f95-f1f6-4016-80f0-e23c477edbfe).
Since 2.0 these links are permanent so you can just provide direct notebook links to your students, e.g. http://127.0.0.1:8888/notebooks/Test.ipynb
Related
I have a notebook which links to other, local notebooks. Something like this:
This is a series of tutorials about X.
Link to [Tutorial 1](tutorial1.ipynb)
Link to [Tutorial 2](tutorial2.ipynb)
...
This works fine in normal jupyter, but not in Google Colab. The links get resolved to URLs like this: https://colab.research.google.com/drive/tutorial1.ipynb which is obviously not where this notebook is.
Is there another way to have local links that works in Google Colab?
If the Notebook is only in Colab, then this works for my use case, maybe for you too:
Right click on the Notebook in the file list view (see below).
Select Get shareable link
Copy the link, and use that:
Link to [Tutorial 1](https://drive.google.com/open?id=12bdw7VdhRhGFw2463wJ)
(That's a made-up link so it doesn't work.)
On the other hand, if it's in GitHub, you can use the link this way — using one of mine (in this repo) as an example:
[My notebook](https://colab.research.google.com/github/agile-geoscience/xlines/blob/master/notebooks/11_Gridding_map_data.ipynb)
Here's that place where you can get a link:
If you shared a Google Drive folder full of notebooks and data files, then it seems like the best way forward is to instruct people to open the other file from the Google Drive tab. That way you are all still working on the same copies of notebook files, which seems like the big advantage of Colab. It's not a link, but it may be the best workflow and it also keeps your notebooks a bit more platform neutral.
When I launch Jupyter with jupyter-notebook I get a redirect screen with the contents
This page should redirect to Jupyter Notebook. If it doesn't, click here to go to Jupyter.
I am then redirected to the Jupyter home screen that I expected to land on in the first place. After that everything seems to work fine.
Why am I being redirected when I launch Jupyter? Is there a way to prevent this from happening?
The page redirection is because of the recent security update to Jupyter notebook in merged pull request #4260: Launch the browser with a redirect file. From now on, the Jupyter will open the file, which will redirect to the browser thus passing the token without putting it in a command-line argument, which may be visible to other users otherwise.
This avoids putting the authentication token into a command-line argument to launch the browser, where it's visible to other users. Filesystem permissions should ensure that only the user who started the notebook can use this route to authenticate.
The new file included in PR is notebook/templates/browser-open.html:
{# This template is not served, but written as a file to open in the browser,
passing the token without putting it in a command-line argument. #}
I have problem previously with my WordPress, so I delete that one and re-install another one using the same "Click to deploy Wordpress". But the installing time is longer than before and still running after 30 min. The website seems up but the information part(password, phpMyadmin password..etc) doesn't come out.
Is there something wrong with my setting? or is because I delete and re-install too many times? or what should I do to fix it?
Below is the image:
the right side keep running more than 30 min
I have managed to reproduce this issue and found a workaround that you can use for now until it is resolved.
Launching the Wordpress service creates two VMs- one temporary “coord” VM that handles the Wordpress build and deployment, and a main WordPress VM that hosts Wordpress. The issue appears to arise when the “coord” VM is not able to retrieve a startup script needed to complete the build, specifically:
https://storage.googleapis.com/c2d-install-scripts/startup-script.sh
As a result of this, the coord VM continually and unsuccessfully attempts to retrieve “startup-script.sh”, and the WordPress installation remains stalled.
The cause of this appears to be that the “coord” VM doesn’t receive an external address upon it’s creation, preventing it from retrieving “startup-script.sh”.
In order to resolve this issue you can assign the coord VM an external IP address, which allows it to retrieve “startup-script.sh”, which in turn allows it to complete the WordPress setup/deployment process.
Instructions for the workaround
In the Compute Engine “VM instances” page, click on the “coord” VM (the machine name should contain the string “coord”)
Click Edit
Click on the network interface for the machine
In the External IP drop-down select “Ephemeral”
Click on “Done”
Click on “Save” at the bottom of the page
This will provide it with an external IP address and allow it to access the resources it needs to complete the setup.
I’ve reported this issue and you can click on the star icon to receive email notifications of any update on it.
When I run my Qt5 program as a superuser, the program completely ignores any system fonts, themes and icons and uses some bogus theme. See screenshot.
HOW to fix this programmatically or in any way possible??
It also ignores any KDE configs/qtconfig. This is driving me nuts.
Right is run as normal user, left is run as superuser.
Your config is being saved in your user's home. If you open app as root, it is working with root's settings. Easiest way to fix this would be graphical root login, than change settings to what you want and switch back to regular user. Root graphical login is disabled in most distros but you can still do it by using second terminal.
Press Alt+Ctrl+F2 to open a second terminal.
Login as root (password won't appear).
Type startx and press Enter, the GUI should start automatically.
Go for settings, set whatever theme you want, then log out.
Press Alt+Ctrl+F1 to go back to first terminal.
Everything should look nice from now on.
I'm looking to modify a language grammar in atom. However I'm not sure how to reload the grammar in order to test my changes. Do I need to quit and restart each time?
The grammar-live-reload was made for that purpose, so it's probably the most convenient way.
Reload automatically editors when grammars files (.cson) changes [...] Only editors that are affected by the selected language are reload[ed].
Otherwise, you can open the command-palette and run Window: Reload (this will also show its shortcut). You can do the same in from the developer tools' command-palette by running Reload Page or Hard Reload Page.