Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Publish Uptime Kuma to npm #3521

Draft
wants to merge 4 commits into
base: master
Choose a base branch
from
Draft

Publish Uptime Kuma to npm #3521

wants to merge 4 commits into from

Conversation

louislam
Copy link
Owner

@louislam louislam commented Aug 3, 2023 •
edited by CommanderStorm
Loading

Provide a new way to install Uptime Kuma via npm.

# Install
npm install uptime-kuma -g
# or
pnpm install uptime-kuma -g 

# Run the server
uptime-kuma
# or with arguments
uptime-kuma --port=8080

TODO:

@louislam louislam added this to the 2.0.0 milestone Aug 3, 2023
@louislam louislam changed the base branch from master to 2.0.X August 11, 2023 12:27
@louislam louislam modified the milestones: 2.0.0, 2.1.0 Dec 5, 2023
@CommanderStorm CommanderStorm deleted the branch master December 14, 2023 19:57
@CommanderStorm CommanderStorm deleted the npm-publish branch December 14, 2023 20:54
@CommanderStorm CommanderStorm restored the npm-publish branch December 14, 2023 21:37
@louislam louislam deleted the branch master January 7, 2024 16:00
@louislam louislam closed this Jan 7, 2024
@CommanderStorm CommanderStorm reopened this Jan 7, 2024
@CommanderStorm CommanderStorm changed the base branch from 2.0.X to master January 7, 2024 19:27
@CommanderStorm
Copy link
Collaborator

@louislam I changed the merge-target, but did not rebase ^^

@CommanderStorm CommanderStorm added the area:deployment related to how uptime kuma can be deployed label Apr 3, 2024
@CommanderStorm CommanderStorm added the pr:please address review comments this PR needs a bit more work to be mergable label May 19, 2024
@github-actions github-actions bot added pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again and removed pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again labels May 19, 2024
@github-actions github-actions bot added pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again and removed pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again labels May 21, 2024
@CommanderStorm
Copy link
Collaborator

#4781 has an alternative approach to publishing npm packages
=> might be more convenient

@CommanderStorm CommanderStorm mentioned this pull request May 22, 2024
Closed
7 tasks
@github-actions github-actions bot added pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again and removed pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again labels May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
area:deployment related to how uptime kuma can be deployed needs:resolve-merge-conflict pr:please address review comments this PR needs a bit more work to be mergable pr:please resolve merge conflict A merge-conflict needs to be addressed before reviewing makes sense again
Projects
None yet
Milestone
2.1.0
Development

Successfully merging this pull request may close these issues.
2 participants
@louislam @CommanderStorm