> [email protected] start /app | |
> node index.js | |
Zigbee2MQTT:debug 2021-08-30 11:18:53: Loaded state from file /app/data/state.json | |
Zigbee2MQTT:info 2021-08-30 11:18:53: Logging to console and directory: '/app/data/log/2021-08-30.11-18-52' filename: log.txt | |
Zigbee2MQTT:debug 2021-08-30 11:18:53: Removing old log directory '/app/data/log/2021-08-30.11-14-54' | |
Zigbee2MQTT:info 2021-08-30 11:18:53: Starting Zigbee2MQTT version 1.18.2 (commit #abd8a09) | |
Zigbee2MQTT:info 2021-08-30 11:18:53: Starting zigbee-herdsman (0.13.88) | |
Zigbee2MQTT:debug 2021-08-30 11:18:53: Using zigbee-herdsman with settings: '{"adapter":{"concurrent":null,"delay":null},"backupPath":"/app/data/coordinator_backup.json","databaseBackupPath":"/app/data/database.db.backup","databasePath":"/app/data/database.db","network":{"channelList":[20],"extendedPanID":[221,221,221,221,221,221,221,221],"networkKey":"HIDDEN","panID":6760},"serialPort":{"path":"/dev/ttyACM0"}}' | |
Zigbee2MQTT:error 2021-08-30 11:19:13: Error while starting zigbee-herdsman |
Handbook / Marketing / Podcast
How we ideate, structure, produce & distribute our podcast episodes
- title: How to Startup (
Podcast name surveyLast survey) - RSS Feed URL: [coming soon]
- category: Startup Founder Education
- format: Solo starting out, but will evolve into Interviewing experts & founders and fireside chats
function main(){ | |
/* | |
* The following preferences can be changed to customize this script. | |
* Most of options can be set by using 1 for yes or 0 for no. | |
* You don't have to change anything here. The script will do fine with the defaults. | |
*/ | |
var config = { | |
/* | |
* Which of the following charts should be displayed on the dashboard? | |
* The "per QS" charts are column charts. They show the current state compared to a previous one (see next option). |
function main(){ | |
/* | |
* The following preferences can be changed to customize this script. | |
* Most of options can be set by using 1 for yes or 0 for no. | |
* You don't have to change anything here. The script will do fine with the defaults. | |
*/ | |
var config = { | |
/* | |
* Which of the following charts should be displayed on the dashboard? | |
* The "per QS" charts are column charts. They show the current state compared to a previous one (see next option). |
function main(){ | |
/* | |
* The following preferences can be changed to customize this script. | |
* Most of options can be set by using 1 for yes or 0 for no. | |
* You don't have to change anything here. The script will do fine with the defaults. | |
*/ | |
var config = { | |
/* | |
* Which of the following charts should be displayed on the dashboard? | |
* The "per QS" charts are column charts. They show the current state compared to a previous one (see next option). |
function main(){ | |
/* | |
* The following preferences can be changed to customize this script. | |
* Most of options can be set by using 1 for yes or 0 for no. | |
* You don't have to change anything here. The script will do fine with the defaults. | |
*/ | |
var config = { | |
/* | |
* Which of the following charts should be displayed on the dashboard? | |
* The "per QS" charts are column charts. They show the current state compared to a previous one (see next option). |
<script src="https://www.anyguide.com/assets/integration.js"></script> | |
<div id="iframe_wrapper"></div> | |
<script language="javascript" type="text/javascript"> | |
(function(){ | |
window.anyroad = new AnyRoad({ | |
container: "#iframe_wrapper", | |
tours: { curated_list: 'join_a_tour' }, | |
iframe_style: { width: '100%', background: 'transparent' }, | |
referrer: { name: 'elenaa' } | |
}); |
Everything that's happening engineering-wise should be well documented, so we don't lose track. Whether it's a feature or a bug, or just some tech related work, it needs to be written down. The log for all activity right now is Pivotal Tracker, and we use per application projects there.
Pivotal Tracker allows you to add three types of entries; features, bugs and chores. Anything that provides measurable value to the app is considered a feature. Bugs are defects in the software. Chores are tasks that while adding value to the product, this value cannot be measured directly. Cleaning up tech debt falls on this category.
The projects on Pivotal Tracker are visible from both Product and Engineering. Sometimes a task in Tracker can be further broken down to smaller tasks. Sometimes a task in Tracker makes sense from a Product point of view, but developers speak a different language. That's why we replicate issues on Github. Every task in Tracker should be linked to one