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.
Related
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.
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.
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!
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I'm looking to set up a TeamCity server for continuously building a .NET web application. I already have hosting, so I don't want to get a whole new hosting account such as AppHarbor.
I don't maintain my own physical server, nor do I want to.
I also don't want to have to pay $50 or more per month for an entire dedicated Windows machine, just to host TeamCity.
I really don't care if it's slow and on a shared machine, as it's just continuous build which will be running in the background.
I'll want to have the outputs automatically deployed to a server of my choice through FTP.
Is there anyone on the market providing hosted TeamCity environments?
AppVeyor CI provides hosted continuous integration for .NET developers.
Disclaimer: I'm the developer of this service.
If your open source project you can get a free account at Code Better http://codebetter.com/jameskovacs/2009/02/24/announcing-teamcity-codebetter-com/ I don't know of any for non open source.
OnCheckin.com offers Cloud Powered Continuous Deployment for.Net websites and services.
Disclosure: I am the developer and founder of this service.
Just came across BuildBox (now Buildkite) from a tweet from someone I follow. Seems like a suitable solution to this.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
My next project will be a lightweight PHP alternative to Trac, since Trac is often confusing to install and is often a little too big or feature-rich for smaller project.
Features planned so far:
Wiki
Bug tracker
Forum(s)
Static pages (easily edited of course)
Markdown support
No code repo hosting (I consider this a feature since most people would prefer to use a 3rd party such as GitHub for the actual code hosting)
My question: if you were to use a self-hosted app for making a website about one of your open source projects, what would you want? Is there anything on that list that's missing? Would you absolutely require the ability to actually host the code repo on the site itself, or would you be ok hosting the code elsewhere (Google Code, GitHub, BitBucket), and using the site only to upload major versions?
Summary: if you were to use a self-hosted app to provide info and support for an open source project of yours, what would you want it to be like?
Redmine is my current favorite, I usually install it via BitNami