This simple docker setup allows you to access a domain via https which is internally proxied to your localhost at a specific port number
For example, you can access:
https://local.kultmedia.com
and see the content that is being served by:
http://localhost:7008
This can be useful when using tools like Resource Override to avoid CORS errors and other SSL issues
The project uses some variables that can be customized inside Dockerfile.
Here is the recap:
| Variable Name | Description | Default value |
|---|---|---|
| CUSTOM_PORT | This is the port where your localhost service is running | 7008 |
| CUSTOM_DOMAIN | This is the domain that you will access via https | local.kultmedia.com |
To have https working correctly, you will need to generate the certificates from your machine
- Install mkcert on your machine
- Run
mkcert -install - Now move into the
certsfolder of this project - Run
mkcert local.kultmedia.com(if you customized the domain, use your custom one) - If the command worked correctly you should have two new files:
local.kultmedia.com.pemlocal.kultmedia.com-key.pem
- If, for some reasons, the two files are not named like this, rename them as above
- In case you customized the domain, the certificates need to be renamed accordingly
- Make sure that Docker is installed and running
- Run with
docker-compose up --build
- Launch the service running at port 7008
- Now access https://local.kultmedia.com
If you use the default domain (local.kultmedia.com) you don't need to do anything else, since this domain is already pointing to localhost. However, if you want to use a custom domain, you also need to make sure that this domain resolves locally to localhost. In macOS this is done by editing the hosts file:
sudo nano /etc/hosts
Now, assuming that your domain is dummydomain.local.dev, add this line:
127.0.0.1 dummydomain.local.dev
Make sure to save the file. Now the domain will resolve to localhost.