Seth Talks About Saas...

[TheMcD 6]

Hey all,

 

Seth talks about growing rich slowly via uBot and SAAS in this article:

 

http://network.ubotstudio.com/blog/get-rich-slowly/

 

Three pieces we need:

 

1. Web based user interface.

2. Connection to uBot (your software/service).

3. Web output for the user.

 

* There are some variations to this, but we'll use this for now.

 

Let's use a sample project like so:

 

User uploads a video to be put up on YouTube, metacafe, Vimeo, etc.

 

What are some of the easiest ways to handle steps 1 and 3 (above)?

 

Here is my crack at it...

 

1. Use a WordPress site (with some sort of loging in to your service).

2. Use a plugin that allows a user to upload a file.

3. Your bot uploads to the three services.

4. Not sure how to show output to user.

 

* I do know that the above "crack at it" is an oversimplification, but it's just to get a minimum viable SAAS up and running.

 

I'm sure I can hear some of you now:

 

"Make the integration with PHP & MYSQL.", and Bob's your Uncle.

 

Well I do know some PHP, really nothing about MYSQL. And last but not least ... security! Doing your own site and security (gives me a headache)... I digress.

 

Anyway...

 

How have you gone about it? (You are doing this already, your own SAAS.)

 

How would you go about a minimum viable SAAS project?

 

Thanks and I look forward to what we all learn here.

[HelloInsomnia 1103]

This is going to be a simplification and will require (PHP/Python/etc some web language) & MySQL knowledge (the latter is easy to learn so don't sweat it).

 

1. Person logs into website and orders a job, the job gets placed into a queue. This "queue" exists in the database as a table.

 

2. Bots are checking this table inside of the database on a regular basis. Eventually, one picks up this "job" and marks it as "pending" (possibly moving this to a pending table it depends on how you set it up)

 

3 A. Bot fulfills the job, marks it as complete and sticks it into another table, executes something on the front end to alert the user the job has finished.

 

3 B. Bot does not fulfill the job, repeat or send back to queue.

 

3 C. Bot crashes, job is not fulfilled. Eventually this has to be accounted for. Maybe you tag the job with the bot ID and check the status of that bot for crashes after so long. Maybe you have another bot that restarts the bots if they crash, the bots can store current job locally and it restarts and carries on. Whatever it is this is something you need to think about if you want to fully automate it.

[Code Docta (Nick C.) 638]

Yup,

 

Ideally you would want an RESTFUL API allowing users access to your ubot.exe whether it be on their VPS or computer at home. This way they use their resources to do the hard work. Your API will allow them to schedules tasks and access several bot services, much like a membership site with/without the user interface. You can also use FB/Twitter/Google etc. to login to your service.

 

Your API could also provide bot status along with ability to send a signal to the scheduler to restart your bot if not running/crashed. Your bot should be headless and rand from the scheduler. While your bots UI has its own screen/tab it would communicate via server(mysql), sqlite3, or JSON file using a MVC pattern.

 

Then you could make and android/IOS app to communicate with both(API/bot).

 

API can provide essential code to run you bot as well. Without that code your bot would be useless or even empty in the case of Python.

 

So, essentially, the web service just allows access to your bot/bots that have its own scheduler(or scheduler on your server) using the users resources(CPU/HD).

 

Your scheduler/bot has a login screen to use a social media site to login and once authenticated you get your scheduler and/or your bots UI.

 

 

I know it's easy with Python and with access to Python in UBot well then, should be enough said.

 

Regards,

Nick

[TheMcD 6]

Yup,

 

Ideally you would want an RESTFUL API allowing users access to your ubot.exe whether it be on their VPS or computer at home. This way they use their resources to do the hard work. Your API will allow them to schedules tasks and access several bot services, much like a membership site with/without the user interface. You can also use FB/Twitter/Google etc. to login to your service.

 

Very nice input.

 

An API.

 

What would be cool is to create a base API, that could be used by everyone. Sure, if you need yours to accept a couple pieces of additional data, you just add that to the base API and voila, you have connection between web interface and uBot.

[Code Docta (Nick C.) 638]

ya, say the "SAAS dev" create a service that all ubotters can use. A membership site that has a use3r interface for the UBot Dev to configure multiple profiles to be used with multiple bots. Then the bots/device just has access through the API.

[TheMcD 6]

To add to the ideas and conversation, here is an article on using Amazon web server for free (hosing your bot on a Windows server):

 

http://network.ubotstudio.com/blog/set-up-ubot-studio-on-a-free-amazon-vps-in-ten-minutes/

 

* I personally don't mind paying for Amazon hosting if it does what I need, and it's price nice.

[TheMcD 6]

User: TheBigWeb has a bot that uses a PHP front end.

 

Here is his post: http://network.ubotstudio.com/forum/index.php/topic/20533-my-software-was-featured-on-indiehackerscom/?do=findComment&comment=127530