topaLE
/
uptime-kuma
1
0
Fork 0
Code Issues 185 Pull Requests 26 Projects Releases 28 Wiki Activity
Labels Milestones

Restructure status page core implementation #863

Open
louislam wants to merge 1 commits from restructure-status-page into master
Conversation 0 Commits 1 Files Changed N/A
louislam commented 4 years ago (Migrated from github.com)
Owner

Description

Since I was not aware of status page which could be multiple, this pr is going to restructure the status page core.

  • Status Page table
  • Migrate current status page, settings to the table
  • /status/:name
  • CNAME alias, multiple for each status page
  • search engine indexing base on each status page
  • Entry Page, default status page
  • public/private field (no logic, just a field)
  • password field (no logic, just a field)
  • incident change to many-to-many

Checklist

  • My code follows the style guidelines of this project
  • I ran ESLint and other linters for modified files
  • I have performed a self-review of my own code and test it
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • My code needed automated testing. I have added them (this is optional task)

⚠️ If you want to create a pull request which is related to status page, I strongly recommend that you should wait until this pr get merged.

# Description Since I was not aware of status page which could be multiple, this pr is going to restructure the status page core. - [ ] Status Page table - [ ] Migrate current status page, settings to the table - [ ] /status/:name - [ ] CNAME alias, multiple for each status page - [ ] search engine indexing base on each status page - [ ] Entry Page, default status page - [ ] public/private field (no logic, just a field) - [ ] password field (no logic, just a field) - [ ] incident change to many-to-many ## Checklist - [ ] My code follows the style guidelines of this project - [ ] I ran ESLint and other linters for modified files - [ ] I have performed a self-review of my own code and test it - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] My changes generate no new warnings - [ ] My code needed automated testing. I have added them (this is optional task) ⚠️ If you want to create a pull request which is related to status page, I strongly recommend that you should wait until this pr get merged.
❤️ 6
This branch is equal with the target branch.
Sign in to join this conversation.
Reviewers
Request review
No reviewers
Labels
Apply labels
Clear labels
bug
Something isn't working dependencies
Pull requests that update a dependency file discussion doc
Improvements or additions to documentation duplicate
This issue or pull request already exists feature-request
New feature or request good first issue
Good for newcomers hacktoberfest hacktoberfest-accepted help help wanted
Extra attention is needed High
High Priority impossible invalid
This doesn't seem right investigating k8s Low
Low Priority Medium
Medium Priority News prerelease bug question
Further information is requested resolved Unknown wontfix
This will not be worked on
No Label bug dependencies discussion doc duplicate feature-request good first issue hacktoberfest hacktoberfest-accepted help help wanted High impossible invalid investigating k8s Low Medium News prerelease bug question resolved Unknown wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch 'restructure-status-page'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes