If you want to work towards feeling better each day, MyMoodTracker can help get you there. Features: - Guidance for over 50 different situations, from castles to rainbows and. Equipment tips, camera settings, creative suggestions and technical points for over 50 categories of photography subjects, covering practically anything you will ever point your camera at. Keeping track of how you are feeling is an important step in improving your mental health and well being. PhotoCaddy is the photography expert you can carry in your pocket. If you want something added, we'll do our best to accommodate. Hourly, daily, weekly, monthly and yearly charts of everything you've entered

Comprehensive reminder system, no more gaps in your history Track many items to see how they affect your mood, including sleep, exercise, medication, menstrual cycles, stress, pain, energy and stimulants Track mood and emotional state throughout the day The fun yet powerful design will help you understand what causes your emotions to change, and get you on the path to feeling good.

The perfect companion for tracking your moods and emotions, and everything else that can affect how you feel. If using my example paths create with your favourite editor /data/caddy/Caddyfile.Best Health App 2011 - 2nd Place.

I am using the following, you should be able to create the same, updating with your domains and email. Create a CaddyfileĪ Caddyfile is structured to have blocks for global settings, snippets, and server. data/caddy/Caddyfile:/etc/caddy/CaddyfileĬaddy will function with only the Caddyfile volume mapped, and is fine for testing, but having the optional data and config volumes separated allows externalising of some key files, for backup or consistency when upgrading the core container image. With your favourite text editor, create & open docker-compose.yml and seed with this. I also typically keep my Docker Compose control file in the same place as the 'head vampire' container, in this case Caddy.

/data/caddy/config : JSON config files (optional) - directoryĬreate some directories $ sudo mkdir /data.

/data/caddy/data : the house for certificates (optional) - directory.

/data/caddy/Caddyfile : the centre of the universe - file.

/data/caddy : the Caddy and Compose root - directory.

Wherever you see /data/caddy, replace with your own core directory. I normally keep all my docker stuff under custom directory /data, but it's up to you.

Optional - an IP whitelist on your cloud server so only you can access the test application.

I have separate domains for the server (SSH, SFTP) and the web site itself.

A domain name or subdomain name you can point to the VPS public IP address.

At the time of writing the latest stable used here is 1.29.2.

A running docker compose environment, built as per this then this great DigitalOcean article.

An AWS Lightsail $5 VPS with 1GB memory (if using, add HTTPS to the firewall).

Variations on this environment might work but this is what works here. Most VPS's (Virtual Private Server) will do, I have my farm in the same place, I find it a fair deal for the included bandwidth and like having the vast AWS infrastructure nearby should I want to make use of it. I am using a $5 AWS Lightsail server in the Frankfurt region. Incidentally, this is my first outing making use of the excellent for my diagram, with a cool sketch library from Rough-JS.

A cloud test server and less than an hour later, it was up and running. In fact, it was while digging around for even a simple example of Traefik V2 with Docker Compose + HTTPS that I found a blogger - also struggling to get it going - who wrote the fateful words, 'discovered caddy, seems simpler'. The tech road was meandering in a wildly zig zag way. The config and syntax complexities were dragging me down, and there weren't really many resources or HTTPS examples online. While Traefik is very cool and a great community, I had been beating my head against the wall trying to get a really basic running model of their new version 2 up and running. Reverse proxy, routing, https, open source, container based, easy to use. It's another proxy application like Traefik that ticks all the boxes. You'll easily be able to replace the Ghost back end with other container-based apps such as Nginx or Wordpress.Īs a longtime user of Traefik, I was pleasantly surprised when I tripped over Caddy. I'm building a Caddy-stack to serve up HTTPS sessions, with a Ghost back end, using Docker containers, orchestrated with Docker Compose.

Photocaddy backup