Hopefully, you find this article useful! Let me know what you think. Thanks!

Hi, I created this plugin to help people with their support after spending 7 hours in a queue to get an answer to my (pretty simple and standard) question.

This tool has a lot of automation and customization, and it's not stupid as most chatbots.

If you have a website, you can create a chatbot even without registration, here: https://enumhq.com/test-drive

Let me know what you think.

Thanks!

ORM is used in this boilerplate, and it's SQLAlchemy. I need to mention it somewhere.

Thanks! Which stack do you use?

Thanks for your great comment.

You are not the first person who wants companies/teams. But I'm not sure I understand you well, guys. Can you give more details, with some examples, why and what it could be useful for?

I know, I know!! I will include unit tests... some day... soon.

Thanks for your opinion! It's probably more valuable for me than from people who like it :)

But you are a little bit wrong. Currently, it supports migrations and will support deployment very soon.

I don't agree about ReactJS and Webpack. I start using both in my projects and it didn't take too much time to learn them. Even if I don't know them deep I know them enough to use in the real projects.

I agree that currently, Django is more might than this project but it's just a beginning.

You are not right about modules too. It has nothing to do with Python's modules, I "invented" my own "modules" - it's just a combination of front-end code and Python API in one folder. And I created them to make the project more scalable. I don't know though if I gained this goal or not - yet.

WOW! You put a lot of work into it, and I'm going to research it. Just wondering, what made you create this phenomenal work?

Hi KRains

Thanks for the kind words. To answer your question, I can say I had a many reasons to create this document. First and foremost I’d like to create an open source project around these specifications and see if I could generate interest and invite contributors to jump on board. Second, is to provide a working document for the community scrutinize and critique as it’s still very much work in progress, and before committing to building the solution I wanted to ensure what is built is done so in a way that gains acceptance and use.

Also, I see that Cloud and more particularly SaaS has a lot of bias surrounding it’s use both from a commercial and personal perspective. This largely has to do with how SaaS providers store and use peoples’ data. My aim with PAL is to create a flexible solution that takes all perspectives into consideration based on the type of offering and what is acceptable by the customer or user of the SaaS offering.

I could go on further to say that since SaaS has become such a large segment of the Cloud market I also feel it’s important to keep as much of it as open and free as possible as to allow smaller players the chance to offer SaaS solutions. Since the market is largely dominated by Big Tech this is becoming increasingly more difficult and that has a lot to do with the lack of resources available to smaller companies. It may not seem apparent to most people especially those in countries where internet services are easily available but currently where I’m located, a country where the economy suffers greatly, the low cost of establishing SaaS solutions for businesses vs offering custom built in-house solutions is a far more feasible option.

Anyway, I hope the you find the contents of the document useful and helps you in some way with your project :)

Regards James

Okay, I got your position. And thanks a lot for your efforts! I will contact you if I have questions/suggestions (I found your email at the end of the doc).

Update the license, now it's MIT.

Looks interesting although it seems to me not SaaS-oriented.