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

Setting up Gitpod for development #67

Open
wants to merge 22 commits into
base: staging
Choose a base branch
from

Conversation

zack-overflow
Copy link

Motivation

From the additions to the Contributing.md explaining Gitpod:

Layup List has a number of old dependencies and technologies and uses python 2.7.16, which is deprecated as its main language. These factors can make setting up a local development for Layup List a little precarious and often frustrating.

Implementation

Gitpod uses a .gitpod.yml file as "environment-as-code" and allows you to define a number of "tasks" to configure the development environment.

Usage

Gitpod works with most popular editors, including terminal-based editors, VS Code, and JetBrains IDEs. The steps for trying it out with Layup List are in this wiki.

Demo (screenshots, animations)

Will try to add ASAP

Referenced Issue(s)

#61

The call to environment.sh seems to not be doing anything besides running `heroku local: run zsh`, the main benefit of which is that it exports the environment variables from .env, which we can do with gitpod in this case. Removing the call eliminates an issue with the init task of the gitpod.yml
Long-running commands like installing a python version are better in the init task if they only need to be run once per workspace.
@zack-overflow
Copy link
Author

As an admin point: These commits should probably be squashed if the changes are merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant