ciphereditor
ciphereditor copied to clipboard
wierkstudio
Dev container configurations into dev branch
Add certain configurations that allow for the repository to be seamlessly opened in a local dev container in VSCode, Docker Dev Containers, or GitHub Workspaces. Also add configuration for VSCode Monorepo workspace support
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Updated |
|---|---|---|---|
| ciphereditor | ✅ Ready (Inspect) | Visit Preview | Aug 31, 2022 at 8:32PM (UTC) |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Awesome! Thank you! How should we let people know about all of this in the README? Should we add a badge like in https://github.com/microsoft/vscode-remote-try-node?
If you want, I can update the README with these setup steps and add the VSCode Remote Containers badge
Yes, please! It would round off this pull request. I'd keep the dev container setup as an alternative to the current setup, though. Let's divide the development setup section into two.
Ok, I finally managed to fix my docker setup after realizing that I had to install some kernel modules and then forgetting to restart cus of new kernel. But alright let me do that rq
@robigan I've committed my suggestion for the README into the PR. What do you think?
After further thought I'm making the conventional setup the primary option here as it does not require the use of Docker or Visual Studio Code. Still, I want to roll with dev containers and see where it leads us. I hope you can relate.
I totally agree, that is why I left the conventional setup at the top of the setup instructions, as those are the first instructions the human eye will see. If you're willing to mark it as primary to make it easier, then please go ahead
@robigan I've committed my suggestion for the README into the PR. What do you think?
TBH you did a much better job than I did, your changes on the README or way cleaner than mine hahaha