|
|
@@ -92,7 +92,7 @@ DB_NAME=porter
|
|
|
SQL_LITE=false
|
|
|
```
|
|
|
|
|
|
-Once you've done this, go to the root repository, and run `docker-compose -f docker-compose-dev.yaml up`. You should see postgres, webpack, and porter containers spin up. When the webpack and porter containers have finished compiling and have spun up successfully (this will take 5-10 minutes after the containers start), you can navigate to `localhost:8080` and you should be greeted with the "Log In" screen.
|
|
|
+Once you've done this, go to the root repository, and run `docker-compose -f docker-compose.dev.yaml up`. You should see postgres, webpack, and porter containers spin up. When the webpack and porter containers have finished compiling and have spun up successfully (this will take 5-10 minutes after the containers start), you can navigate to `localhost:8080` and you should be greeted with the "Log In" screen.
|
|
|
|
|
|
At this point, you can make a change to any `.go` file to trigger a backend rebuild, and any file in `/dashboard/src` to trigger a hot reload. Happy developing!
|
|
|
|
|
|
@@ -106,4 +106,4 @@ We do not currently have a process for frontend testing -- if building out a fro
|
|
|
|
|
|
To ensure that your PR is merged before an upcoming release, it is easiest if you prefix the branch with the release version you'd like to be finished by (the upcoming two releases will always exist at https://github.com/porter-dev/porter/projects). If your pull request is related to an issue, please mention that issue in the branch name. So for example, if I'd like to close issue `200` and I'd like to merge the PR by release `0.3.0`, I would run `git checkout -b 0.3.0-200-pod-deletion`.
|
|
|
|
|
|
-For now, request [**@abelanger5**](https://github.com/abelanger5) to review your PR.
|
|
|
+For now, request [**@abelanger5**](https://github.com/abelanger5) to review your PR.
|
jusrhee