Jonathon, I think we're all familiar with the issues CF has caused with the Chrome browser, but I noticed this evening, I had to clear my Firefox cache before I could log into the forums. I admit I am running Mozilla's Nightly builds, but I've been doing that for years and today is the first time I've ever had a caching/cookie problem here. It always seemed Rocketscript was causing most of those problems with Chrome, but there were problems, to be sure.That being said, let me know if you encounter any bugs or oddities while navigating around the forum here.
It's a bit like the conversation we were having about using Memcached. Without being able to see real-world data, I am pretty skeptical about adding anything. You'll doubtless recall how I was even reluctant about using LiteSpeed, aye? (LiteSpeed is still exceeding my expectations, BTW.) It really would be nice to see some numbers from this site, before and after Railgun.Just for the record, I haven't noticed a huge speed boost here before and after Railgun, but it's also important to note that our forum has been optimized to death to be speedy.
1) I don't know if our CF will be able to "stack" on top of this or not. I wouldn't imagine so. To get the railgun benefits the domains would have to be setup through our API key and then likely managed directly through cloudflare.com. Honestly though, we won't know how this will work without trying it.1) What if I am already a CloudFlare certified partner and offer CF via my clients cPanel via my VPS(or more)?
2) What if we are already hosting our sites via CloudFlare Pro and (+)
3) If we are reselling your VPS and offering shared hosting via your VPS ... will we have the ability to promote RailGun in our Marketing Material? Of course, we have to actively market CloudFlare AND we are already reselling your services.
Yes , It's better to wait 2 / 3 days until all the forum data is cached before you can do any real tests. If a file / pic or whatever is being requested many times CF CDN servers will cache it automatically. Just give it some time to do it's thing.It's very possible that I was testing prior to the Railgun cached data having synced out to all of the Cloudflare edge nodes.
That actually makes complete sense. That is exactly what I was looking to make sense of. It was something I was going to implement for shared users.. although, if it is all tying in to your API and for the sake of all legalities.. I may remove it from my cpanel and simply market things differently. It's still early in my process and I haven't begun my campaign.. so this is ok.. besides.. I still need to purchase another VPS from you.The cPanel plugin isn't compatible with VPSs/Dedis because it's all tied to our API key - which isn't supposed to be shared or given out like that. Shared hosting customers for example can use the cPanel plugin, but VPSs/Dedis will work based on us whitelisting IP ranges and then they can activate Railgun directly on cloudflare.com or if we potentially make a control panel for Cloudflare using their API that ties into our billing system then that option will be available. At the beginning it will simply be us whitelisting IP addresses and you being able to activate it at cloudflare.com.