User Power
Value/Post Ratio
138%
- Jul 24, 2019
- 58
- 80
Thanks for stopping by. I see your point about StackOverflow, given the strong presence of developers in this forum I thought it wouldn't hurt...
1. Will DM
2. I understand the differences but I do not understand how to approach this using multiple sites. I know how to point a domain to a server with files for one website (so far I've only used Heroku). However, when a customer buys a new domain name, a new configuration has to be created with this site and the domain be pointed there. Are you saying that I can have only one server that can handle multiple websites, like shared hosting? Is there a good resource to study for this problem?
3. Speed, simplicity and keeping costs low. I will go with the solution that obeys these, but simplicity is more of a priority admittedly.
4. That's great, I thought WordPress was the only option and I wanted something that is much simpler and with a simple learning curve.
2. Yes, one server is enough. Study about "Reverse Proxy" such as Nginx and Docker.
3. Go with one DB (put it in the Docker - as well as everything else), create an API around it and expose it as a service.
Dislike ads? Remove them and support the forum:
Subscribe to Fastlane Insiders.