This object is in archive!
Development and Production Server License?
Just purchased Corporate for our client, have UR setup right now on our DEV server, and so in the URL field I have help.dev.domain.com. Thing is, I do not see any space to actually specify both a DEV and PROD server URL. I will need to run it on help.domain.com when it goes live of course. How do I handle that? Does my DEV environment simply become invalid at that time? That is not exactly the best way to work.
So what I need to know is, how can I run UR on both our DEV and PROD servers?
Thanks,
Ken
Hello Ken,
One installation can't be opened in different URLs because of 2 limitations:
So if you open community on another URL, it will fail. Also we don't understand why it's required to open 1 instance in 2 URLS
Hello Ken,
One installation can't be opened in different URLs because of 2 limitations:
So if you open community on another URL, it will fail. Also we don't understand why it's required to open 1 instance in 2 URLS
Hello Ken,
One installation can't be opened in different URLs because of 2 limitations:
So if you open community on another URL, it will fail. Also we don't understand why it's required to open 1 instance in 2 URLS
Hello Ken,
One installation can't be opened in different URLs because of 2 limitations:
So if you open community on another URL, it will fail. Also we don't understand why it's required to open 1 instance in 2 URLS
Hi Stas,
Okay, so I assume that when I need to move from development to production, I can just change the BaseURL option, and I assume I would need to then update the URL on the Licenses page and download a new key? Because right now I am developing it in our... development environment.
The way we work, and the way I have worked at different companies in the past, is that we have a development server, and a production server. Once something is pushed to production at the end of a sprint, quarter, or whatever the lifecycle is, then we do our development and testing in on the dev server until we push those changes live to production.
That is a pretty standard development lifecycle, isn't it? In this case, no we are not running two separate communities. We are running one community and we have a separate development server to work on.
Because of your limitation of only allowing for one URL, I would call that a Production URL, then if I want to make any changes or experiment with anything, I am forced to do that in a live environment that is being accessed by our users.
Does that make more sense now?
Hi Stas,
Okay, so I assume that when I need to move from development to production, I can just change the BaseURL option, and I assume I would need to then update the URL on the Licenses page and download a new key? Because right now I am developing it in our... development environment.
The way we work, and the way I have worked at different companies in the past, is that we have a development server, and a production server. Once something is pushed to production at the end of a sprint, quarter, or whatever the lifecycle is, then we do our development and testing in on the dev server until we push those changes live to production.
That is a pretty standard development lifecycle, isn't it? In this case, no we are not running two separate communities. We are running one community and we have a separate development server to work on.
Because of your limitation of only allowing for one URL, I would call that a Production URL, then if I want to make any changes or experiment with anything, I am forced to do that in a live environment that is being accessed by our users.
Does that make more sense now?
Hello Ken,
Yes, it makes more sense. With 3.0 you can do dev installation and live installation at different URLs. Just have 1 license.key generate for live URL.
When you push changes, just ignore /configs folder
Hello Ken,
Yes, it makes more sense. With 3.0 you can do dev installation and live installation at different URLs. Just have 1 license.key generate for live URL.
When you push changes, just ignore /configs folder
Hi Stas,
This sounds great! Thanks.
Ken
Hi Stas,
This sounds great! Thanks.
Ken
Replies have been locked on this page!