giuem / uptimerobot-page

Another status page based on UptimeRobot

👋 This is giuem!

• ✨ I'm currently working at bytedance as a frontend engineer, but also looking for a great job.
• ❤️ I have a blog: https://www.giuem.com.

---

uptimerobot-page's Issues

Docker Build Fail?

The command '/bin/sh -c yarn install && yarn cache clean' returned a non-zero code: 1

https://hub.docker.com/r/giuem/uptimerobot-page/builds/bhpc2obzr7edfgeuvste5fc/

Can not use with Docker inside CT

Maybe because it creat bridge in the container,and this is not allowed on CT version.
I read the source and I think it is not necessary for creating bridge.Any suggestions?
Here are some of the failure log.

Mar 17 16:51:56 Zxilly dockerd[6608]: time="2019-03-17T16:51:56.720096228+08:00" level=info msg="Loading containers: start."
Mar 17 16:51:56 Zxilly dockerd[6608]: time="2019-03-17T16:51:56.721403460+08:00" level=warning msg="Running modprobe bridge br_netfilter failed with message: , error: exit status 1"
Mar 17 16:51:56 Zxilly dockerd[6608]: time="2019-03-17T16:51:56.722238132+08:00" level=warning msg="Running modprobe nf_nat failed with message: ``, error: exit status 1"
Mar 17 16:51:56 Zxilly dockerd[6608]: time="2019-03-17T16:51:56.723062107+08:00" level=warning msg="Running modprobe xt_conntrack failed with message: ``, error: exit status 1"
Mar 17 16:51:57 Zxilly dockerd[6608]: time="2019-03-17T16:51:57.096619812+08:00" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a prefer
Mar 17 16:51:57 Zxilly dockerd[6608]: time="2019-03-17T16:51:57.298167534+08:00" level=info msg="Loading containers: done."
Mar 17 16:51:57 Zxilly dockerd[6608]: time="2019-03-17T16:51:57.336401302+08:00" level=info msg="Docker daemon" commit=774a1f4 graphdriver(s)=overlay2 version=18.09.3
Mar 17 16:51:57 Zxilly dockerd[6608]: time="2019-03-17T16:51:57.336502960+08:00" level=info msg="Daemon has completed initialization"
Mar 17 16:51:57 Zxilly systemd[1]: Started Docker Application Container Engine.
Mar 17 16:51:57 Zxilly dockerd[6608]: time="2019-03-17T16:51:57.384422871+08:00" level=info msg="API listen on /var/run/docker.sock"
Mar 17 16:52:49 Zxilly dockerd[6608]: time="2019-03-17T16:52:49.398151146+08:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 17 16:52:51 Zxilly dockerd[6608]: time="2019-03-17T16:52:51.142437166+08:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 17 17:36:17 Zxilly dockerd[6608]: time="2019-03-17T17:36:17+08:00" level=warning msg="Running modprobe nf_nat failed with message: ``, error: exit status 1"
Mar 17 17:36:17 Zxilly dockerd[6608]: time="2019-03-17T17:36:17+08:00" level=warning msg="Running modprobe xt_conntrack failed with message: ``, error: exit status 1"
Mar 17 17:36:17 Zxilly dockerd[6608]: time="2019-03-17T17:36:17.975271539+08:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Mar 17 17:36:52 Zxilly dockerd[6608]: time="2019-03-17T17:36:52.002998790+08:00" level=error msg="Error setting up exec command in container c53aedcd8b59: Container c53aedcd8b594841192156c4b1b88754c886beeaa7eb3d8ec7
Mar 17 17:37:54 Zxilly dockerd[6608]: time="2019-03-17T17:37:54+08:00" level=warning msg="Running modprobe nf_nat failed with message: ``, error: exit status 1"
Mar 17 17:37:54 Zxilly dockerd[6608]: time="2019-03-17T17:37:54+08:00" level=warning msg="Running modprobe xt_conntrack failed with message: ``, error: exit status 1"
Mar 17 17:37:55 Zxilly dockerd[6608]: time="2019-03-17T17:37:55.109649525+08:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
lines 42-101/101 (END)
'''

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Parsing error of CRON_TIME in docker-compose.yml

$ docker-compose up
Recreating uptimerobot-page_uptimerobot-page_1_c370e42683f3 ... done
Attaching to uptimerobot-page_uptimerobot-page_1_c370e42683f3
uptimerobot-page_1_c370e42683f3 | /app/node_modules/cron/lib/cron.js:411
uptimerobot-page_1_c370e42683f3 | 					throw new Error('Field (' + field + ') cannot be parsed');
uptimerobot-page_1_c370e42683f3 | 					^
uptimerobot-page_1_c370e42683f3 |
uptimerobot-page_1_c370e42683f3 | Error: Field ("0-59/1) cannot be parsed
uptimerobot-page_1_c370e42683f3 |     at CronTime._parseField (/app/node_modules/cron/lib/cron.js:411:12)
uptimerobot-page_1_c370e42683f3 |     at CronTime._parse (/app/node_modules/cron/lib/cron.js:375:10)
uptimerobot-page_1_c370e42683f3 |     at new CronTime (/app/node_modules/cron/lib/cron.js:46:9)
uptimerobot-page_1_c370e42683f3 |     at new CronJob (/app/node_modules/cron/lib/cron.js:477:19)
uptimerobot-page_1_c370e42683f3 |     at _default (/app/build/bootstrap/cron.js:13:28)
uptimerobot-page_1_c370e42683f3 |     at createAPP (/app/build/bootstrap/app.js:44:21)
uptimerobot-page_1_c370e42683f3 |     at Object.<anonymous> (/app/build/bootstrap/index.js:9:32)
uptimerobot-page_1_c370e42683f3 |     at Module._compile (internal/modules/cjs/loader.js:688:30)
uptimerobot-page_1_c370e42683f3 |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
uptimerobot-page_1_c370e42683f3 |     at Module.load (internal/modules/cjs/loader.js:598:32)
uptimerobot-page_1_c370e42683f3 |     at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
uptimerobot-page_1_c370e42683f3 |     at Function.Module._load (internal/modules/cjs/loader.js:529:3)
uptimerobot-page_1_c370e42683f3 |     at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
uptimerobot-page_1_c370e42683f3 |     at startup (internal/bootstrap/node.js:285:19)
uptimerobot-page_1_c370e42683f3 |     at bootstrapNodeJSCore (internal/bootstrap/node.js:739:3)
uptimerobot-page_uptimerobot-page_1_c370e42683f3 exited with code 1

I deleted the environment variables CRON_TIME in docker-compose.yml and it works properly.

Gulp v4 compatibility issues

Some guys reported that an error occurred during gulp build which said 'Task function must be specified.'. gulpjs/undertaker#54 indicates that gulpfile.js must be updated in order to be compatible with gulp v4.