Fix the gap in the installation guides.

[Martech-WorkShop]

Describe the ISSUE
When using the official guide on how to install Lago, the guide seems to target a test environment based on "localhost".
That is perfect for playing but not for serious testing, much less for production.
Since there are no more options, you are forced to jump into Kubernetes if you want something more serious.

But, unless you are an accounting firm, you have no use for a K8S deployment, but at the same time, you can't run it on "localhost". You need a proper VPS setup on the cloud, or like in my case, you need to run it on a larger server, behind a proxy.

I have requested the pricing for the premium hosted version and while I am certain the price is fair for a larger organization, for many SMB's its a tad steep.

I am certain Lago FOSS is very enticing to many SMBs who also might not have the technical capabilities to deploy on their own without guidance or help.
Hence, I suggest expanding the number of guides by adding a VPS guide, a Reverse proxy guide, maybe even a non-compose guide, which could make the architecture much more obvious to a whole lot more people.

In all these cases I would be happy to work on the guides myself if you consider these could in fact be relevant to the project.

NOTE: A development installation guide is also provided and the corresponding compose file found in the repo, which is great but does not solve the issue for staging and production since it is also focused on local development for "app.lago.dev"

Steps to reproduce the behavior:

1. Go to the getting started, docker installation guide,
2. Follow the steps from any computer other than localhost.
3. Resulting deployment will not work.

Expected behavior
Clear and concise guides (or even and automated script (or two)) facilitating installation for the most common use cases, whatever those are.

Support

• OS: Linux
• Version: Latest stable

[jdenquin]

Hello @Martech-WorkShop

I totally understand your point and you're right.
We started to work on a Pulumi recipes for AWS some months ago to provide an other deployment option. It's not totally done and still WIP.

We'll work on some other options this year :

• One click deployment
• Better documentation to support those cases

[Martech-WorkShop]

Thanks for responding @jdenquin

Sounds good, let me know if I can be of any help...
Feel free to close if there's nothing else to discuss.