nitrc-ce
nitrc-ce > RE: Getting started with NITRC-CE
Apr 12, 2022 10:04 PM | David Cash
RE: Getting started with NITRC-CE
Hi Christian-
Thanks for your help, and that is helpful to know that if I run into this issue again (sounds like I probably won't), then there is a way to work around that.
Regarding local VM - waiting for the next release should probably work as I am developing and testing for a course in late July and can do some of that on the Cloud or with the one of the VMs available in the downloads. My goal with building one locally was to be flexible in case we didn't have the network bandwidth for everyone to be up in the cloud and people with sufficient compute on their laptops could then have a VM that they could use on their local machine instead. Ideally, I might try and shrink it down by reducing the number of packages installed (somewhere between the Classic and Full), but that is a secondary goal.
Thanks again for all of the help-
Dave
Originally posted by Christian Haselgrove:
Thanks for your help, and that is helpful to know that if I run into this issue again (sounds like I probably won't), then there is a way to work around that.
Regarding local VM - waiting for the next release should probably work as I am developing and testing for a course in late July and can do some of that on the Cloud or with the one of the VMs available in the downloads. My goal with building one locally was to be flexible in case we didn't have the network bandwidth for everyone to be up in the cloud and people with sufficient compute on their laptops could then have a VM that they could use on their local machine instead. Ideally, I might try and shrink it down by reducing the number of packages installed (somewhere between the Classic and Full), but that is a secondary goal.
Thanks again for all of the help-
Dave
Originally posted by Christian Haselgrove:
David,
Thanks for the explanation. I thought this was deep in the plumbing, and it was -- that was some impressive detective work on your part!
For what it's worth, the domain name is only a convenience that allows us to give you an HTTPS connection that works right from the start. If you point your browser to https://IP-ADDRESS/, the instance will certainly behave, but you'll have to tell your browser not to worry about the fact that there's no SSL certificate set up for the IP address.
We did find that we were running up against a quota for serving the certificates. Having changed that, you shouldn't have any trouble with this in the future. Of course, please do let us know if you run into problems.
Preparing a VM for you to use locally has proven more troublesome than I had expected. Is this something you need in fairly short order, or can it wait a few weeks until our next release?
Christian
Thanks for the explanation. I thought this was deep in the plumbing, and it was -- that was some impressive detective work on your part!
For what it's worth, the domain name is only a convenience that allows us to give you an HTTPS connection that works right from the start. If you point your browser to https://IP-ADDRESS/, the instance will certainly behave, but you'll have to tell your browser not to worry about the fact that there's no SSL certificate set up for the IP address.
We did find that we were running up against a quota for serving the certificates. Having changed that, you shouldn't have any trouble with this in the future. Of course, please do let us know if you run into problems.
Preparing a VM for you to use locally has proven more troublesome than I had expected. Is this something you need in fairly short order, or can it wait a few weeks until our next release?
Christian
Threaded View
| Title | Author | Date |
|---|---|---|
| David Cash | Mar 31, 2022 | |
| Christian Haselgrove | Apr 1, 2022 | |
| David Cash | Apr 4, 2022 | |
| David Cash | Apr 12, 2022 | |
| NITRC Moderator | Apr 12, 2022 | |
| David Cash | Apr 12, 2022 | |
| Christian Haselgrove | Apr 12, 2022 | |
| David Cash | Apr 12, 2022 | |