Tag Info

New answers tagged

3

Using /dev/random is meant to be reserved for things which truly need to be cryptographically secure, such as private key material, because it relies on an entropy pool which can be depleted rapidly if the RNG is overused. Unless for some reason you think the NSA might want to influence the results of your card games? So /dev/urandom, a PRNG which never ...


1

Since you're dealing with Drupal many parts of your website configuration will not just live in code. This has been solved many times before, but I don't think it has ever been solved once and for all. There will be pain. You can ease this pain by ensuring that developers are putting as much as possible in code, through Features and custom Drupal modules, ...


0

For starters, I would strongly recommend paying for a 3rd-party DNS provider that's independent of any hosting/email/Internet services; I typically use them for the domain registrar as well because it's a convenient to renew both simultaneously and there's usually a discount for having both. It will cost more (~$25-50 USD per year, which is really nothing ...


1

EDIT: Moving your customer's web hosting service has nothing to do with their email service. As long as the destination of the MX record is not changing, nothing will happen to their email delivery. Just change the A records for their web site. It is good practice to reduce the TTL on the records as described in other posts or in my original response. ...


0

There will be no "downtime". What you'll need to do is think about how you're going to sync all the mail over. This can always be done afterwards.


1

What you describe is not possible without doing some extra work. You can achieve this in two ways Configuring Tomcat's HTTP connector in server.xml to listen on port 80 and configure your app to run in the ROOT context. Add an Apache HTTPD (or NGINX if that suits your taste) reverse proxy which listens on port 80 and connects locally to your Tomcat ...


1

DNS translates host names to IP addresses only. It cannot forward ports or URLs. The simplest solution would be to run the application on your server on port 80 and run in the ROOT context. Make the home page one of the defaults or override it as defined in the Tomcat FAQs. Your domain provider generally provides basic DNS services and you should be able ...


1

If the server of your client has a public (dynamic?) IP address, you need to sign up with a dyndns service like no-ip or dyn. Since the IP address is likely to change every day, a (sub-)domain has to be pointed to that IP everytime it changes. The dyndns service does that for you. All you have to do is ping the service once the IP address changed, so the ...


1

If you want to have this installation externally visible then there are two things you'll want to do: Create a DNS record to point to the IP of the server - this will allow your visitors to access the server via http://docs.example.com/ Configure your webserver such that you don't need to use the external port. If you were using Apache I'd suggest you ...



Top 50 recent answers are included