When I have installed a Zend-Server in a Openshift gear, I have notice that indicates me the Zend Server Licence will expire in 7 days. Is this managed by Openshift or I have to buy a licence after 7 days?
Quoting from Zend Server 6.1 and PHP 5.4 Cloud Hosting OpenShift blog:
License Edition
Enterprise Edition license
Zend Server 6.1 cartridge comes with 7-days free Enterprise Trial
license when instantiated. Users can extend the Enterprise Trial
license for another 21 days by registering the Zend Server instance or
switch to their already purchased license.
Free Edition license
Once the Enterprise Trial license expires and Zend Server process gets
restarted, the application code continues to run with Zend Server now
running in Free Edition. This edition is still perfectly suited for
development environments but lacks features designed for production
environments, such as extended data retention, Page Caching, Job
Queue, and auto-generated root cause analysis.
See this comparison of Zend Server Editions for more details.
According to this page: http://www.zend.com/products/server/license/product?edition=FREE
**
Sorry, Zend Server Free Edition is no longer available.
**
Be aware that, unless you are a RedHat employee working on this problem, you cannot see any of the details for any of these bug reports, so there is no way to know if there has been any progress - from the Zend Forums, it looks like this has been a problem for years and has never been fixed.
Bug 1120132 - There is no way to acquire a new Zend Server 6 license when the Enterprise Trial expired
Bug 1120103 - Failed to redirect to the login page or update license page after cancelled the update license on the first time when the Enterprise Trial license expired
https://bugzilla.redhat.com/show_bug.cgi?id=1120132
So, an answer to this question seems impossible to obtain from those responsible for perpetrating it. It looks to be impossible to migrate from the trial licence to the free edition. This could be down to a design fault in the Zend ecosystem - it might never work and there seems to be no recourse for the user hit by this.
According to this page, to uninstall Zend Server, you make sure it's not running and simply delete it.
This is something we're aware of and are working on a fix, take a look at this BZ for more information https://bugzilla.redhat.com/show_bug.cgi?id=1120132.
Related
I just registered a hosting service from www.amhosting.com and they said that the Server support MySQL and .Net 3.0 only while the site I am installing is DNN 7 which is running with MSSQL and .Net 4.0.
So what is the solution for this case?
Could I run DNN 7 in .net 3.0 environment?
or should I downgrade the DNN to lower version that is able to run in .net 3.0?
How to configure the DNN site to run with MySQL?
Thanks a lot.
Cheers,
Timmy
I think you should change your hosting solution.
From what I know DNN7 only works with .NET 4.0 / 4.5
MySql - god forbid, you're in a world of pain. I have heard about attempts to make the DNN Core compatible with MySql... but it's only the Core, and any such projects would be outdated in a matter of months, as DNN does release quite often.
Talking about third party modules, which sooner or later you'll be bound to download from codeplex or buy from Dnn store - forget about. no dnn developer out there provides scripts for mysql.
Good luck!
As Greg states, you won't have an easy time getting DNN working in 2.0 (there was no 3.0, but 3.5 exists) with MYSQL, and you will be limited based on the "provider" for MYSQL.
Go with another hosting company that does Windows Hosting with MSSQL options, there are plenty of them out there for low cost, you'll save a lot more money changing hosting, than you will trying to get mysql working with DNN, and you won't have any upgrade options available to you.
i am currently building a website around a couchbase database and if it gets popular it is likely that i will be hosting the site and database on more than 2 machines at some stage in the future. its a fair way off still, so i would like some information to help me decide which direction to go from here. my questions are:
does anybody know if i am allowed to deploy the free edition (ce) of couchbase on more than 2 nodes? if the answer varies depending on the version then please could you tell me which version permits this (if any).
if it is not possible to deploy the the free version of couchbase on more than 2 nodes then could someone explain whether this is prevented by software, or by law?
i found the following statement on the couchbase website:
Community Edition (CE) are best for non-commercial developers, where
taking some time to figure out or resolve issues doesn’t result in
major problems. There are no constraints on using these binaries on
production systems
which makes it sound like the software can be installed on as many machines as desired in production without a requirement to pay, but then another couchbase page reads:
Looking for the free version? Our Enterprise Edition Free version
offers the full functionality of Couchbase Server, with free unlimited
use in development and up to two nodes in a production cluster.
so i'm confused. maybe this last one is just referring to the cost of support and not any cost associated with the software itself?
You can deploy Community Edition on 2 nodes and more. Restrictions exist only for Enterprise Edition:
http://www.couchbase.com/couchbase-support
If you hover over the "Why Enterprise" or "Why Community" link on the download page, you get the details:
Community Edition:
Choose Community Edition if you're working non-commercial projects:
For enthusiasts able to resolve issues independently
Untested binaries that do not include the latest EE bug fixes
No constraints on using binaries on production systems
Help available from the Couchbase user community
So you can use the Community Edition without constraints on an unlimited number of nodes in production or for development.
Enterprise Edition:
Choose Enterprise Edition if you're working on funded project, here's why:
Rigorously tested, production-ready release with latest bug fixes
Free for testing and development for any number of nodes
Free for production up to two nodes
Annual subscription available, includes support and hot-fixes
The Free Enterprise Edition constraints are what is referred to in the table referenced in one of the other answers in the "Free" Collumn: http://www.couchbase.com/couchbase-support.
The packages also have the license files describing the binary licenses.
And of course the source code for Couchbase Server is open, under Apache 2.0 license.
These are two different versions, Community Edition vs Enterprise Edition. CE is free to be deployed on as many as you want to, But with Forums only Support vs Enterprise is free for up to 2 nodes in production.
That said, if your data is mission critical to you or your clients, The recommendation is to migrate to the Enterprise edition. If your application can be supported by forums help only, there is no need to move from your CE Couchbase Server.
I've read through a number of pages detailing the version differences between the different MySQL versions, but none of them have given me a real clear picture as to what is best for the application I am making. I'm in the process of building a CRM which will handle 20,000 customers at launch and built on a LAMP stack. The OS will either be CentOS or FreeBSD.
Right now for test purposes we've been using a MySQL 5.0 server for the database, but we are wondering which version we should use for production. If anyone could give some thoughts as to the pros and cons of using 5.0 vs 5.1 vs 5.5 vs 5.6 in the context of a CRM application, it would be most appreciated.
TL;DR 5.5
For a new software rollout, it makes sense to integrate and do final testing with the latest generally available (GA) release of your infrastructure components.
Right now that's 5.5.20 of the MySQL community server. 5.6.x is considered a development release. It probably doesn't make sense for you to try to do integration and final testing with such a release, unless it offers a new feature that's a critical success factor for your new software. (But then you should ask yourself whether it makes sense to make your product dependent on exotic new features in unfinished dbms releases.)
EDIT... #rkosegi has a good point. If you're going to deploy on an enterprise grade linux server distro like Red Hat Enterprise Linux (rhel) use the version it supports. 5.1 works fine.
I think better you should use v5.1.XX because it's in active development state and stable too.
MySQL has stopped working on v5.0 i guess extend support also will expire soon.
http://dev.mysql.com/doc/refman/5.0/en/
This is my first question so play nice!!! I've done a search and could only find similar questions relating to .NET 3.5 last year so I thought I'd ask for people's recommendations at this point in time regarding a good web host to use for a small e-commerce website that will run on .NET 4.0 with a SQL Server 2008 back end.
Opinions on hosts seem to change daily as do their offers and the technology that they support so I'd love to hear what people are using at this time and how they're getting on. I generally run everything through GoDaddy but their Shared hosting packages only support SQL Server 2005 at the moment, I called them and to get access to a SQL Server 2008 database you have to go down the Virtual Server route which will cost too much for this project.
Thanks in advance!
I went with WinHost in the end and am now up and running. Setup, at least was faultless. http://www.winhost.com/windows-hosting-plans.aspx
Not that it's a prerequisite for commenting here, but I'd like to pick the brain of someone that's taken their Reporting Services platform from 2000 to 2008 (skipping right over 2005).
The architecture between 2000 and 2005 (so thus between 2000 and 2008 also) changed significantly it seems, so I'd like to know what needs to be done (before,during,after) the process of taking my rs2000 install (installed on a web server running IIS 5, connecting to a remote sql server 2000 box that hosts the ReportServer/ReportServerTempDB databases) and converting it to SQL208 - where, from the looks of it, is hosted in some sort of it's own native hosting engine, no IIS needed (is that right?).
I've used this tool before, but only for moving stuff between 2 rs2000 databases. I'm curious if it works between 2000 and 2008. I've also been reading on TechNet and MSDN about some kind of "upgrade advisor" and "upgrade wizard" - but I remember what the VB6 to VB.NET Wizard was like, so I'm a little skeptical of a wizard that proclaims to help migrate stuff between 2 architecturally different versions of a product.
Disclaimer: I am not a Reporting Services (or SQL Server) admin. Just the guy on the team most familiar with installing/supporting the tool, so I'm stuck being responsible for this migration too - though I'm a veteran developer, not totally clueless.
Be aware, there is no anonymous mode in SRS 2008, you should use Active Directory / Kerberos / Windows authentication or use your own authentication module.
In SRS2008 you've got feature like Tablix/Matrix which are really usefull, maybe you can make some optimizations into your old reports.