edwardchanjw/tideflow.platform.app.yaml

## tideflow.platform.app.yaml
**Core Zapier Clone: TideFlow. CI and Live on Platform.sh in 5 minutes.**

As a developer that having some exposure of pre-Cloud era, until currently cloud subscription based + Pay Per Use economy, I had seem the economy of the Cloud's Technology evolved like Telco industry did 10 years ago.

Zapier, one of the coolest automation tools in the market, I am not here to tell your whether the Zapier's economy is right or not. It surely worked for certain business, if you able to grab and compete with competition, or niche to hold your market. Either way, Open source's edition would mostly helped, at least when truly transparent processing, and "Data never gone out your infrastructure kind of operation"
For list of open source code workflow automation tools such as node-red, flogo, node-red, etc. For the review of all of them, it can be valid for another blog post. I had choose to tested Tideflow, as it having super minimal proof of concept to get into it, and template. Potentially understand the downside of small project comparable to big project like node-red, and Flogo.

**Why I am choosing hosting it via Platform.sh vs Heroku vs Scaleway?**

Pro:
- Platform.sh is PaaS, similar to Heroku, stay focus on Stack rather than Linux Administrator, if you deep dive into feature building
- Platform.sh is Bandwidth unlimited. (Mostly second highest in the list)
- Platform.sh included Support on compliance and Web framework
- Platform.sh having automatic SSL
- Having Travis-CI like with their Continuous deployment included, make your workflow only involved Dev and Ops

Cons:

- Platform.sh do not have buildpacks.io of Standard. but it having Travis-CI like of Building and Deploy step.

Step 1:  Setup TideFlow in Travis-CI   (Optional when I create other post, to use sorely Platform.sh)

1. Clone of https://github.com/tideflow-io/tideflow
2. Write your .travis.yml file like https://github.com/edwardchanjw/tideflow/blob/master/.travis.yml
3. Yoi got the Travis-CI's build version of of Tar.GZ file

Step 2.  Writing Platform.sh's Continuous deployment's YAML

1. Clone https://github.com/platformsh-examples/platformsh-example-meteor
2.  Copied the to the repo and also the .platform.app.yaml in Step 3.
3. https://gist.github.com/edwardchanjw/de5eaff958f92975da61f16e33dc5cc4
4. change the ROOT_URL to your Platform.sh's provided URL, probably I can update Step 3 later...because I don't have time to test it now.

I have the urge to learn some Next.JS first, then I am bringing you the updated version of this article and another how to setup NEXT.js continuous deployment on Heroku and Platform.sh in next week. If you having any question, please don't afraid to ask, but I might update it after 2-3 day.

So that is, I am probably also setup a subscription SaaS soon. At the same time, I am going to write some React tutorial of dashboard of photo grid builder, and upgrade it with less than 100 line change and total 500-2000 code (of course never include the create-react-app's code and React library ecosystem) and support both and dashboard of React Component's Grid Builder. I would like to demonstrate how good when the component encapsulation and code portability and compatibility on React ecosystem, hopefully get accepted for Writer program for cover some living expense. At the same time, which probably using Next.js and Firebase, because I am really wanted a shorter code, less memory usage, responsiveness. Probably I would write another article hosting Next.js and Firebase boilerplate on Platform.sh and Heroku. See ya next time.
	Core Zapier Clone: TideFlow. CI and Live on Platform.sh in 5 minutes.

	As a developer that having some exposure of pre-Cloud era, until currently cloud subscription based + Pay Per Use economy, I had seem the economy of the Cloud's Technology evolved like Telco industry did 10 years ago.

	Zapier, one of the coolest automation tools in the market, I am not here to tell your whether the Zapier's economy is right or not. It surely worked for certain business, if you able to grab and compete with competition, or niche to hold your market. Either way, Open source's edition would mostly helped, at least when truly transparent processing, and "Data never gone out your infrastructure kind of operation"
	For list of open source code workflow automation tools such as node-red, flogo, node-red, etc. For the review of all of them, it can be valid for another blog post. I had choose to tested Tideflow, as it having super minimal proof of concept to get into it, and template. Potentially understand the downside of small project comparable to big project like node-red, and Flogo.

	Why I am choosing hosting it via Platform.sh vs Heroku vs Scaleway?

	Pro:
	- Platform.sh is PaaS, similar to Heroku, stay focus on Stack rather than Linux Administrator, if you deep dive into feature building
	- Platform.sh is Bandwidth unlimited. (Mostly second highest in the list)
	- Platform.sh included Support on compliance and Web framework
	- Platform.sh having automatic SSL
	- Having Travis-CI like with their Continuous deployment included, make your workflow only involved Dev and Ops

	Cons:

	- Platform.sh do not have buildpacks.io of Standard. but it having Travis-CI like of Building and Deploy step.

	Step 1: Setup TideFlow in Travis-CI (Optional when I create other post, to use sorely Platform.sh)

	1. Clone of https://github.com/tideflow-io/tideflow
	2. Write your .travis.yml file like https://github.com/edwardchanjw/tideflow/blob/master/.travis.yml
	3. Yoi got the Travis-CI's build version of of Tar.GZ file

	Step 2. Writing Platform.sh's Continuous deployment's YAML

	1. Clone https://github.com/platformsh-examples/platformsh-example-meteor
	2. Copied the to the repo and also the .platform.app.yaml in Step 3.
	3. https://gist.github.com/edwardchanjw/de5eaff958f92975da61f16e33dc5cc4
	4. change the ROOT_URL to your Platform.sh's provided URL, probably I can update Step 3 later...because I don't have time to test it now.

	I have the urge to learn some Next.JS first, then I am bringing you the updated version of this article and another how to setup NEXT.js continuous deployment on Heroku and Platform.sh in next week. If you having any question, please don't afraid to ask, but I might update it after 2-3 day.

	So that is, I am probably also setup a subscription SaaS soon. At the same time, I am going to write some React tutorial of dashboard of photo grid builder, and upgrade it with less than 100 line change and total 500-2000 code (of course never include the create-react-app's code and React library ecosystem) and support both and dashboard of React Component's Grid Builder. I would like to demonstrate how good when the component encapsulation and code portability and compatibility on React ecosystem, hopefully get accepted for Writer program for cover some living expense. At the same time, which probably using Next.js and Firebase, because I am really wanted a shorter code, less memory usage, responsiveness. Probably I would write another article hosting Next.js and Firebase boilerplate on Platform.sh and Heroku. See ya next time.