I'm currently running Ubuntu 12.04 LTS with NGINX 1.5.10 and SPDY v3.1. While implementing SPDY, I've seen web servers that are supporting multiple versions of the SPDY protocol. For an example you can see:
http://spdycheck.org/#google.com
http://spdycheck.org/#facebook.com
Obviously these are some of the biggest sites around, but I've looked for guidelines or documentation on how to support the different versions of the protocol, but there are no clear answers.
I'm not sure whether this is possible but any help or guidance as to how to achieve this would be much appreciated!
Thanks!
Alex
I've looked for guidelines or documentation on how to support the
different versions of the protocol, but there are no clear answers.
The answer is simple: don't, just use the latest version. Both Chrome and Firefox are aggressive about deprecating support for older versions -- e.g. expect spdy/v2 support to be removed in Q2/Q3 of 2014; IE should keep up as well.
If you want to track progress and watch out for announcements around new drafts or plans to deprecate old versions, sign up for spdy-dev mailing list.
It depends on which version of nginx you installed. The current version will install the current version of SPDY. SPDY 3.1 is in a module built for nginx.
You shouldn't have to do anything different to your code to support the different versions since this is a transport mechanism for the server.
Related
I have a development VM that's taking a lot of disk space. I am trying remove unused apps/tools. I just found out that I am keeping these old versions of Win10 and .NetCore SDKs. I'd like to know if it is ok to remove the old versions and keep the latest? I'm worried if it might encounter problems compiling my old projects. I would really appreciate your answer. Thanks.
I would like to know if we will be able to do security vulnerability, license and copyright scan using with sonatype nexus lifecycle for ruby gems?
I was not able to tun a trial version of IQ server due to licence requirements and see for myself. The free Application Health Check (AHC) seems to support only java based programs.
Please clarify.
IQ Server 1.35 introduced Lifecycle XC which has very basic support for RubyGems (and other formats that are not support by Sonatype yet), but that won't provide what you're looking for.
Recently announced IQ Server 1.46 enabled RubyGems support in Nexus Firewall. This might be good enough for what you're looking for.
However if you need RubyGems support in Nexus Lifecycle, then you have to wait for that.
We successfully setup the Meteor 0.7.1.2 in Centos. Is it Latest version supporting installation in windows 8 officially?. If yes please share the information.
we know its supporting unofficially with the following url
http://win.meteor.com
Thanks
Ramu
I agree about the cloud solutions. I've used the unofficial Windows version and had some problems, but I am loving cloud development with Meteor.
If you are interested in trying it out, I wrote up an entire tutorial on how to get set up with cloud development in Meteor and included a screencast.
http://simpleprogrammer.com/2014/10/13/getting-started-meteor-tutorial-cloud/
Windows support is not yet official and win.meteor.com outlines some workarounds, the better ones which include utilizing a virtual machine. There is a suggested native solution (launchmeteor.exe), although unofficial, with key difference (for some developers) being Meteorite not work on Windows yet.
According to the roadmap trello board https://trello.com/c/ZMvnfMfI/11-official-windows-support official windows support is targeted for 1.0 if time permits, but it seems very unlikely.
For interim portability, you may want to have a look at cloud solutions like nitrous.io at http://help.nitrous.io/meteor-app/ which runs the dev environment on the cloud but has a windows desktop app http://blog.nitrous.io/2014/02/25/nitrous-desktop-is-now-available-for-windows.html which at least lets you develop locally and sync to your nitrous.io cloud box.
We've recently had several hacks on our one server. We've been advised to upgrade all scripts. The problem is, the Drupal installations. Upgrading these are a massive task. I would like to know, out of fellow Drupal users, in your experience, how unsafe is it to remain on a say version 6.10 as apposed to upgrading 6.28 (the latest)? Is there a point at which you can say: this is really too old now and an upgrade is absolutely necessary?
I'm not too worried about the modules, my concern is the Core Drupal installation. Does it ever become a security risk, or can you stay on the older versions?
"Upgrading these are a massive task"
Not necessarily! I find using git a pretty safe way to deal with such upgrades.
My basic workflow is usually to:
- create a repository with the current Drupal version.
- download the latest core version
- rsync the current version with the latest core version
- update the repository
As expected, I do all of the above on my local version, after checking that everything is working fine. I update the remote repository, then update the actual live site from git.
If you're not familiar with git, basic tutorials are easy to find online. The idea here is not to explain the process in details, rather to send you in the right direction. You will find that it's a pretty flexible workflow, a great way to update modules and generally any type of code.
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
Starting a new project. It's basically a blogging/commenting system.
We're considering node.js as the back end server. Is node.js ready for this sort of thing or is it too early and experimental?
We need HTTPS and gzip compression - perhaps a front end nginx server could provide this?
What's missing from node.js that would make developing a web app difficult?
From a production ready perspective, we're wondering if it is stable enough for building a commercial app on top of.
Thanks
UPDATE:
Almost a year has passed and now I'd definitely use node.js for live systems.
It's not ready. It sure is an awesome piece of software but it's not suitable for production use yet.
The developer of node.js himself stated in a talk, that it's probably full of bugs and security issues.
This is the talk: http://www.yuiblog.com/blog/2010/05/20/video-dahl/
He recommends that IF it is to be used in a production environment, you should place it behind a stable http proxy like nginx but he discourages doing that at all.
I'll wait for a production release and until then, play with it on my local machine.
Node.js is really great. But it's complicated for a production use now. Actually, the API change several times in each version and can be change again a lot of time. So you need fix to a particular version. The migration can be painful.
I'm using it for a production site. It's been live for a few months and I've had no issues with the node runtime. Stick with the latest stable release (currently 0.2.6).
The 3rd party modules written by the community are where you may run into issues. Some modules are more stable than others. The node community has standardized on github, so it's pretty easy to fork and fix things you run into. But be prepared to roll up your sleeves and hack -- it's probable that you'll need to fix a few bugs in the modules you use.
Overall I've been happy using node.js
It's just another tool, with different pros and cons. If your project is planned carefully you shouldn't run into major problems. Node.js is a very active project and it shouldn't be long before it reaches stable. If your team finally decides to use node.js please contribute any findings / solutions / code or any kind of valuable information back to the community while you're at it. That would really help. The more people active, the faster node.js will progress.
It's still got some rough edges, but I'd say it's ready to use (I'm about to launch a production site based on it). Here's an article describing how 3 companies are using it in production.
You may still find yourself finding/fixing the occasional bug, but that's where the community really shines.
(Updated answer) On June 2013 (version 0.10.12):
Node.js is ready for production, it's stable and really fast.
I am using it on live servers with Redis, using a SmartOS VM with dtrace and flamegraph for profiling (on a dev server). It also replaced quite well my Apache/PHP stack for creating websites.
The best ways to find up-to-date modules are Nipster and npmjs.
As some modules are not mature enough, finding the right one is sometimes an iterative process.
--
(Old answer) On May 2012 (version 0.6.18):
Node.js and its API seems stable enough for production use.
However, its ecosystem isn't: most modules are not stable yet and a lot of them aren't maintained anymore (last commits from 8 to 18 months - you can check on the github pages of modules)
Currently, using a module often require an active participation: subscribing to its mailing list and patch it when needed.