Skip to content

Conversation

@repli2dev
Copy link

Clarify configuration of click tracking with default Caddy configuration

Clarify configuration of click tracking with default Caddy configuration
@repli2dev
Copy link
Author

I struggled a bit to figure out the info in Tracking domain setup in Postal UI that says that adding CNAME will do it (it did not) and this page that provided only extensive info about fully custom configuration.

Copy link
Contributor

@willpower232 willpower232 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some ideas, let me know what you think

1. Adding CNAME record for `click.yourdomain.com` to previously configured `track.postal.example.com` followed by Caddy additional configuration.
2. Configuring custom proxy for `click.yourdomain.com` on your webserver.

Then you need to configure particular Postal service :
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think using the word service confuses things a little, maybe move this after your block of text below so the original If you're happy things are working, you can enable tracking as follows: is back above this list

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to say that you add it in Postal UI to particular sending service, not sure about the terminology 🙏

$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bd788587e651 caddy "caddy run --config …" 2 weeks ago Up 2 weeks postal-caddy
$ docker restart bd788587e651

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe you can just do docker restart postal-caddy instead of grabbing the container ID

Comment on lines +38 to +44
After saving this new configuration restart Caddy:
```
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bd788587e651 caddy "caddy run --config …" 2 weeks ago Up 2 weeks postal-caddy
$ docker restart bd788587e651
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah good point @deanpcmad, anything against this @repli2dev?

Suggested change
After saving this new configuration restart Caddy:
```
$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bd788587e651 caddy "caddy run --config …" 2 weeks ago Up 2 weeks postal-caddy
$ docker restart bd788587e651
```
After saving this new configuration restart Caddy, for example if you're using docker, you may be able to `docker restart caddy`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants