Developing in a Dev Container
This project provides partial support for developing in a dev container. We are still working on this feature, but once it is ready, it should make the onboarding process much easier. At that point, it would be the recommended way to develop this project.
Why use a dev container?
The main reason to use a dev container is to make the onboarding process as easy as possible. With a dev container, you can get started with this project with just a few clicks. You don't need to install any dependencies on your machine, and you don't need to worry about setting up your environment. Everything is already set up for you.
Getting started
Prerequisites
- Visual Studio Code version 1.60.0 or higher.
- Docker version 20.10.8 or higher.
- Remote - Containers extension for Visual Studio Code.
INFO
For now, you must change "file sharing implementation" from VirtioFS to gRPC fuse in the Docker settings. See oven-sh/bun#4923 for more details.
INFO
For now, you must rebuild the container using ⌘
⇧
P
→ Dev Containers: Rebuild Container
after building the container the first time. See #55 for details; PRs welcome.
Setup
- Clone the repository
$ gh repo clone agnyz/the-bed-stack
$ cd the-bed-stack
$ gh repo clone agnyz/the-bed-stack
$ cd the-bed-stack
Open the project in a dev container
- Open the command palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows/Linux) and select Remote-Containers: Open Folder in Container....
- Select the project folder.
- Wait for the container to build and open the project in a new window.
🎉 You're ready to go!
What's Next?
- Please report any issues you encounter with the dev container in GitHub Issues, with the
devcontainers
label.