Depending on where you purchase SSL certificate, I pick namecheap. I don't have any reason for it, but they are as reliable as it could be. GoDaddy, to me, is okay--they tend to have lower renewal cost for domain too. Back to SSL certificate, you need to generate a CSR (Certificate Signing Request) to ask for SSL. I'm using openSSL.
Depending on where you purchase SSL certificate, I pick namecheap. I don't have any reason for it, but they are as reliable as it could be. GoDaddy, to me, is okay--they tend to have lower renewal cost for domain too. Back to SSL certificate, you need to generate a CSR (Certificate Signing Request) to ask for SSL. I'm using openSSL.
State or Province Name (full name) [Some-State]: NH
State or Province Name (full name) [Some-State]: NH
Locality Name (eg, city) []: Atkinson
Locality Name (eg, city) []: Atkinson
Organization Name (eg, company) [Internet Widgits Pty Ltd]: 10ninox Ltd
Organization Name (eg, company) [Internet Widgits Pty Ltd]: 10ninox Ltd
Organizational Unit Name (eg, section) []:
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []: 10ninox.com
Common Name (eg, YOUR name) []: 10ninox.com
Email Address []:
Email Address []:
A challenge password []:
A challenge password []:
An optional company name []:
An optional company name []:
Some fields can be left blank, but you pretty much like to answer all for your own credential. The thing is you <strong>should leave challenge password empty</strong>, otherwise, you will have to type that every time your Nginx reload or restart. Then you get 2 file <code>mywhatever.key</code> and <code>whatever.csr</code>
Some fields can be left blank, but you pretty much like to answer all for your own credential. The thing is you <strong>should leave challenge password empty</strong>, otherwise, you will have to type that every time your Nginx reload or restart. Then you get 2 file <code>mywhatever.key</code> and <code>whatever.csr</code>
@ -52,23 +52,23 @@ Now you have to extract <code>your_site.zip</code> which contains several files
Merge those files into one, <code>10ninox-ssl-bundle.csr</code> or whatever name you want.
Merge those files into one, <code>10ninox-ssl-bundle.csr</code> or whatever name you want.
Then copy the bundle file and <code>mywhatever.key</code> we got earlier to a directory in your server; location is up to you. There is no restricted whatsoever. The last process is to setup Nginx to know where SSL certificate is in Nginx virtualhost file (likely to be <code>/etc/nginx/sites-available/10ninox.com</code> for Debian)
Then copy the bundle file and <code>mywhatever.key</code> we got earlier to a directory in your server; location is up to you. There is no restricted whatsoever. The last process is to setup Nginx to know where SSL certificate is in Nginx virtualhost file (likely to be <code>/etc/nginx/sites-available/10ninox.com</code> for Debian)
The change arrived. __10ninox blog__ now has turned into pretty minimal web pages. It is a bit harder on user's side since there is nothing such as tag link, month page, search, and so on, but posts remain the same: URL, content.
10ninox's blog was started by using WordPress, but over the past years, I haven't been actively blogging and I'm doing a lot more on coding side. Consequently, I figured out that I should have just turned the blog into an easier and cheaper process on my part. Nowadays, I prefered doing anything in text file; working in terminal; pushing stuffs from there to logging in to WordPress--previewing and publishing from there. [Jekyll](http://jekyllrb.com/) was one of the obvious choices as far as Google's results are concerned. Don't ask me why I pick Jekyll over anything since I do not know if there is anything better. I did try to find Jekyll alternative in Python, but have yet to find anything better. Jekyll is okay with markdown and I'm comfortable with it. Since I do not code in Ruby, I am seemingly blind to configure in any way, but basic. Hopefully, one day, I get around to work on that, but so far, this works with only nginx and cheap VM. I couldn't be happier.
Thanks to [Jekyll](http://jekyllrb.com/), [Disqus](http://disqus.com), [git](http://www.git-scm.com/), and [nginx](http://nginx.org/) to make this possible.