A Super simple Multi-tenant SaaS Application
Budget: $30 – $250 AUD
The Goal of the projects is a SaaS application allowing users to register their account name as subdomain. (Reverse-proxy for subdomains with SSL)
We do have a node service and Nginx load balancer and secured the port 443 with a let's encrypt certificate. Now every time a customer want to point their own domain (example.com) or (www.example.com) we need to issue the certificate for them
What you deliver:
- Assuming that we have a domain on our local machine set up with the name "(link removed)"
- A Dockerized solution with "Nodejs(express)", "Nginx" and "Let's Encrypt" and any database of your choice.
- Ability to create an account. No auth is needed, just be able to create a branded account name as a subdomain. Examples: "account1.brand.local" and "account2.brand.local"
- Ability to register another domain like "[https:/][brand2].com" as an A record on the domain DNS with our service and register and auto-generate a Let's encrypt CERT
- The type of the challenge for the DNS should be (DNS-01 challenge)https[://]letsencrypt[.org]/docs/challenge-types/[#dns-01-challenge]
We do have a node service and Nginx load balancer and secured the port 443 with a let's encrypt certificate. Now every time a customer want to point their own domain (example.com) or (www.example.com) we need to issue the certificate for them
What you deliver:
- Assuming that we have a domain on our local machine set up with the name "(link removed)"
- A Dockerized solution with "Nodejs(express)", "Nginx" and "Let's Encrypt" and any database of your choice.
- Ability to create an account. No auth is needed, just be able to create a branded account name as a subdomain. Examples: "account1.brand.local" and "account2.brand.local"
- Ability to register another domain like "[https:/][brand2].com" as an A record on the domain DNS with our service and register and auto-generate a Let's encrypt CERT
- The type of the challenge for the DNS should be (DNS-01 challenge)https[://]letsencrypt[.org]/docs/challenge-types/[#dns-01-challenge]