#nodeapp

[urmahkind]

We CANNOT FORGET Second Cup Canada's Hand-made Pumpkin🎃 Spice Bakery!!! MY FAV was PUMPKIN SPICE BLONDIE SQUARE💛💛💛, but pumpkin spice Muffin and Vegan Pumpkin Chocolate Chip Loaf were DELICIOUS as well!  ___________________________ @secondcupcanada, @node.app, @jojoinstameets ___________________________ #Secondcupcanada #SecondCupCanadaMeets #Nodeapp #Jojoinstameets ___________________________ #Pumpkin #pumpkinspice #Vegan #Plantbase #BlondieSquare #Muffin #Treats #Bakery #Chocolatechip #Handmade (at Second Cup Canada) https://www.instagram.com/p/Boev_ulha5T/?utm_source=ig_tumblr_share&igshid=d1evo9yljyuf

[mialee0123]

All of us know that it’s easy to differentiate the power of a server and an android device, as the computing power of a server is more prominent than the computing capability of a mobile device.

If an application has a massive computational load then it grows more effective for the android device to transfer parameters to a backend server to do the hefty work and then deliver the result. For a general pattern install androidjs, that way interacting between a front-end client and a back end server will help to practice JSON.

[caribdish]

Do you know where this is in #ontario? @caribdish deliver to your door steps!! . . . . #mealprep #torontofoodblogger #tastethesix #cravethe6ix #dishedto #tastetoronto #streetsoftoronto #yyzeats #torontofoodie #torontoeats #foodinstagram #torontofood #blogto #dailyhiveto #yyzfood #foodblog #foodporn #foodgram #nodeapp #canadatakeout #toptorontorestaurants #cambridge #craveto #homecooking #GaltCityCentre #authenic #blogTO (at Galt City Centre) https://www.instagram.com/p/CQzgtFoM1Lt/?utm_medium=tumblr

[torontoseoulcialite]

I'd ask who wore it best, but I'm afraid you'd all choose the bottle! • I'm having a little humpday #martini today using locally-produced premium vodka, distilled six times. @snowallurepremiumvodka can be purchased at 33 different LCBO stores across #Toronto and online for $49.95. 🍸//#snowallurepremiumvodka #snowallurevodka #nodeapp @node.app #snowangels #premiumvodka #vodka #drinkstagram *gifted (at Liberty Village) https://www.instagram.com/p/CCZbCDdMfIL/?igshid=iv3e8lghvfj3

[coding-samuraized]

node script executable

mkdir nodeapp cd nodeapp npm init, go with defaults mkdir bin touch script.js $ node bin/script.js in package.json { “name”: “comtrolweb”, “version”: “1.0.0”, “description”: “”, “bin”: { “marcus”: “./bin/script.js” }, “main”: “index.js”, cd bin ➜ bin npm link To unlink: ➜ bin npm unlink at last, add #! usr/bin/env node at the top of script.js if this adding #! usr/bin/env node didn’t work: adding !#env node solved the problem

[fravoposts-blog]

1Z0-593 Oracle Real Application Clusters 11g Essentials

1Z0-593 exam tests the knowledge of the candidates about the Oracle database. The Oracle certified individuals can have a brighter career with the Oracle certification, opening newer and better career prospects for them in handling the Oracle products and working with the Oracle Company.

Oracle is one of today's best IT companies, and the Oracle Real Application Clusters 11g Essentials exam will ensure that the candidate has not only master the valuable knowledge, but the certification would be a testimony of the skills of the candidate. The questions on the 1Z0-593 exam are in multiple choice formats, ranging from the complex problem solving questions to the ones that are comparatively simpler. The time duration of the 1Z0-593 exam is 120 minutes and the number of questions is 79. The exam will be taken at a Pearson VUE exam center and has a passing score of 72%. The Oracle Real Application Clusters 11g Essentials exam is a difficult exam, hence a thorough knowledge and at hands experience would render helpful in attaining a good score. The list of exam topics to be covered in the exam is the following; however, other related exam topics can also be given the questions from:

Oracle Grid Infrastructure overview and the RAC

·        Description of ASM and Oracle architecture

·        RAC services

·        Tools used by RAC and Grid Infrastructure

·        Planning of the cluster installation

·        Usage of CVU, knowing how to review and backup the environment of Oracle

·        Preparation of cluster servers

·        Understanding hardware and software requirements and configuration of tasks

·        Administrator environment preparation

·        Configuration of different environments, operating systems, and groups

Storage preparation

·        Explaining and understanding the requirements

·        Configuration and description of different tasks

·        Installation directories preparation

Network preparation

·        Understanding network requirements

·        Types of IP addresses

·        Implementation of the basic network practices

·        Oracle Clusterware 11g installation

·        Installation, creation and configuration of the clusterware database

·        Installation of Oracle software with RAC

·        Understanding the nodeapps, listeners, databases, and insurances, including the handling of instances

·        Usage of SRVCTL (Server Control Utility)

·        Usage of Oracle CRSCTL (Clusterware Control Utility)

·        Enabling or disabling the daemons, debugging and diagnostics of cluster issues

·        Usage of Oracle OIFCFG (Oracle Interface Configuration Tool)

·        Usage of Oracle OCRCONFIG (Oracle Cluster Registry Configuration Utility)

·        Usage of other utilities such as OCRCHECK and OCRDUMP

·        Usage of Oracle ASMCA (ASM Configuration Assistant)

·        Usage of ASMCMD (ASM Command Tool)

·        Usage of Oracle IPD/OS (Cluster Health Monitor)

Fravo is well known in the field of IT and Tech Certification Exams for its preparation material regarding 1Z0-593 exam Visit https://www.fravo.com/1Z0-593-exams.html

[youngprogrammersclub]

How to Apply Critical Patch Update (CPU) on RAC

Patch Details: Patch “CPUJULY2012” CPU patch is released 4 times in a year JAN/APR/JUL/OCTVersion & Platform: 10.2.0.4 Database on LINUX Overview:A Critical patch update (CPU) is a collection of patches for multiple security vulnerabilities. CPU patch are usually cumulative, which means fixes from previous Oracle security alerts and critical patch updates are included in current patch. However each advisory describes only the security fixes added since the critical patch update advisory. Thus it is not required to have previous security patches applied before applying the latest patches. However, you must be on the stated patch set level for a given product home before applying the latest patches for that release: Information about latest CPU patchNote: Do not forget to read the README file from the patch before start the actual work.–        If this is a RAC environment, select one of the patch installation methods provided by OPatch (rolling, all node, or minimum downtime), and shutdown instances and listeners as appropriate for the installation method selected. This CPU patch is rolling RAC installable.–        If this is not a RAC environment, shut down all instances and listeners associated with the Oracle home that you are updating.Repeat the Steps for each node of RAC– Shutdown the Oracle instances and services or listener on node 1 – Apply the patch to the on node 1 – Start the Oracle instance of node 1 – Now Shutdown the Oracle instance on node 2 – Apply the patch to on node 2 – Start the Oracle instance of node 2– Repeat this process as per the number of node. 1. Download the CPU required patchset from Metalink2. Change the owner of the patch file to oracle user.# chown –R oracle3. Set the PATH variable to locate the opatch utility.$ export PATH=$PATH: $ORACLE_HOME/OPatch4. unzip the patch and go the unzipped directory$unzip “patchfile.zip”5. Find and invoke the Opatch version$ opatch versionOPatch Version: 10.2.0.4.2$ opatch lsinventoryIf you want check the CPU patch is whether rolling support or not, go to the patch directoryCd /oracle/??  --patch directory$ opatch query -all6. Backup the oraInventory and Opatch directory$cp -R oraInventory old_oraInventory$cp -R opatch old_opatch7. If you are Applying on RAC: Stop Instance/asm/nodeapps of node1$ srvctl stop instance -d racdb –i racdb1$ srvctl stop asm -n rac1$ srvctl stop nodeapps -n rac18. Go to the Patch Directory and invoke opatch apply.$ cd ??  --patch directory$opatch apply or $opatch napply -skip_subset -skip_duplicate9. Verify Patches are applied$opatch lsinventory -detail -oh $ORACLE_HOME10. Now start the Node1 and repeat the same steps 7 to 9 for Node211. Verify Patches are applied           $opatch lsinventory -detail -oh $ORACLE_HOME12. Start the Instance/Asm/Nodeapps of node2$srvctl start instance –d racdb –i racdb2$srvctl start asm –n rac2$srvctl start nodeapps –n rac2$crs_stat –t Post CPU Patch Steps:For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus on each node. Connect as SYSDBA and run the catbundle.sqlscript:On node1/node2:cd $ORACLE_HOME/rdbms/adminsqlplus /nologSQL> CONNECT / AS SYSDBASQL> STARTUPSQL> @catbundle.sql cpu applySQL> @utlrp.sqlThe catbundle.sql execution is reflected in the dba_registry_historyview by a row associated with bundle series CPU. Check the following log files for any errors:catbundle_CPU__APPLY_.log, catbundle_CPU__GENERATE_.log on the path $ORACLE_HOME/cfgtoollogs/catbundleRecompiling Views in the DatabaseIf you already applied this during previous CPU installation then you can skip this section. To check whether view recompilation has already been performed:SELECT * FROM registry$history where ID = '6452863';If the view recompilation has been performed, this statement returns one or more rows. If the view recompilation has not been performed, this statement returns no rows.If no rows returns then go the following steps for RAC environment:1. Run the pre-check script, which reports the maximum number of views and objects that may be recompiled:cd $ORACLE_HOME/cpu/view_recompilesqlplus /nologSQL> CONNECT / AS SYSDBASQL> @recompile_precheck_jan2010cpu.sqlNote: If the database is in RAC environment then perform both the steps otherwise (single instance db), perform only step1 skip the step 2. cd $ORACLE_HOME/cpu/view_recompilesqlplus /nologSQL> CONNECT / AS SYSDBASQL> SHUTDOWN IMMEDIATE;SQL> STARTUP UPGRADE;SQL> @view_recompile_jan2010cpu.sqlSQL> SHUTDOWN;SQL> STARTUP;2. Stop all instances except the one where the view recompilation is being executed.cd $ORACLE_HOME/cpu/view_recompilesqlplus /nologSQL> CONNECT / AS SYSDBASQL> STARTUP NOMOUNT;SQL> ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=spfile;SQL> SHUTDOWN;SQL> STARTUP UPGRADE;SQL> @?/ cpu/view_recompile /view_recompile_jan2008cpu.sqlSQL> SHUTDOWN;SQL> STARTUP NOMOUNT;Set the CLUSTER_DATABASE initialization parameter to TRUE:SQL> ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=spfile;Restart the database:SQL> QUITcd $CRS_HOME/binsrvctl start database -d racdbIf any invalid objects were reported, run the utlrp.sqlscript:cd $ORACLE_HOME/rdbms/adminsqlplus /nologSQL> CONNECT / AS SYSDBASQL> @utlrp.sqlThen, manually recompile any invalid objects:SQL> alter package schemaname.packagename compile;Verify Patches are applied.$opatch lsinventory -detail -oh $CRS_HOME #if you have CRS_HOME$opatch lsinventory -detail -oh $ORACLE_HOME#if you have both ORACLE_HOME

[for-the-user]

a minikube dev envionment and workflow

window.location.replace("https://blog.sebastianfromearth.com/post/20180523065409");

Set up your local kubernetes environment

Add this to your /etc/hosts file somewhere: IMPORTANT - note that the ip address may be 192.168.99.101 or 192.168.99.102, etc, depending on how many times you have recreated your environment locally. Use the appropriate value.

192.168.99.100 dev.myapp.com

Minikube requirements (one of):

virtualbox (at least version 5) vmwarefusion kvm (driver installation) xhyve (driver installation)

Install kubectl, helm & minikube: IMPORTANT - please make sure you are using minikube version 0.24.1

### MAC # kubectl curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.9.0/bin/darwin/amd64/kubectl; chmod +x ./kubectl; sudo mv ./kubectl /usr/local/bin/kubectl # kubernetes-helm sudo curl -LO https://storage.googleapis.com/kubernetes-helm/helm-v2.7.2-darwin-amd64.tar.gz; sudo tar -zxvf helm-v2.7.2-darwin-amd64.tar.gz; sudo mv darwin-amd64/helm /usr/local/bin/helm # minikube curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.24.1/minikube-darwin-amd64; chmod +x minikube; mv minikube /usr/local/bin/minikube ### Linux # kubectl sudo curl -LO https://storage.googleapis.com/kubernetes-release/release/v1.9.0/bin/linux/amd64/kubectl; sudo chmod +x ./kubectl; sudo mv ./kubectl /usr/local/bin/kubectl # kubernetes-helm sudo curl -LO https://storage.googleapis.com/kubernetes-helm/helm-v2.7.2-linux-amd64.tar.gz; sudo tar -zxvf helm-v2.7.2-linux-amd64.tar.gz; sudo mv linux-amd64/helm /usr/local/bin/helm # minikube sudo curl -Lo minikube https://storage.googleapis.com/minikube/releases/v0.24.1/minikube-linux-amd64; sudo chmod +x minikube; sudo mv minikube /usr/local/bin/minikube

Start minikube, sync the project directory's files into the minikube VM and load the dashboard: IMPORTANT - please make sure you use kubernetes version v1.8.0

minikube start --memory 4096 --kubernetes-version v1.8.0 rsync -av --numeric-ids --stats -e "ssh -i $(minikube ssh-key)" --rsync-path="sudo rsync" /my/project/dir/ docker@$(minikube ip):/myprojectdir/ minikube dashboard

Add an nginx ingress controller into your local kubernetes cluster, as well as heapster:

minikube addons enable ingress minikube addons enable heapster

Install tiller into your local kubernetes cluster:

helm init

You just saw this rsync command above:

rsync -av --numeric-ids --stats -e "ssh -i $(minikube ssh-key)" --rsync-path="sudo rsync" /my/project/dir/ docker@$(minikube ip):/myprojectdir/

The workflow here is to sync the files, rather than mount, with the minikube vm. This is because on a mac, mounting is way too slow with docker, especially for node projects. Once the files have been synced into the minikube vm, we can mount them into local docker containers which will be used in the minikube k8s cluster.

Let's take a node project as an example.

Development Workflow

We will do work on our host, using a ide/text editor on the host and also node/npm on the host. We will use the minikube docker daemon, and we will rsync changed files into the minikube vm.

Change to the root of your app project directory on your host:

cd /my/node/project/dir/

Build this example node application using the npm installed on your host:

npm i; npm run build

Re-sync any changed files into the minikube vm: IMPORTANT - remember to do this each time, maybe can be added in the package.json (I didn't make any hot change functionality yet).

rsync -av --numeric-ids --stats -e "ssh -i $(minikube ssh-key)" --rsync-path="sudo rsync" /my/project/dir/ docker@$(minikube ip):/myprojectdir/

Use minikube's docker daemon:

eval $(minikube docker-env)

Build your dev docker image inside the minikube VM:

docker build -t my-node-app -f Dockerfile.dev .

The dockerfile might look something like:

FROM node:8.9 as builder RUN node -v && npm -v FROM nginx:1.12 COPY ./nginx.conf /etc/nginx/nginx.conf

...and the nginx config might look something like:

worker_processes auto; events { worker_connections 1024; } error_log /dev/stdout debug; http { include mime.types; sendfile off; server_tokens off; server { listen 8080; access_log /dev/stdout; error_log /dev/stdout; client_max_body_size 0; location / { root /var/www; try_files $uri $uri/ =404; index index.html; } } }

Deploy the node app to your minikube kubernetes environment:

helm upgrade --install --values helm/myapp/values/dev.yaml --namespace dev dev helm/myapp

The missing part you might be wondering about is how the docker container is serving the built html/css/js files. It's in the helm chart, using a persistent volume mount and persistent volume claim:

--- apiVersion: extensions/v1beta1 kind: Deployment metadata: name: my-node-app namespace: {{ .Release.Namespace }} labels: env: {{ .Release.Namespace }} role: my-node-app app: my-node-app spec: replicas: {{ .Values.nodeApp.replicaCount }} strategy: type: RollingUpdate rollingUpdate: maxSurge: 1 maxUnavailable: 1 template: metadata: labels: env: {{ .Release.Namespace }} role: my-node-app app: my-node-app spec: containers: - name: my-node-app image: {{ .Values.nodeApp.imageName }}:{{ .Values.nodeApp.dockerImageVersion }} {{ if eq .Values.env "dev" }} volumeMounts: - mountPath: /var/www name: app-volume {{ end }} imagePullPolicy: {{ .Values.imagePullPolicy }} resources: requests: memory: {{ .Values.nodeApp.memory.requests }} cpu: {{ .Values.nodeApp.cpu.requests }} limits: memory: {{ .Values.nodeApp.memory.limit }} cpu: {{ .Values.nodeApp.cpu.limit }} ports: - containerPort: {{ .Values.nodeApp.port }} name: http {{ if eq .Values.env "dev" }} volumes: - name: app-volume persistentVolumeClaim: claimName: app-claim {{ end }} --- apiVersion: v1 kind: PersistentVolume metadata: name: app-volume spec: storageClassName: app-manual accessModes: - ReadWriteOnce capacity: storage: 250Mi hostPath: path: /myprojectdir/web

Values:

env: dev imagePullPolicy: IfNotPresent nodeApp: replicaCount: 1 cpu: requests: 100m limit: 200m memory: requests: 100Mi limit: 200Mi port: 8080 imageName: my-node-app dockerImageVersion: latest

Now every time we edit our application and make a change, we can rebuild it, resync it and redeploy it with helm (which mounts the files into the running pod). I admit this isn't exactly seemless, but it is possible to work like this in a k8s style environment.

A large upside (from an ops perspective) is that you can then use the same helm chart, with different values files to provision separate environments. You could even package the whole thing as a helm chart to be stored in the chart museum for one line installation of an entire environment.

Each environment will be the same, they will all use the same tooling ecosystem, and your infrastructure changes can be tracked and committed to a git repository. If you want to make sure your dev environment is as close as possible to your qa, staging, prod or any other environments you are running with, this might be a viable skeleton of an option.

Resetting Everything

To remove the app from your minikube kubernetes cluster:

helm del --purge dev

To destroy everything and reset completely:

minikube stop minikube delete rm -rf ~/.minikube rm -f ~/.kube/config

[suzukiapple]

node.jsアプリをサーバー再起動時に自動起動させる

init.dスクリプトを書いて昔ながらのSysVinit式で実現した。 Ubuntuは15.04からsystemdが採用されており、それを使った方法もある。 このページをご覧の方は、systemdについてもお調べいただければ。

自分の環境

Ubuntu 16.04.4 LTS (GNU/Linux 4.4.0-116-generic x86_64) nvm 0.33.8 node v8.9.4

foreverの導入

foreverのプロセス管理ファイルを格納するディレクトリも併せて作成する。 作成したディレクトリの所有者をnode.jsアプリを実行させたいユーザへ変更する。

npm install -g forever sudo mkdir /etc/forever sudo chown -R suzuki:suzuki /etc/forever

init.dスクリプトを作る

sudo emacs /etc/init.d/homebot

homebot

#!/bin/bash ### BEGIN INIT INFO # If you wish the Daemon to be lauched at boot / stopped at shutdown : # # On Debian-based distributions: # INSTALL : update-rc.d scriptname defaults # (UNINSTALL : update-rc.d -f scriptname remove) # # On RedHat-based distributions (CentOS, OpenSUSE...): # INSTALL : chkconfig --level 35 scriptname on # (UNINSTALL : chkconfig --level 35 scriptname off) # # chkconfig: 2345 90 60 # Provides: /home/suzuki/workspace/homebot/ # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: forever running /home/suzuki/workspace/homebot/ # Description: /home/suzuki/workspace/homebot/ ### END INIT INFO if [ -e /lib/lsb/init-functions ]; then # LSB source function library. . /lib/lsb/init-functions fi; export FOREVER_ROOT="/etc/forever" # load nvm export NVM_DIR="/home/suzuki/.nvm" [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm user="suzuki" workDir="/home/suzuki/workspace/homebot" pidFile="homebot.pid" logFile="homebot.log" foreverApp="forever" nodeCommand="coffee" nodeApp="node_modules/.bin/hubot --adapter slack" start() { echo "Starting $nodeApp" export NODE_ENV=production export HUBOT_SLACK_TOKEN="xxxx-xxxx-xxxx" sudo -E -H -u ${user} ${foreverApp} start --pidFile ${pidFile} -l ${logFile} --sourceDir ${workDir} -a -d -c ${nodeCommand} ${nodeApp} RETVAL=$? } restart() { echo "Restarting $nodeApp" sudo -E -H -u ${user} ${foreverApp} restart ${nodeApp} RETVAL=$? } stop() { echo "Shutting down $nodeApp" sudo -E -H -u ${user} ${foreverApp} stop $(cat ${FOREVER_ROOT%/}/pids/${pidFile}) RETVAL=$? } status() { echo "Status $nodeApp" sudo -E -H -u ${user} ${foreverApp} list RETVAL=$? } case "$1" in start) start ;; stop) stop ;; status) status ;; restart) restart ;; *) echo "Usage: {start|stop|status|restart}" exit 1 ;; esac exit $RETVAL

user="suzuki"：node.jsアプリを実行させたいユーザ workDir="/home/suzuki/workspace/homebot" ：node.jsアプリの置いてあるディレクトリ pidFile="homebot.pid"：pidファイル名(FOREVER_ROOT配下に置かれる) logFile="homebot.log" ：ログファイル名(FOREVER_ROOT配下に置かれる) foreverApp="forever"：foreverを実行させるコマンド(変更不要) nodeCommand="coffee"：node.jsアプリを実行させるコマンド nodeApp="node_modules/.bin/hubot --adapter slack"：node.jsアプリのパス

今回hubotを自動起動させたかったので、nodeCommand="coffee”だったり、export HUBOT_SLACK_TOKENだったりしています。 必要に応じて書き換えてください。

スクリプトを直接実行して動作確認。

sudo /etc/init.d/homebot start sudo /etc/init.d/homebot status sudo /etc/init.d/homebot stop

問題がなければ自動起動の登録。

sudo update-rc.d hoebot defaults

自動起動の登録解除はこれ。

sudo update-rc.d -f homebot remove

forever list してもプロセスが一覧に出てこない場合は、FOREVER_ROOTをexportすると出てくるようになる。

export FOREVER_ROOT="/etc/forever”

参考： https://dev.classmethod.jp/server-side/daemonize-nodejs-by-initd-forever/ https://gist.github.com/operatino/8389370

[g2travels-blog]

Where are we right now?

Check out our live-updating status:

[torontoseoulcialite]

Got out of my apartment for the first time in 2+ days for a treat! I didn't go ape at @gongchacanada, but even without sugar it's deeeeelish! • Pearl Milk Tea, no sugar • Oreo Milk Foam Earl Grey Tea, no sugar Which would you enjoy? If balanced isn't your jam, their drinks of the month are: • Strawberry Crème Brûlée • Brown Sugar Milk Tea 🍓🥤// #gongcha #gongchacanada #toronto #nodeapp #supportlocalbusiness #supportlocal *gifted (at Gong Cha - Queen & Spadina) https://www.instagram.com/p/CA0eIk8BWtR/?igshid=1v5kwmlkliyw7

[torontoseoulcialite]

Treat life like a ball pit - jump in! 🥂//@eighteen30to @jojoinstameets #eighteen30Meets#doitforthegram #eatingfortheinsta . . . . . . #jojoinstameets #drinkstoronto #torontoentertainmentdistrict #nodeapp #kingstwest #torontococktails #entertainmentdistrict #torontodrinks #torontoblogger (at Eighteen30) https://www.instagram.com/p/B6R_KLSFyPu/?igshid=r0z2xnunnxjo

[torontoseoulcialite]

Smokonut - @cirocvodka coconut, mezcal, @maliburumus, pineapple juice, coconut cream. An island getaway in a glass on a frosty Sunday! 🥥🍍🏝️ // #stk . . . . . #drinkstoronto #torontoentertainmentdistrict #nodeapp #Yorkville #torontococktails #torontodrinks #torontoblogger #artofdrinks #craftedmixology #torontofoodies #toreats #cocktailgram #tastethesix #hypetoronto #inclusive #cocktailart #tofoodies #foodiefeature #tastetoronto #downtowntoronto #torontofoodie #imbibe #streetsoftoronto #foodaholic #coconut #toronto (at STK - Toronto) https://www.instagram.com/p/B6LfKspBXt6/?igshid=1evl477ki1wor

[urmahkind]

Eh Bae Bae from EGG BAE🍳 - Soft Scrambled Eggs, Sweet and Spicy Bacon, Muenster Cheese, Tomato, Arugula, Pickled Shallots, Bae Sauce . . . Egg Bae (Eggs Before All Else) is a Toronto-based eatery mastering the craft of breakfast sandwiches with freshly baked buns from scratch, in-house prepared meats, and premium ingredients. . . . Menu -All sandwiches are made with a warm and fluffy in-house egg bun and free-range eggs. Salad box option available. Gluten-free buns are available upon request. . Thx, @cheatdayto! . . #Eggbaeto #sandwiches #torontofood #foodstagram #eggslut #foodie #toronto #egglover #egggang #Nodeapp #breakfastsandwich #curiocityto #sandwich #torontophoto #instafood #toronto_insta #foodgasm #tastetorontofood #food #egg #foodphotography #blogto #liketheegg #curiocitytoronto #tastetoronto #torontoeats #foodporn #eggs #eggsandwich #eggcellent #blogtolicious (at Egg Bae) https://www.instagram.com/p/BvwwPs-BWLW/?utm_source=ig_tumblr_share&igshid=1ny1snenssdtf

[caribdish]

Repost from @nevereatwong This Grenada Chicken Pelau meal kit from @caribdish was well packaged with everything pre-measured and a colourful one pager instructions that is easy to follow. And with that even though I never had tried this dish before but you can’t tell it is my first time making it ➡️swipe 👀 @caribdish is a local kitchen that offers many delightful authenic Caribbean dishes in a meal kit that is available for pick up or delivery. So stop serving your family the same meal every week, impress them with some dishes from @caribdish! Carib Dish 📍6171 Conin Drive, Mississauga Delivery available 📱caribdish.com Like•Save•Comment•Share #tastethesix #cravethe6ix #dishedto #tastetoronto #streetsoftoronto #yyzeats #torontofoodie #torontoeats #foodinstagram #torontofood #blogto #dailyhiveto #yyzfood #foodblog #foodporn #foodgram #nodeapp #canadatakeout #toptorontorestaurants #viewthevibe #craveto #caribdish #caribbeanfood #mealkit #homecooking #video #authenic (at Toronto, Ontario) https://www.instagram.com/p/CP32k8olAQM/?utm_medium=tumblr

[caribdish]

Repost from @nevereatwong This Grenada Chicken Pelau meal kit from @caribdish was well packaged with everything pre-measured and a colourful one pager instructions that is easy to follow. And with that even though I never had tried this dish before but you can’t tell it is my first time making it ➡️swipe 👀 @caribdish is a local kitchen that offers many delightful authenic Caribbean dishes in a meal kit that is available for pick up or delivery. So stop serving your family the same meal every week, impress them with some dishes from @caribdish! Carib Dish 📍6171 Conin Drive, Mississauga Delivery available 📱caribdish.com Like•Save•Comment•Share #tastethesix #cravethe6ix #dishedto #tastetoronto #streetsoftoronto #yyzeats #torontofoodie #torontoeats #foodinstagram #torontofood #blogto #dailyhiveto #yyzfood #foodblog #foodporn #foodgram #nodeapp #canadatakeout #toptorontorestaurants #viewthevibe #craveto #caribdish #caribbeanfood #mealkit #homecooking #video #authenic (at Ontario, Canada) https://www.instagram.com/p/CP32c7zFpuK/?utm_medium=tumblr