Where should I host personal websites? [closed] - hosting

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm making a simple website for a family friend. I'm still new to the whole coding world, so I'm still trying to figure basic stuff out.
In terms of hosting the site, I've found quite a few hosting services with different options. For example, I could get a BlueHost premium account and then be able to host all of my future websites.
My main question, from a business perspective, is how do companies or freelance front-end developers host sites? Then, on top of that question, should I do the same with this personal site.

If you currently are looking only for personal use, with very less traffic then the best that I can think of is HEROKU (also free tier is available).
For professional use I would recommend still recommend Heroku for a very troublesome free hosting, but if you need professional type control, I would like to recommend GCP/AWS (both of them equally).
Other Hosting to be considered Netlify.

Related

Heroku / Devops: Do I need an extra server instance in Asia for my Chinese users? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
My current user base is all in the US so my current Heroku server is in US-East. However, I am about to add Chinese localizations to my app so I expect a lot of people in China to download my app. I am afraid that my US-East server will be too far and latency will be much higher.
Is it common to deploy multiple instances of my server in different locations? Or can I assume that technology has developed to the point where latency will not be an issue for a CRUD app?
Building multi region apps can get complicated very quickly and often introduce new problems on their own. For example, it’s easy to host an Asian app, but what database does it talk to? If it has its own database for speed, how do you sync with your American database? If it will continue to use the American database, you’ll still have latency.
If your application is fairly simple, you’re almost key certainly better off to keep with just a single US based application, and use a CDN such as Cloudflare to cache assets closer to asian clients.

Why are there so many free chrome extensions on the chrome web store? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I want to develop and monetize a video recorder and screen capture chrome extension but I fail to understand why there are so many free extensions on the Chrome Web Store. I see these as fierce competition for my extension since I want to offer In-App purchases. So, I ask, why is it there are so many free Chrome extensions and how do their developers make money?
Not all the extensions are developed by professional programmers who need to charge for them for a living. Many programmers develop extensions with the only purpose of providing a useful service. If they can offer that for free, I can't see why not.
In my case, I make money from my day job (completely unrelated to programming). I benefit from using free software (Linux) and my free extension is a way to contribute to the community.

How do you "show off" your web development work? [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I have searched quite a bit and haven't found an answer yet. I am learning to develop websites and am ready to put together a portfolio of everything that I have been building. My question is, what is the best/most cost effective way to display my work? I have bought several domain names and hosting for them but it's getting expensive. I want to be able to make a portfolio of my work without buying a domain name/hosting for each of them. I know I can take screes shots but this doesn't show many details of the site. Maybe host them on my own computer since they won't have much traffic? I'm sure I'm missing something obvious. Thanks for the help!
Having a personal website/portfolio is great, and you only have to pay for your own domain, which is usually about $10/year. A great free option -- that also has the benefit of showing off all your code -- is hosting projects on GitHub Pages.
I think what you are looking for is something like DigitalOcean. Digital Ocean offers very cheap and reliable server hosting so that you can do exactly what you want with your hosting. Also, with a click of a button you can install something like LAMP (Apache, MySQL, PHP). This can show your full completed projects and all of your code, unlike GitHub Pages. Also, I know 512MB of RAM my not seem like much, but it is plenty for a basic web server. And 20GB Should be good unless you also are looking for a filesystem.
Good Luck!

Recommendations for linux hosting [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm about to embark on a new project which will require linux hosting, so I was hoping for some recommendations. The full technology stack is yet to be finalised, but it very likely to feature: nodejs, ruby and some form of NoSql(couchDB/mongoDB).
As well as supporting a variety of technologies, the hosting also needs to be scalable. Also, it could do with being as cheap as possible.
Any suggestions?
Thanks
Iain
From my personal experience I highly recommend Linode. They're probably the best on the VPS market. If you don't mind starting with a little bigger server, you can try Amazon EC2, which is also a great service.
I haven't had a single problem with Linode in over 2 years, and every time I needed something on tech support, the reply was almost instant.

Difference between/use of dev.site.com and beta.site.com [closed]

Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
Am trying to implement a few deployment policies in my organization. Usually, we do all the development on localhost and then simply deploy the site to the production site (i.e. site.com). Am trying to place a rule to first deploy the site to say beta.site.com, test it completely and then deploy it to the final site. Now I know many companies use dev.site.com, then beta.site.com and then finally site.com.
Am wondering what exactly is the purpose of dev.site.com and then beta.site.com. Will be both be active at the same time or is it that during development we should use dev.site.com and then later beta.site.com? What exactly is the use of a staging server/site then?
Please feel free to ask if anything is unclear. Thankyou for your time and patience.
This is totally up to interpretation and there are no binding rules, but everywhere I've been it's been along these lines:
dev. for the development environment, a full mirror of the site/project/product, to which developers upload changes to find out whether things work at all, and where they can test new technologies / products / versions / settings. Often updated with data from the public version (if one exists)
beta. for staging versions that have been tested by the developers, but need "higher-level" user testing / review before going public, already available to a wider circle than just the developers (colleagues, the whole team, beta testers, the public, etc.)
I would expect that your dev site would primarily be for internal Q/A. For a site like this, I would restrict the incoming IP addresses to those of your own company so your development site isn't exposed to the general public accidentally.

Resources