Dollibar SAAS Setup and hosting

Maintaining my Dolibarr
1

Dear Team,

We want to host dollibar as a SAAS application. What the needed Steps and server criteria needed for dollibar SAAS setup?

How it can be hosted? What are details for the same

Please let me know on this.

Thank you :slight_smile:

3

Dear @ashwin1109

Sorry, but if you can not install and explore Dolibarr to answer those questions yourself, then I do not believe you should offer ANY SAAS, be it Dolibarr or any other software.

Because how would you know how to fix issues yourself if you didnā€™t learn yourself how to answer such seemingly simple questions to formulate, but hard to really answer, because it all depends on a lot of different factors, so many different factors that I donā€™t even want to begin listing them.

Best regards, JonB

1 Like
4

As @jonbendtsen mentioned, hosting any ERP, especially working with it as SaaS, isnā€™t as simple as something that can be explained in a forum post :sweat_smile: If youā€™re asking such a generic question, one would assume you donā€™t have much technical knowledge, and your service could easily fail without you knowing why or how to fix it.

That said, I can share my 8-year experience offering hosted Dolibarr (with plans ranging from 8 to 30ā‚¬ monthly). Itā€™s not the best setup in the world, and there isnā€™t really a ā€œbest way to do itā€. It depends on the technologies you know (or that your technical person knows) and the volume of Dolibarr instances you want/expect to handle.

In my case:

  • 2 CPU cores and 4GB RAM VPS, from the best VPS provider Iā€™ve ever had (Iā€™ve been hosting webapps for 30 years): clouding.io (Barcelona, RGPD)
  • One subdomain per client (per Dolibarr instance actually, as some clients have multiple Dolibarr instances), so each has their own database and file space
  • Since everything is on the same server, Iā€™ve programmed several bash scripts to automate certain tasks, such as one to propagate code changes from one instance to all others (when I discover and fix bugs in my modules or third-party ones)
  • For this reason, I keep all clients on the same Dolibarr version always. So far, no one has complained. Usually, people donā€™t complain if the software works :sweat_smile:
  • Last but not least, a robust backup system. In my case, I use borgbackup software for Linux CLI to make a backup EVERY HOUR to a remote server in Hetzner (Germany, RGPD) that is 100% natively compatible with borgbackup, and I sleep very peacefully. I created custom bash scripts to automate the use of borgbackup adapted to this hosting infrastructure and to perform a prior database dump, so everything is stored in one place.

Good luck.

1 Like
5

By the way, itā€™s important to mention the DoliCloud project and its opensource software specifically designed for setting up a Dolibarr SaaS solution.

This software helps you automate practically everything: from creating new instances, including demo or trial instances, to handling periodic billing!

I personally reviewed it and found it interesting, but honestly, Iā€™m satisfied with how I manage my SaaS service, and switching to DoliCloud doesnā€™t make sense for me at the moment. However, it might be more useful for your needs. You should definitely check it out if you havenā€™t already.

I must warn you though, itā€™s not simple to install, configure, and manage. Youā€™ll definitely need people who know what theyā€™re doing.

1 Like
6

There is a big difference between ā€˜hosting dolibarrā€™ and offering a business grade service that meets the compliance requirements (data protection laws) of your SME customers in different countries (e.g. Europe, US, Canada, South Africa etc) and business continuity/disaster recovery.

Also you need to think about how you are going to differentiate your service, there are lots of low cost Dolibarr services, all exactly the same.

We have addressed all of the above points - drop me an email and I will share more detailed info, mark.hutchinson@accellier.com

1 Like
7

concuerdo con todos los colegas anteriores y te espongo ni situacion, llevo un aƱo y medio con mi servidor el linea tengo proxmox gestionando mis contenedores y funciona bien tanto como dolibarr pero sigo asiendo pruevas y sigo encontrando errores y aprendiendo a solucionarlos, en produccion se que eso sera peor, estoy por empesar a vender mi servicio pero se que me encontrare con mucho problemasā€¦ a mi criterio tienes que preguntarte, que pasaria si Xxx, y pensar en todos los problemas q puedas tener o contratar a alguin que los solucione, exitosā€¦

8

Iā€™m exploring a setup for hosting multiple Dolibarr instances under the same domain and wanted to get your thoughts. The proposed structure looks like this:

  • https://sub1.dolidomain.com/instance-1
  • https://sub1.dolidomain.com/instance-2
  • https://sub1.dolidomain.com/instance-n
  • https://sub2.dolidomain.com/instance-11
  • https://sub2.dolidomain.com/instance-12
  • https://sub2.dolidomain.com/instance-n

Each instance is stored in its own folder, with a separate documents directory and an independent database for each.

Key questions:

  1. Are there potential security risks associated with this setup?
  2. Would there be any performance concerns with this type of configuration as the number of instances grows?
  3. Are there best practices for organizing and securing this kind of multi-instance deployment?

Looking forward to hearing your insights and experiences. Thanks!

9

We have our own Dolibarr ERP SaaS [Thrive ERP] (Thrive ERP | Accellier), at the time I am writing this this web page is being updated and has some formatting/content issues but you will see we have extended the standard Dolibarr functionality considerably.

Our domain structure is - https://customername.app1.domain.com

We have set our SaaS up so all customers use a single line of code, but each customer has their own configuration file and database.

We have quite a few customers (this SaaS has only been runnning for 6 months, but growing quite quickly) that have between 2 and 40 users and performance is fine ā€¦but all of our servers have SSD discs, and you need ot have enough computing power to handle peak loads and also for when customers decide to run large reports.

In terms of securityā€¦

  • Web application firewall
  • Secure configuration, Regular vulnerability scans & fixes
  • Update everything/keep patched every 2 weeks
  • Implement access controls
  • Malware protection
  • Your database should be in a seperate server to the application server (also not accessible directly from Internet and only accessible from application servers.
  • Good backups
  • In our case we have a resilient hosting infrastructure running across multiple data centres, with clustered databases so we have resilience built in.
1 Like