loading...

re: Organize Your Side Projects with a Single Domain! VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Great article! I do have a few questions. Let’s say that I have a full stack node app, that uses, for example, mongodb as the db. And now that I...
 
  1. It sounds like what you're describing might be outside of the scope of this article. Side project domains are a great way to showcase your live projects to potential employers or clients, or to setup small projects that you don't have enough traffic yet to justify buying it's own domain. The keyword in that last sentence is 'live projects', the end goal is to give users a way to access the site or app on the web (think Twitter or Youtube). In your case, it sounds like the end goal is to sell developers the code that they can use to build 'instances' of your app, which doesn't make as much sense to use a side project domain for. Let me know if I misunderstood what you were saying!

  2. I haven't worked a lot with node, but I always recommend using cloud service providers as opposed to traditional hosting services, so I'd look into Heroku, AWS, Google Cloud, or Digital Ocean. Heroku's probably best if you want to keep things simple!

 

Sorry! I was in a rush, so I couldn't write what I meant properly.
The end goal is to sell my app to small companies. Well not really to sell it, but make them use my app.
I'll take another example. Let's say that I have built an invoice app which will help all the groceries stores in my town. This is what I meant by different instances. This implies that grocery store X will have different products than grocery store Y, but they would still use the same app that I built.
So the final question is: If I want to have my app used by multiple users, I should make sure that for every app I use a different domain so the data won't get mixed up?

I'm sorry if I'm going too much beyond the scope of the article, I've been having this unclarity for a while.
Thank you once again!

Code of Conduct Report abuse