Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add jupyter-desktop-server #21369

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
43 changes: 43 additions & 0 deletions recipes/jupyter-desktop-server/meta.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
{% set name = "jupyter-desktop-server" %}
{% set version = "0.1.3" %}

package:
name: {{ name|lower }}
version: {{ version }}

source:
url: https://pypi.io/packages/source/{{ name[0] }}/{{ name }}/jupyter-desktop-server-{{ version }}.tar.gz
sha256: 5915a2dbbe250f59b3cc01859297b26b2e1836e03a5db4bfbfd438005649d7e4

build:
noarch: python
script: {{ PYTHON }} -m pip install . -vv
number: 0

requirements:
host:
- pip
- python >=3.8
run:
- jupyter-server-proxy >=1.4.0
- python >=3.8

test:
imports:
- jupyter_desktop
commands:
- pip check
requires:
- pip

about:
home: https://pypi.org/project/jupyter-desktop-server/
summary: Run a Linux Desktop on a JupyterHub
license: BSD-3-Clause
license_file: jupyter_desktop/share/web/noVNC-1.1.0/LICENSE.txt

extra:
recipe-maintainers:
- yuvipanda
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yuvipanda, similar to #21368, ok if I list you as a conda-forge recipe maintainer for jupyter-desktop-server here (need an explicit yes/no answer)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weiji14 so it was actually upstreamed into https://github.com/jupyterhub/jupyter-remote-desktop-proxy but no new release has been made yet. Should I make a release with the new name and we can try again?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah yes, that would be better. Give me a ping when the new release has been tagged.

- weiji14
weiji14 marked this conversation as resolved.
Show resolved Hide resolved
- manics