Generate and Use SSL Cert in Windows

Raj Kishor — Thu, 30 Nov 2023 13:11:29 +0000

Creating a Self-Signed SSL Certificate

There is two types of SSL certificates

Self-signed: generated by user to use in testing/local environments.
CA signed: generated and signed by CAs (Certificate authorities) to used in production environments.

To generate the self signed SSL Certificate follow these steps as below:

Generate a Private Key
Create a CSR ( certificate signing request) using the private key.
Generate the SSL certification from CSR

Windows

Step 1 – Download OpenSSL Binary Link

Step 2 - Open OpenSSL Command Prompt

Step 3 - Generate private key and certificate signing request

A private key and certificate signing request are required to create an SSL certificate.

These can be generated with a few simple commands.

When the openssl req command asks for a “challenge password”, just press return, leaving the password empty. Since this is a self-signed certificate.
This password is used by Certificate Authorities to authenticate the certificate owner when they want to revoke their certificate.

$ openssl genrsa -aes256 -passout pass:gsahdg -out server.pass.key 4096
...

$ openssl rsa -passin pass:gsahdg -in server.pass.key -out server.key

$ openssl req -new -key server.key -out server.csr

...
Country Name (2 letter code) [AU]:US
State or Province Name (full name) [Some-State]:California
...
A challenge password []:
...

Step 4 - Generate SSL certificate

The self-signed SSL certificate is generated from the server.key private key and server.csr files

$ openssl x509 -req -sha256 -days 365 -in server.csr -signkey server.key -out server.crt

The server.crt file is your site certificate suitable for use with hosted website along with the server.key private key.

Reference: https://devcenter.heroku.com/articles/ssl-certificate-self#generate-private-key-and-certificate-signing-request

Ember upgrade v3.x to 4.x

Raj Kishor — Sat, 18 Mar 2023 20:08:30 +0000

A dev journey of Ember upgrade from v3.20 to 4.8

Every aspiring dev journey starts from documentation, a bunch of documentations.

Upgrade guide:

Deprecation guide:

https://deprecations.emberjs.com

Release guide:

https://blog.emberjs.com/tag/releases

RFCs guide: Checkout to know more about behind the curtain of a deprecation

https://rfcs.emberjs.com/#accepted

Upgrading a project is very ambitious task, and like every ambitious task let's break into small tasks.

Upgrade Plan

Sequential upgrade LTS wise.
Handle deprecation of only upgraded LTS.

How to upgrade?

Step 1: Upgrade ember-cli [as eg. 3.24.0 to 3.28.0]

  $ npm install -g ember-cli-update

  $ npm uninstall -g ember-cli
  $ npm install -g ember-cli@3.28.0
  $ ember --version

Step 2: Navigate to project path in terminal

$ cd <project-path>
$ ember-cli-update --to 3.28.0

This will update the project to the mentioned Ember CLI version. It will only modify the files if there are changes between your project's version and the latest version, and it will only change the section necessary, not the entire file.

You will probably encounter merge conflicts, in which the default behavior is to let you resolve conflicts on your own.

Step 3: Run your project to checkout any breakage [Project dependant]

Project third party packages can be upgraded while or even after upgrade of ember-cli, depends on project and type of breakage.

Detailed Ref: https://cli.emberjs.com/release/basic-use/upgrading

How to handle deprecation?
Step 1: Install ember-cli-deprecation-workflow in project

$ npm install ember-cli-deprecation-workflow --dev

Step 2: create config/deprecation-workflow.js
Step 3: Add deprecation message entries as per documentation

Dev note: Handling and maintenance of deprecation in large project becomes tedious, this is how I handled one deprecation/version-wise at a time.
Github link: https://github.com/rajforum/ember-upgrade-note/blob/main/deprecation-wokflow.js

Change handler to log to list deprecations and throw once fixed.

TLDR tip:

There are codemods which reduce repetitive bulky changes.
- https://github.com/orgs/ember-codemods/repositories
- https://github.com/dyfactor/dyfactor-plugin-disambiguate-locals
If you're jumping from 3.x to 4.x as 4.0.0 is not an LTS candidate even-though I would suggest to have 4.0.0 as internal-upgrade which handle all v3x deprecations.

A mention to other Refs which has helpful at very first upgrade.

DEV Community: Raj Kishor

Generate and Use SSL Cert in Windows

Creating a Self-Signed SSL Certificate

Windows

Ember upgrade v3.x to 4.x