Skip to content

Commit

Permalink
initial project creation
Browse files Browse the repository at this point in the history
  • Loading branch information
swelham committed Mar 12, 2019
0 parents commit d5db519
Show file tree
Hide file tree
Showing 8 changed files with 96 additions and 0 deletions.
4 changes: 4 additions & 0 deletions .formatter.exs
@@ -0,0 +1,4 @@
# Used by "mix format"
[
inputs: ["{mix,.formatter}.exs", "{config,lib,test}/**/*.{ex,exs}"]
]
26 changes: 26 additions & 0 deletions .gitignore
@@ -0,0 +1,26 @@
# The directory Mix will write compiled artifacts to.
/_build/

# If you run "mix test --cover", coverage assets end up here.
/cover/

# The directory Mix downloads your dependencies sources to.
/deps/

# Where third-party dependencies like ExDoc output generated docs.
/doc/

# Ignore .fetch files in case you like to edit your project deps locally.
/.fetch

# If the VM crashes, it generates a dump, let's ignore it too.
erl_crash.dump

# Also ignore archive artifacts (built via "mix archive.build").
*.ez

# Ignore package tarball (built via "mix hex.build").
faktory_worker-*.tar

# ignore elixir language server files
/.elixir_ls
3 changes: 3 additions & 0 deletions README.md
@@ -0,0 +1,3 @@
# Faktory Worker

**TODO: Add description**
30 changes: 30 additions & 0 deletions config/config.exs
@@ -0,0 +1,30 @@
# This file is responsible for configuring your application
# and its dependencies with the aid of the Mix.Config module.
use Mix.Config

# This configuration is loaded before any dependency and is restricted
# to this project. If another project depends on this project, this
# file won't be loaded nor affect the parent project. For this reason,
# if you want to provide default values for your application for
# third-party users, it should be done in your "mix.exs" file.

# You can configure your application as:
#
# config :faktory_worker, key: :value
#
# and access this configuration in your application as:
#
# Application.get_env(:faktory_worker, :key)
#
# You can also configure a third-party app:
#
# config :logger, level: :info
#

# It is also possible to import configuration files, relative to this
# directory. For example, you can emulate configuration per environment
# by uncommenting the line below and defining dev.exs, test.exs and such.
# Configuration from the imported file will override the ones defined
# here (which is why it is important to import them last).
#
# import_config "#{Mix.env()}.exs"
5 changes: 5 additions & 0 deletions lib/faktory_worker.ex
@@ -0,0 +1,5 @@
defmodule FaktoryWorker do
@moduledoc """
TODO: docs
"""
end
23 changes: 23 additions & 0 deletions mix.exs
@@ -0,0 +1,23 @@
defmodule FaktoryWorker.MixProject do
use Mix.Project

def project do
[
app: :faktory_worker,
version: "0.1.0",
elixir: "~> 1.8",
start_permanent: Mix.env() == :prod,
deps: deps()
]
end

def application do
[
extra_applications: [:logger]
]
end

defp deps do
[]
end
end
4 changes: 4 additions & 0 deletions test/faktory_worker_test.exs
@@ -0,0 +1,4 @@
defmodule FaktoryWorkerTest do
use ExUnit.Case
doctest FaktoryWorker
end
1 change: 1 addition & 0 deletions test/test_helper.exs
@@ -0,0 +1 @@
ExUnit.start()

0 comments on commit d5db519

Please sign in to comment.