Meta-ticket: Gitpod usability improvements

[mkoeppe]

• Added gitpod badge to trac tickets:
  Image https://img.shields.io/badge/-Gitpod-908a85?logo=gitpod
  Link https://gitpod.io/#https://github.com/sagemath/sagetrac-mirror/tree/<branch>

• Improve vs code config #33450 Improve vs code config

• Gitpod: track remote trac branch #33589 Gitpod: track remote trac branch

• Migrate gitpod to conda #33739 Migrate gitpod to conda

• Add pip packages to conda environments, add missing conda.txt files #33613 Gitpod: Install git-trac-command

• Make docker-in-docker available in Gitpod #34255 docker

• Prebuild of develop branch is not available (probably because the prebuild of the develop branch still uses the old docker image)

• Prefer Linux package manager over linuxbrew; add nix detection #32753 Prefer Linux package manager over linuxbrew (or remove linuxbrew from the Docker image)

• in the terminal, viewing graphics silently does nothing

sage: polytopes.cube().show()
Launched html viewer for Graphics3d Object
sage: polytopes.regular_polygon(5).show()
Launched png viewer for Graphics object consisting of 7 graphics primitives

• The scipy folks have some good documentation and configuration (​https://scipy.github.io/devdocs/dev/contributor/quickstart_gitpod.html), perhaps we can lift something from there.

• Link to https://code.visualstudio.com/docs/datascience/jupyter-notebooks

• Link to https://www.gitpod.io/docs/configure/browser-settings

• Remove popup notifications:

  • "Snooty language server is not installed or out of date."

• Extensions for:

  • Cython
  • autoconf

• docbuild: Ignore "source directory has changed" #33354: Prebuild documentation in a way that incremental docbuilds are fast (#33103 comment:101); perhaps best done after pip-installable packages sagemath-doc-src, sagemath-doc-inventory, sagemath-doc-html, sagemath-doc-pdf #29868 (pip-installable packages sagemath-doc-html etc.)

• Add instruction on how to display build docs:

  • python3 -m http.server --directory ./local/share/doc/sage/html/ 8001
  • https://www.gitpod.io/docs/languages/html and https://www.gitpod.io/docs/config-ports
  • Should we start this sever automatically and display the build docs in a vscode browser tab?

CC: @tobiasdiez @dimpase

Component: user interface

Issue created by migration from https://trac.sagemath.org/ticket/33113

[mkoeppe]

Changed dependencies from #33103 to #30677, #33103

[mkoeppe]

Changed dependencies from #30677, #33103 to none

[mkoeppe]

comment:18

Ticket branches are often based on an older beta version. Given that we build on top of the Docker image for the current beta version (dev), shouldn't we attempt to merge the branch into the base of the Docker image and build that?

[tobiasdiez]

comment:19

Isn't this what the prebuild at gitpod is essentially doing?

[mkoeppe]

comment:21

Replying to @tobiasdiez:

Isn't this what the prebuild at gitpod is essentially doing?

No, it's not merging. It's building the top of the branch.

[tobiasdiez]

comment:22

Then I don't understand what you mean. The docker image used by gitpod is the same for all branches.

[mkoeppe]

comment:23

Yes, it is, and it is based on the latest beta.

The branch that is being tested, however, may be based on a much older beta. When building this branch, it will downgrade packages to the versions recorded in that older beta.

[tobiasdiez]

comment:24

Yes, that's the current behavior, right? So what are you proposing to improve there?

[mkoeppe]

comment:25

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

[tobiasdiez]

comment:27

Replying to @mkoeppe:

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

So you want to merge the develop branch into the branch that is open in gitpod?

Note also that gitpod prebuild the branch when a new commit arrives. Thus the docker image used is the one that had been published when the branch had its last commit.

[mkoeppe]

comment:29

Replying to @tobiasdiez:

Replying to @mkoeppe:

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

So you want to merge the develop branch into the branch that is open in gitpod?

Technically not the develop branch but the ref from which the Docker image has been built. Most of the times, that's the same.

[mkoeppe]

comment:30

Replying to @tobiasdiez:

Note also that gitpod prebuild the branch when a new commit arrives. Thus the docker image used is the one that had been published when the branch had its last commit.

Yes, that's fine.