Maintenance: update lib catex

.dockerignore

@@ -0,0 +1,45 @@
+# This file excludes paths from the Docker build context.
+#
+# By default, Docker's build context includes all files (and folders) in the
+# current directory. Even if a file isn't copied into the container it is still sent to
+# the Docker daemon.
+#
+# There are multiple reasons to exclude files from the build context:
+#
+# 1. Prevent nested folders from being copied into the container (ex: exclude
+#    /assets/node_modules when copying /assets)
+# 2. Reduce the size of the build context and improve build time (ex. /build, /deps, /doc)
+# 3. Avoid sending files containing sensitive information
+#
+# More information on using .dockerignore is available here:
+# https://docs.docker.com/engine/reference/builder/#dockerignore-file
+
+.dockerignore
+
+# Ignore git, but keep git HEAD and refs to access current commit hash if needed:
+#
+# $ cat .git/HEAD | awk '{print ".git/"$2}' | xargs cat
+# d0b8727759e1e0e7aa3d41707d12376e373d5ecc
+.git
+!.git/HEAD
+!.git/refs
+
+# Common development/test artifacts
+/cover/
+/doc/
+/test/
+/tmp/
+.elixir_ls
+
+# Mix artifacts
+/_build/
+/deps/
+*.ez
+
+# Generated on crash by the VM
+erl_crash.dump
+
+# Static artifacts - These should be fetched and built inside the Docker image
+/assets/node_modules/
+/priv/static/assets/
+/priv/static/cache_manifest.json

.env.template

@@ -0,0 +1,83 @@
+# Default values are optimized for production to avoid having to configure
+# much in production.
+#
+# However it should be easy to get going in development too. If you see an
+# uncommented option that means it's either mandatory to set or it's being
+# overwritten in development to make your life easier.
+
+# Rather than use the directory name, let's control the name of the project.
+export COMPOSE_PROJECT_NAME=hellophoenix
+
+# You should generate a random string of 64+ characters for this value in prod.
+# You can generate a secure secret by running: ./run secret
+export SECRET_KEY_BASE=please_generate_a_more_secure_unique_secret_value_for_your_project
+
+# Which environment is running? MIX_ENV should be "dev" or "prod" and NODE_ENV
+# should be "production" or "development". When MIX_ENV is set to prod you'll
+# automatically be set to build and run releases instead of using mix.
+#export MIX_ENV=prod
+#export NODE_ENV=production
+export MIX_ENV=dev
+export NODE_ENV=development
+
+# The URL that will be generated through out your app. When you combine all 3
+# values it should be the URL that visitors access in their browser / client.
+#export URL_SCHEME=https
+#export URL_HOST=
+#export URL_PORT=443
+export URL_SCHEME=http
+export URL_HOST=localhost
+export URL_PORT=8000
+
+# If you're using a CDN you can customize which URL gets used for your static
+# files. If left commented out it will fall back to using your URL_HOST.
+#export URL_STATIC_HOST=
+
+# The bind port for cowboy (web server).
+#
+# Be warned that if you change this value you'll need to change 8000 in both
+# your Dockerfile and in a few spots in docker-compose.yml due to the nature of
+# how this value can be set (Docker Compose doesn't support nested ENV vars).
+#export PORT=8000
+
+# You'll always want to set POSTGRES_USER and POSTGRES_PASSWORD since the
+# postgres Docker image uses them for its default database user and password.
+export POSTGRES_USER=hello
+export POSTGRES_PASSWORD=password
+#export POSTGRES_HOST=postgres
+#export POSTGRES_PORT=5432
+#export POSTGRES_DB=hello
+
+# Should Docker restart your containers if they go down in unexpected ways?
+#export DOCKER_RESTART_POLICY=unless-stopped
+export DOCKER_RESTART_POLICY=no
+
+# What health check test command do you want to run? In development, having it
+# curl your web server will result in a lot of log spam, so setting it to
+# /bin/true is an easy way to make the health check do basically nothing.
+#export DOCKER_WEB_HEALTHCHECK_TEST=curl localhost:8000/up
+export DOCKER_WEB_HEALTHCHECK_TEST=/bin/true
+
+# What ip:port should be published back to the Docker host for the app server?
+# If you're using Docker Toolbox or a custom VM you can't use 127.0.0.1. This
+# is being overwritten in dev to be compatible with more dev environments.
+#
+# If you have a port conflict because something else is using 8000 then you
+# can either stop that process or change 8000 to be something else.
+#
+# Use the default in production to avoid having gunicorn directly accessible to
+# the internet without assistance from a cloud based firewall.
+#export DOCKER_WEB_PORT_FORWARD=127.0.0.1:8000
+export DOCKER_WEB_PORT_FORWARD=8000
+
+# What volume path should be used? In dev we want to volume mount everything
+# so we can develop our code without rebuilding our Docker images.
+#export DOCKER_WEB_VOLUME=./priv/static:/app/priv/static
+export DOCKER_WEB_VOLUME=.:/app
+
+# What CPU and memory constraints will be added to your services? When left at
+# 0, they will happily use as much as needed.
+#export DOCKER_POSTGRES_CPUS=0
+#export DOCKER_POSTGRES_MEMORY=0
+#export DOCKER_WEB_CPUS=0
+#export DOCKER_WEB_MEMORY=0

.formatter.exs

@@ -0,0 +1,6 @@
+[
+  import_deps: [:ecto, :phoenix, :ecto_sql],
+  inputs: ["*.{ex,exs}", "priv/*/seeds.exs", "{config,lib,test}/**/*.{ex,exs}"],
+  subdirectories: ["priv/*/migrations"],
+  line_length: 120
+]