Saas- Idea to Reality

abhishekq61 — Sat, 18 Apr 2020 12:45:06 +0000

Disclaimer: I am writing this blog on behalf of StaqLab tunnel Staqlab Tunnel-Expose Your localhost .This blog contains a refrence of services provide by staqlab tunnel.

If you are new to software development or a student you must have considered what is basic lifecycle whish a Saas Product follows right from being an idea to reality.
Here i will try to explain you the key steps involved to develop your own Saas Products which company follows to make their product go-live to general public.
Software development lifecycle can be broadly classified in broadly three main categories leaving some miscellaneous part like funding, hiring etc behind because that altogether a completely different story

Developing

First you write some code in programming language of your choices and needs. Then you will have to decide what framework and existing technology you can rely you to be a part of your software technology stack.
Choosing the right technology stack is a very crucial and important task and it should be done with much sincerity and keeping the future needs and scalability in mind.
You can can't come the other day your software proves to be successful venture and start the whole development process right from the scratch.Spending a little bit of time in choosing right technology will save much of your time in coming future.

Testing

There are basically in-app test and AB Tests.

In-App Tests
This is some code you write- to test the code in development will work properly or not. Funny isn't it -the paradox.
There is generally a test folder which relies in your code directory. Before introducing a new feature or solving some existing bug-you write a testcase for it.
Generally you give some input condition to your test code and then expects a specif output.If the code under test produces the right output you assumes your code is working perfectly.
You write a series of crucial testcases and then can proceed to A/B Testing.

A/B Testing
This is end-to-end user experience testing. In this there is not some machines who test your codes. There are actually some real beta-users or testers who test your software for user usability and user experience
For testers you will need to give them some public url which they can open in their respective PC and begin the testing. To do so you can deploy the code on some beta environment but it do comes with a cost and also its not so effective approach if there are many parallel development going on. Deploying a server for every such bug/ feature testing would be a heavy burden on founders pocket.

Here comes the role of tunnelling to save you from this dilemia .
You can you StaqLab tunnel Staqlab Tunnel-Expose Your localhost .It exposes serer on your machine over to the public internet.
The develoepr/tester will need to run the code on his machine and using Staqlab Tunnel-Expose Your localhost he can generate an public url.

Screenshot taken from app.

You can also pass-on that link to anyone who is not on your private network too.You ac also give it to your clients before actually making the changes live.
After all the bug are resolved and testers give you a go-ahead on user usability and experience your software is ready to actually go Live, after some party and snacks Ofcourse!!

Deployment

First determine minimum server requirement for your software to run properly. Minimum the requirement minimum the cost for servers. Don't be too miser ofcourse.
After you drilled down the requirement choose some cloud service providers you like such as AWS, Digital Ocean, Heroku to name few.
Setup the server and install dependencies on it you need for your baby software.

After that copy your code to your sever and run that magical start command that ignites your application - most probably yarn start if you working on JS.

If you are tired of deploying the code everytime you make some changes you can use CI/CD services to automate this work for you.

Now start marketing your product and make your product available to the world!!!

Debug#Host Servers on your localhost

abhishekq61 — Sat, 04 Apr 2020 12:33:58 +0000

Disclaimer: I am author from Staqlab Tunnel.This blog contains reference to services provided by tunnel-staqlab.
Do give me a thumbs up, if you find this blog useful

One of the major part of coder life is testing.When it comes to stand-alone consoles apps the testing is pretty easy.You just hook up some debug breakpoints in your favourite IDE and hit the debug button and vola you could see all the variables and inspect your code right-in where you placed your breakpoint.

But what if you rely on some external services to get your code working...

As for example, most of the REST/HTTP applications contains webhook routes from external services as a major part of the workflow.

You just want requests from these services to be forwarded to your localhost!!! But wait what, is this possible?
Can your localhost be connected over to the internet and traffic from web is forwarded to your local machine?

Yes this is possible through principles of SSH Tunneling.
There are already tunnels servers like Staqlab Tunnel which forwards traffic from web to your localhost.

The guide on staqlab is pretty self-explanatory. However lets discuss step-by-step procedure here also.
I will assume your server is running on localhost:3000
At the end of this tutorial you will be able to get a public url, which points to server running locally on port 3000.Do mind that the port can be any valid port.It doesn't necessarily be 3000

Step 1:

Download tunnel client for you pc from https://tunnel.staqlab.com/downloads

Step 2:

Go to your downloads folder and unzip the zip file downloaded

Step 3:

Open terminal and navigate to folder where you have placed the downloaded file. and paste below command
./staqlab-tunnel 3000
if you want to have a custom domain.Look, its also possible.Replace above command with below command.
./staqlab-tunnel 3000 hostname=<your-domain>
e.g
./staqlab-tunnel 3000 hostname=kitty-lovers

After following above steps, you will be greeted with 3 urls on your terminal window.

First one, is inspector url. Its a powerful tool where you can investigate and replay all the http/https traffic from/to your server

The second and third url are http and https versions of the the public url which is in this case is

Just copy this url and paste it in your browser and see the magic, you can
see response from your pc on the your browser window.

Share this url with your colleagues, and display your work over the web!!

DEV Community: abhishekq61