This object is in archive!
sandbox, developer licenses
It would be nice to have a sandbox where people would try how UR works and where they could experiment with it even after their trial expired. I purchased a license and we are in the process of setting it up and I would still appreciate it to see how certain things work without putting responses into a live system (ours or UR's)
Agree, we were thinking of dev licenses and will incorporate it after 2.1 release. As of now, we are concentrated on it to polish some of the features, tweak several modules and release new.As of now, there are several ways to use it:
- It can be installed on localhost/anydomain without problems;
- You can close your community from publicity with htpasswd.
Maybe you'll find more convenient way to use test environment, but later it will be more easy. Probably in the beginning of next year.
Update: Done
Agree, we were thinking of dev licenses and will incorporate it after 2.1 release. As of now, we are concentrated on it to polish some of the features, tweak several modules and release new.As of now, there are several ways to use it:
- It can be installed on localhost/anydomain without problems;
- You can close your community from publicity with htpasswd.
Maybe you'll find more convenient way to use test environment, but later it will be more easy. Probably in the beginning of next year.
Update: Done
Hey Stas.
So just to clarify on this point: if we purchase either the Standard or the Enterprise license - will we be able to run UseResponse BOTH on our production site (support.production-domain.com) and our dev site (support.dev-domain.com)?
Because of our testing requirements we run dev and prod on different actual domains.
Thanks!
Dan
Hey Stas.
So just to clarify on this point: if we purchase either the Standard or the Enterprise license - will we be able to run UseResponse BOTH on our production site (support.production-domain.com) and our dev site (support.dev-domain.com)?
Because of our testing requirements we run dev and prod on different actual domains.
Thanks!
Dan
Hi Dan,
There are 3 options available at this moment:
In general, your live and dev servers should have the same instance that will be contained inside url like: "production" for both and your dev can be dev.production and live will be production.com
Hi Dan,
There are 3 options available at this moment:
In general, your live and dev servers should have the same instance that will be contained inside url like: "production" for both and your dev can be dev.production and live will be production.com
Agree, we were thinking of dev licenses and will incorporate it after 2.1 release. As of now, we are concentrated on it to polish some of the features, tweak several modules and release new.As of now, there are several ways to use it:
- It can be installed on localhost/anydomain without problems;
- You can close your community from publicity with htpasswd.
Maybe you'll find more convenient way to use test environment, but later it will be more easy. Probably in the beginning of next year.
Update: Done
Agree, we were thinking of dev licenses and will incorporate it after 2.1 release. As of now, we are concentrated on it to polish some of the features, tweak several modules and release new.As of now, there are several ways to use it:
- It can be installed on localhost/anydomain without problems;
- You can close your community from publicity with htpasswd.
Maybe you'll find more convenient way to use test environment, but later it will be more easy. Probably in the beginning of next year.
Update: Done
What if I'm hosting this on servers that are only accessible to our company? We plan on using it to create a community support tool for our internal users. How does this change things from a licensing and domain perspective?
What if I'm hosting this on servers that are only accessible to our company? We plan on using it to create a community support tool for our internal users. How does this change things from a licensing and domain perspective?
Hello Scott,
With 1 license you can install and use system on 1 url/domain, no matter if it's public or private community. Developer license could be used for development purposes on any domains.
So in your case there are no problems in using 1 license for private community
Hello Scott,
With 1 license you can install and use system on 1 url/domain, no matter if it's public or private community. Developer license could be used for development purposes on any domains.
So in your case there are no problems in using 1 license for private community
Replies have been locked on this page!