I was investigating some of the test failures in https://github.com/coder/coder/pull/429 - and realized that we actually don't need the `http-proxy-middleware` package anymore (or the `express` package). Of course - the failures were unrelated to that change, so this doesn't fix the CI failures that were encountered. `http-proxy-middleware` and `express` were needed for our custom NextJS dev server, but that code was removed in #348 , so those dependencies are no longer explicitly required. We should just remove them to avoid the maintenance overhead. Another clean-up / follow-up from #348
Coder v2
This repository contains source code for Coder V2. Additional documentation:
Directory Structure
.github/
: Settings for Dependabot for updating dependencies and build/deploy pipelines with GitHub Actions.semantic.yaml
: Configuration for semantic pull requests\
examples
: Example terraform project templates.site
: Front-end UI code.
Development
Pre-requisites
git
go
version 1.17, with theGOPATH
environment variable setnode
yarn
Cloning
git clone https://github.com/coder/coder
cd coder
Building
make build
make install
The coder
CLI binary will now be available at $GOPATH/bin/coder
Development
./develop.sh
The develop.sh
script runs the server locally on port 3000
, and runs a hot-reload server for front-end code on 8080
.
Front-End Plan
For the front-end team, we're planning on 2 phases to the 'v2' work:
Phase 1
Phase 1 is the 'new-wine-in-an-old-bottle' approach - we want to preserve the look and feel (UX) of v1, while testing and validating the market fit of our new v2 provisioner model. This means that we'll preserve Material UI and re-use components from v1 (porting them over to the v2 codebase).
Phase 2
Phase 2 is the 'new-wine-in-a-new-bottle' - which we can do once we've successfully packaged the new wine in the old bottle.
In other words, once we've validated that the new strategy fits and is desirable for our customers, we'd like to build a new, v2-native UI (leveraging designers on the team to build a first-class experience around the new provisioner model).