profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/PeterDaveHello/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Peter Dave Hello PeterDaveHello @nodejs @maintainers @transmission-remote-gui Taiwan, R.O.C https://www.peterdavehello.org/ Free & Open Source enthusiast. Interested in SysAdmin & Git ⚒⚙. A 👨🏼 who ♥️ Debian GNU/Linux 🐧 lives in 🇹🇼

nvm-sh/nvm 52375

Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

g0v/moedict-webkit 493

萌典網站

PeterDaveHello/add-apt-ppa 5

🏎 Speedup ppa apt repository adding process 🕶

cmingou/cord-tools 3

Tools and scripts about build CORD

PeterDaveHello/AccountAutoCreator 2

FreeBSD account bulk creator

chitwanix/Kelvin 1

A scientific conversion Utility

chitwanix/loadshedding 1

Nepal Loadshedding Utility

extend1994/cdnjs 1

Free and Open Source Public Web CDN for web developer!

chitwanix/chitwanix.com 0

Official Site of Chitwanix.com

gitstats-collection/jsdelivr-gitstats 0

jsdelivr main repository gitstats analytics

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 313b35660a8addb0dadbffffb29d0b1f0a5479f4

:bento: Update graphs [skip ci]

view details

push time in 6 hours

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 12d98ca4186c0526b1a693e500dd3023692d957c

:pencil: Update summary in README [skip ci] [upptime]

view details

Upptime Bot

commit sha 431ecc6c815082942521911e8d47c4298ce82c88

:card_file_box: Update status summary [skip ci] [upptime]

view details

push time in 6 hours

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 8eb72a55e2dde7c2c37f58b00797e54d334baccb

🟩 ipinfo.tw is up (200 in 1041 ms) [skip ci] [upptime]

view details

push time in 7 hours

delete branch PeterDaveHelloKitchen/htrace.sh

delete branch : UpdateDockerfile

delete time in 9 hours

issue commenttmick0/gitlab-calendar

Add support for milestones

I don't think there's another trigger yet, unless somebody implemented it.

minorOffense

comment created time in 21 hours

PR opened Turgon37/docker-smtp-relay

Update README.md

Set the proper container name to smtp-relay in the usage, so the later usage examples can work properly, as they need to specify the correct container name.

+1 -1

0 comment

1 changed file

pr created time in a day

push eventPeterDaveHello/docker-smtp-relay

Peter Dave Hello

commit sha f59a561171e966676dde1be0272cece065bc4723

Update README.md Set the proper container name to `smtp-relay` in the usage, so the later usage examples can work properly, as they need to specify the correct container name.

view details

push time in a day

fork PeterDaveHello/docker-smtp-relay

Docker image running a SMTP relay with postfix

fork in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 91cfc347e607733465f6bcbac472cf0175038acc

:bento: Update graphs [skip ci]

view details

push time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 59c614c05bd4558ec9737787b1e5d367a23ecb7c

:pencil: Update summary in README [skip ci] [upptime]

view details

Upptime Bot

commit sha dfaf93af772d91197c7f984f4374f465ef13bc33

:card_file_box: Update status summary [skip ci] [upptime]

view details

push time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 87049c3bf8b0fe2dcdb4f0c5ae789d34beb08a98

🟩 ipinfo.tw is up (200 in 1114 ms) [skip ci] [upptime]

view details

push time in a day

Pull request review commentPeterDaveHello/docker-markdownlint

Update Node.js to v17

-FROM node:16-alpine3.14+FROM node:17-alpine3.14

I prefer to use LTS version.

renovate[bot]

comment created time in a day

PullRequestReviewEvent
PullRequestReviewEvent

PR closed PeterDaveHello/docker-markdownlint

Update Node.js to v17

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
node final major 16-alpine3.14 -> 17-alpine3.14

Release Notes

<details> <summary>nodejs/node</summary>

v17

<a href="doc/changelogs/CHANGELOG_V5.md#​5.1.0">Moved to doc/changelogs/CHANGELOG_V5.md#​5.1.0</a>.

</details>


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • [ ] <!-- rebase-check -->If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

+1 -1

0 comment

1 changed file

renovate[bot]

pr closed time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 3e19eeb1857958415ab651f1e885e118c0138919

:pencil: Update summary in README [skip ci] [upptime]

view details

Upptime Bot

commit sha cd35cd5843847103a89acd28c252b0b5ff72cff2

:card_file_box: Update status summary [skip ci] [upptime]

view details

push time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 6c1be6df5c0f5996b864912940aa84eb29f26d4d

🟩 ipinfo.tw is up (200 in 975 ms) [skip ci] [upptime]

view details

push time in a day

issue closedPeterDaveHello/ipinfo.tw-uptime

🛑 ipinfo.tw is down

In 289c439, ipinfo.tw (https://ipinfo.tw) was down:

  • HTTP code: 0
  • Response time: 0 ms

closed time in a day

PeterDaveHello

issue commentPeterDaveHello/ipinfo.tw-uptime

🛑 ipinfo.tw is down

Resolved: ipinfo.tw is back up in 6c1be6d.

PeterDaveHello

comment created time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha a5ea6e3221be750d2dd3729ffb77bffef854853a

:pencil: Update summary in README [skip ci] [upptime]

view details

Upptime Bot

commit sha 8f111e2091ded1926f2278fa15a023ecaca1da98

:card_file_box: Update status summary [skip ci] [upptime]

view details

push time in a day

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha 289c43938215244c4130f7d9c9201a59fb3a3dfc

🟥 ipinfo.tw is down (0 in 0 ms) [skip ci] [upptime]

view details

push time in a day

issue openedPeterDaveHello/ipinfo.tw-uptime

🛑 ipinfo.tw is down

In 289c439, ipinfo.tw (https://ipinfo.tw) was down:

  • HTTP code: 0
  • Response time: 0 ms

created time in a day

PR opened nodejs/docker-node

Update node.js v16 from 16.11.1 to 16.12.0
  • https://nodejs.org/en/blog/release/v16.12.0/
  • https://github.com/nodejs/node/releases/tag/v16.12.0
  • https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md#16.12.0

<!-- Provide a general summary of your changes in the Title above. -->

Description

<!-- Describe your changes in detail. -->

Motivation and Context

<!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. -->

Testing Details

<!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. -->

Example Output(if appropriate)

Types of changes

<!-- What types of changes does your code introduce? Put an x in all the boxes that apply. -->

  • [ ] Documentation
  • [ ] Version change (Update, remove or add more Node.js versions)
  • [ ] Variant change (Update, remove or add more variants, or versions of variants)
  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)
  • [ ] Others (non of above)

Checklist

<!-- Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

  • [ ] My code follows the code style of this project.
  • [ ] My change requires a change to the documentation.
  • [ ] I have updated the documentation accordingly.
  • [ ] I have read the CONTRIBUTING.md document.
  • [ ] All new and existing tests passed.
+14 -14

0 comment

10 changed files

pr created time in a day

create barnchPeterDaveHello/docker-node

branch : update-node.js

created branch time in a day

issue commentPeterDaveHello/docker-azcopy

Require Linux/ARM64 Docker Image for azcopy

Update: I've published a test build with the latest azcopy v10.12.2, please help test it on your platform.

https://hub.docker.com/layers/peterdavehello/azcopy/test/images/sha256-e0ec84482d7d9d6a2bf6d0b2487cd3e00965258d3564dc604120373e9526b77e?context=explore

odidev

comment created time in 2 days

startedTurgon37/docker-smtp-relay

started time in 2 days

pull request commentnodejs/docker-node

fix: docker-entrypoint.sh file handling, closes #1456

Should be fine to re-add? /cc @nodejs/docker

I'm good to add it back 👍

MasonM

comment created time in 2 days

Pull request review commentnodejs/docker-node

fix: docker-entrypoint.sh file handling, closes #1456

 jobs:           echo "Expected: \"${{ matrix.version }}\", Got: \"${image_node_version}\""           [ "${image_node_version}" == "${{ matrix.version }}" ] +      - name: Regression test for issue 1456

Nice, thanks @MasonM

MasonM

comment created time in 2 days

PullRequestReviewEvent

push eventPeterDaveHello/ipinfo.tw-uptime

Upptime Bot

commit sha cb584599f6d5ebc7591f78dc25046c6cbd015fac

:bento: Update graphs [skip ci]

view details

push time in 2 days