ManimCommunity / ManimCommunity/manim
Providing a Gitpod configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40.9k
- Forks
- 3.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 25
Description
Discussed in https://github.com/ManimCommunity/manim/discussions/2127
Originally posted by NicoWeio October 2, 2021
Today, I spent a few hours trying to automate the setup of a dev environment for Manim using gitpod.io, taking inspiration from https://github.com/ManimCommunity/manim/blob/main/.github/workflows/ci.yml and https://github.com/ManimCommunity/manim/blob/main/docker/Dockerfile.
While I was able to build/execute Manim in the generated container after some tries, I can't get it quite right.
Do you agree that providing a Gitpod (or GitHub Codespaces in the future) configuration is a good idea? In this case, can someone with more experience in Manim/Gitpod/Docker build a proper one? :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing .github/workflows/ci.yml and docker/Dockerfile, which the issue identifies as references for the development environment. Determine the missing Gitpod setup needed to build and execute Manim in the generated container; done means the configuration reliably provides that working environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- developer-experience, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100