Remove .devcontainer (#5074)
This commit is contained in:
parent
c567e8eb8e
commit
11f108b501
|
@ -1,28 +0,0 @@
|
||||||
# Codespaces
|
|
||||||
|
|
||||||
You can modifiy Uptime Kuma in your browser without setting up a local development.
|
|
||||||
|
|
||||||
![image](https://github.com/louislam/uptime-kuma/assets/1336778/31d9f06d-dd0b-4405-8e0d-a96586ee4595)
|
|
||||||
|
|
||||||
1. Click `Code` -> `Create codespace on master`
|
|
||||||
2. Wait a few minutes until you see there are two exposed ports
|
|
||||||
3. Go to the `3000` url, see if it is working
|
|
||||||
|
|
||||||
![image](https://github.com/louislam/uptime-kuma/assets/1336778/909b2eb4-4c5e-44e4-ac26-6d20ed856e7f)
|
|
||||||
|
|
||||||
## Frontend
|
|
||||||
|
|
||||||
Since the frontend is using [Vite.js](https://vitejs.dev/), all changes in this area will be hot-reloaded.
|
|
||||||
You don't need to restart the frontend, unless you try to add a new frontend dependency.
|
|
||||||
|
|
||||||
## Backend
|
|
||||||
|
|
||||||
The backend does not automatically hot-reload.
|
|
||||||
You will need to restart the backend after changing something using these steps:
|
|
||||||
|
|
||||||
1. Click `Terminal`
|
|
||||||
2. Click `Codespaces: server-dev` in the right panel
|
|
||||||
3. Press `Ctrl + C` to stop the server
|
|
||||||
4. Press `Up` to run `npm run start-server-dev`
|
|
||||||
|
|
||||||
![image](https://github.com/louislam/uptime-kuma/assets/1336778/e0c0a350-fe46-4588-9f37-e053c85834d1)
|
|
|
@ -1,23 +0,0 @@
|
||||||
{
|
|
||||||
"image": "mcr.microsoft.com/devcontainers/javascript-node:dev-18-bookworm",
|
|
||||||
"features": {
|
|
||||||
"ghcr.io/devcontainers/features/github-cli:1": {}
|
|
||||||
},
|
|
||||||
"updateContentCommand": "npm ci",
|
|
||||||
"postCreateCommand": "",
|
|
||||||
"postAttachCommand": {
|
|
||||||
"frontend-dev": "npm run start-frontend-devcontainer",
|
|
||||||
"server-dev": "npm run start-server-dev",
|
|
||||||
"open-port": "gh codespace ports visibility 3001:public -c $CODESPACE_NAME"
|
|
||||||
},
|
|
||||||
"customizations": {
|
|
||||||
"vscode": {
|
|
||||||
"extensions": [
|
|
||||||
"streetsidesoftware.code-spell-checker",
|
|
||||||
"dbaeumer.vscode-eslint",
|
|
||||||
"GitHub.copilot-chat"
|
|
||||||
]
|
|
||||||
}
|
|
||||||
},
|
|
||||||
"forwardPorts": [3000, 3001]
|
|
||||||
}
|
|
|
@ -17,7 +17,6 @@ README.md
|
||||||
.vscode
|
.vscode
|
||||||
.eslint*
|
.eslint*
|
||||||
.stylelint*
|
.stylelint*
|
||||||
/.devcontainer
|
|
||||||
/.github
|
/.github
|
||||||
yarn.lock
|
yarn.lock
|
||||||
app.json
|
app.json
|
||||||
|
|
|
@ -236,12 +236,6 @@ The goal is to make the Uptime Kuma installation as easy as installing a mobile
|
||||||
- IDE that supports [`ESLint`](https://eslint.org/) and EditorConfig (I am using [`IntelliJ IDEA`](https://www.jetbrains.com/idea/))
|
- IDE that supports [`ESLint`](https://eslint.org/) and EditorConfig (I am using [`IntelliJ IDEA`](https://www.jetbrains.com/idea/))
|
||||||
- A SQLite GUI tool (f.ex. [`SQLite Expert Personal`](https://www.sqliteexpert.com/download.html) or [`DBeaver Community`](https://dbeaver.io/download/))
|
- A SQLite GUI tool (f.ex. [`SQLite Expert Personal`](https://www.sqliteexpert.com/download.html) or [`DBeaver Community`](https://dbeaver.io/download/))
|
||||||
|
|
||||||
### GitHub Codespaces
|
|
||||||
|
|
||||||
If you don't want to setup an local environment, you can now develop on GitHub Codespaces, read more:
|
|
||||||
|
|
||||||
https://github.com/louislam/uptime-kuma/tree/master/.devcontainer
|
|
||||||
|
|
||||||
## Git Branches
|
## Git Branches
|
||||||
|
|
||||||
- `master`: 2.X.X development. If you want to add a new feature, your pull request should base on this.
|
- `master`: 2.X.X development. If you want to add a new feature, your pull request should base on this.
|
||||||
|
|
Loading…
Reference in New Issue