Running the GTN website online using GitHub CodeSpaces

Author(s) orcid logoSaskia Hiltemann avatar Saskia Hiltemann
Editor(s) Teresa Müller avatar Teresa Müller
Reviewers Helena Rasche avatar Saskia Hiltemann avatar
Overview
Creative Commons License: CC-BY Questions:
  • How can I get a preview of the GTN website using GitHub CodeSpaces?

Objectives:
  • Preview the GTN website online via CodeSpaces

  • Make changes to the GTN website and preview those changes

  • Save the changes to your fork of the GTN repo

  • Create a pull request (PR) based on your changes

Time estimation: 30 minutes
Supporting Materials:
Published: Nov 11, 2024
Last modification: Dec 4, 2024
License: Tutorial Content is licensed under Creative Commons Attribution 4.0 International License. The GTN Framework is licensed under MIT
purl PURL: https://gxy.io/GTN:T00471
version Revision: 3

If you are working on your own training materials and want preview them online without installing anything on your computer, you can do this using GitHub CodeSpaces! Everybody gets 60 free hours of CodeSpaces per month.

Agenda

In this tutorial, you will learn how to contribute to the GTN website:

  1. Launching CodeSpaces
  2. The VScode environment
  3. Build and preview the GTN website
  4. Editing Training Materials on CodeSpaces
  5. Saving your changes back to GitHub
  6. Closing your CodeSpace

Launching CodeSpaces

Hands-on: Setting up GitPod
  1. Create a fork of the GTN GitHub repository

    The fork button on GitHub

  2. Already have a fork of the GTN? Make sure it is up to date.

    If you created your fork a long time ago, the default branch on your fork may still be called master instead of main

    1. Point your browser to your fork of the GTN repository
      • The url will be https://github.com/<your username>/training_material (replacing with your GitHub username)
    2. Check the default branch that is shown (at top left).

      Github with the top bar of a repository shown, including the button for 'Sync Fork'

    3. Does it say main?
      • Congrats, nothing to do, you can skip the rest of these steps
    4. Does it say master? Then you need to update it, following the instructions below

    5. Go to your fork’s settings (Click on the gear icon called “Settings”)
    6. Find “Branches” on the left
    7. If it says master you can click on the ⇆ icon to switch branches.
    8. Select main (it may not be present).
    9. If it isn’t present, use the pencil icon to rename master to main.

    Whenever you want to contribute something new to the GTN, it is important to start with an up-to-date branch. To do this, you should always update the main branch of your fork, before creating a so-called feature branch, a branch where you make your changes.

    1. Point your browser to your fork of the GTN repository
      • The url will be https://github.com/<your username>/training_material (replacing ‘your username’ with your GitHub username)
    2. You might see a message like “This branch is 367 commits behind galaxyproject/training-material:main.” as in the screenshot below.

      Github with the top bar of a repository shown, including the button for 'Sync Fork'

    3. Click the Sync Fork button on your fork to update it to the latest version.

    4. TIP: never work directly on your main branch, since that will make the sync process more difficult. Always create a new branch before committing your changes.

  3. Navigate to your fork of the GTN

  4. Click on the green Code button

  5. At the top, switch to the CodeSpaces tab the codespaces tab of the menu.

  6. Click on Create codespace on main
    • Note: if you switch to a specific branch in GitHub first, you can create a codespace for that branch
  7. This will setup a Visual Studio Code environment for you
    • It may take a couple minutes to finish setting everything up
    • In this environment you can also build the GTN website to preview your changes
    • When everything is ready, you should see something like this:

    screenshot of Codespaces just after startup.

The VScode environment

Let’s have a closer look at your CodeSpaces window:

  • Left: Here you see all the files in the GTN repository
  • Top: This is the main window where you can view and edit files
  • Bottom: Terminal window. Here you can type commands (e.g. to build the website preview) and read output and error messages.

VScode interface.

Build and preview the GTN website

Before we start making any changes, let’s build the website and get a live preview.

Hands-on: Setting up GitPod
  1. In the terminal window (bottom), type the following command: make preview

    • This will take 2-3 minutes to complete

    output in the terminal after issuing the make preview command.

  2. When the build process is finished, a preview window will automatically open (at the top right)
    • The preview will show the GTN 404 (codespace doesnt know what to show)
    • Just click on Return to homepage.

    If the preview window doesn’t open for you, or if you close it and want to reopen it, you can always do so as follows:

    1. Go to the Ports tab of the bottom panel

      screenshot of the tabs on the bottom panel.

    2. Hover over the link in the Forwarded Address column, 3 icons should appear

      screenshot of the 3 icons.

    3. Click on:

      • The world/globe icon to open the GTN preview in a new window, or
      • Or, click on the window icon to the right of the globe icon to preview the GTN in a tab inside the codespaces environment
  3. If you opened the GTN preview inside the codespace, your window will now look something like this:

    screenshot of the codespace with the preview editor opend to the GTN homepage.

    screenshot of firefox permissions dialog which shows blocked windows and an allow menu. Some browsers block popups by default, you may need to allow CodeSpaces to show popups in your browser.

Editing Training Materials on CodeSpaces

Now that you have the codespace environment working and we have a live preview up, let’s make some changes to the GTN materials and get an instant preview.

Scenario: You have spotted a typo in one of the tutorials, and would like to fix this and see the resulting GTN webpage.

Hands-on: Make and view changes
  1. In the preview of the GTN website, open the following tutorial:
    • Topic: “Introduction to Galaxy Analyses” topic
    • Tutorial: “A Short Introduction to Galaxy””
    • We will edit this tutorial and watch the live preview window for the effects
  2. On the file browser on the left, open the following file:

    topics/introduction/tutorials/galaxy-intro-short/tutorial.md
    
  3. Change the title of the tutorial
    • From: “A Short Introduction to Galaxy”
    • To: “A Short and Cool Introduction to Galaxy”

    we changed the title of the tutorial in the text editor window.

  4. Save the file
    • CTRL+S to save the file
    • You should immediately see a message in the terminal saying “regenerating”. CodeSpaces has detected your changes and is rebuilding the website.

    the terminal shows a message stating the website is being regenerated.

  5. Move to the top right panel where the GTN is previewed and refresh the website
    • galaxy-refresh Refresh button in front of the address bar of the preview panel
    • You can also open the preview in it’s own brower tab, using the galaxy_instance button at the top-right corner of the preview window. Then you can reload the page the regular way (e.g. F5 or ctrl + r or the reload button in the browser)

    It is possible that this reload button gives you the 404 again, in that case there are 2 solutions

    1. Right-click in the preview panel, and choose
      • Chrome: “Reload Frame”
      • Firefox: “This Frame -> Reload Frame”
    2. Open the preview in it’s own browser tab
      • Click the galaxy_instance button at the top-right corner of the preview window
  6. You should see the change you made:

    The updated preview with our changed tutorial title.

In this way you can edit files in the text editor, and see the effects in the website preview.

Saving your changes back to GitHub

When you have finished your changes, it all looks good in the preview, you want to save your changes back to GitHub so that you can either continue later, or make a Pull Request to the GTN to contribute your changes.

Hands-on: Comitting changes

Before you can commit your changes you have to create a branch. You have two options to preform this task:

  1. Option 1: via the terminal
    • Hit ctrl+c if your preview was still running to stop it
    • Create a new branch, commit your changes, push changes:
   git checkout -b fix-title
   git commit -m "update tutorial title" topics/introduction/tutorials/galaxy-intro-short/tutorial.md
   git push origin fix-title
  1. Option 2: via the web interface
    • Create a new branch:
      • On the bottom-left, click on the branch logo (probably labelled “main”) button on the bottom of the page with the current branch.
      • Enter fix-title as the name for your new branch (at top of window) Addint a new branch.
      • Choose “+ Create new branch…” from the dropdown
    • Commit changes:
      • On the left menu, click on the “changed files” tab button on the left menu to show changed files.
      • You should see your changed file (tutorial.md)
      • Click on the “+” icon next to the file we edited to stage changes stage changes button.
      • Enter a commit message (top of window)
      • Hit the checkmark icon below the massage to commit the changes - Publish changes
    • Click the cloud button at bottom left to publish your changes publish changes button.

Next, we will see these changes to on your branch/fork. We will do this from outside of our codespace.

Hands-on: Pushing changes to GitHub
  1. In your browser (outside of codespaces), navigate to the GTN GitHub page
  2. GitHub will helpfully show you any recent branches you’ve pushed to your fork
    • Click the Compare & pull request button to create a PR for your changes compare and pull request button on the new branch.

Closing your CodeSpace

Everybody gets 60 hours per month for free on CodeSpaces. Your codespace will automatically shut down after 30 minutes of inactivity, but it is always a good idea to close your CodeSpace when you are finished with it, to conserve your quotum.

Hands-on: Shutting down your CodeSpace
  1. Return to the GTN GitHub page

  2. Click on the green Code button again

  3. Under the Codespaces tab, you should see your running codespace

    codespaces menu in github.

  4. Click on the 3-dots menu to the right of your (randomly generated) codespace name

  5. In this menu you can quit your codespace in two ways:

    • Stop codespace: your changes will be kept and you can restart the codespace later
    • Delete your codespace. Any changes you did not commit and push to GitHub are lost. screenshot of the codespace options menu.

    • In this menu you can also resume a stopped codespace by simply clicking Open in Browswer

Congrats! You learned how to contribute to the GTN by using the CodeSpaces environment!