Mix.Project.config[:version] is not production related. It fails when starts production env mode.

Related issue: #15

Hi there!

We need to add a description to the projects so that users can find out what kind of project needs to translate. Can you help us?

This is not a hard problem to solve:

• 1. First let's add some tests for our feature:

# test/docdog/editor/editor_test.exs

...

-    @update_attrs %{"name" => "Phoenix Documentation"}
+    @update_attrs %{"name" => "Phoenix Documentation", "description" => "New description"}

...

    test "update_project/2 with valid data updates the project", %{project: project} do
      assert {:ok, project} = Editor.update_project(project, @update_attrs)
      assert %Project{} = project
      assert project.name == "Phoenix Documentation"
+     assert project.description == "New description"
    end
...

# test/docdog_web/controllers/project_controller_test.exs

...

-    project = insert(:project, user: user, name: "Elixir Documentation 1")
+    project = insert(:project, user: user, name: "Elixir Documentation 1", description: "Official documentation of Elixir language")

...

     test "lists main user projects", %{conn: conn} do
       conn = get(conn, project_path(conn, :index))
       assert html_response(conn, 200) =~ "Elixir Documentation 1"
+      assert html_response(conn, 200) =~ "Official documentation of Elixir language"
+
       assert html_response(conn, 200) =~ "Elixir Documentation 2"
+      assert html_response(conn, 200) =~ "No description"
+
       refute html_response(conn, 200) =~ "Another User Project"

...

    test "renders form", %{conn: conn} do
      conn = get(conn, project_path(conn, :new))
      assert html_response(conn, 200) =~ "New Project"
+     assert html_response(conn, 200) =~ "Description"
    end

...

• 2. Run mix test. You'll see:

82 tests, 3 failures

Now you need to fix all of them. This is a real TDD.

• 3. Run mix ecto.gen.migration add_description_to_projects. See one of another migrations in project and add body to the new one migration like there.

• 4. Run mix ecto.migrate to apply the migration.

• 5. Add new field to schema and changeset in Project module.

• 6. Add changes to project/_project and project/form templates.

NB. In tests we want to output "No description" in case of empty description. To make it easy, simply add this function to views/project_view.ex:

def description(project) do
  project.description || "No description"
end

And call it in template.

Good luck!

I have found these guys on github: https://github.com/translation-gang

I think that it may be a good idea to cooperate with them. Since we all do the same thing.
@rtrv @jarosluv what do you think?

When sign in first time everything worked fine, but with login from other browser I get
Internal server error

Right now mix credo --strict generates more than 160 issues.

credo must be a required step inside travis.
I will add it, and also fix existing linting issues.

PR is incoming.

Add public projects to popular section.

Travis has a special way to handle deployments.
In our case it is a script: https://docs.travis-ci.com/user/deployment/script/

In this case we won't have any problems in deploying broken releases or deploying branches other than master.

PR is incoming.

We have to choose a license before the contributions start.
Because, that's a very important thing.

Depending on the license this software might not be considered OSS.
Here's a good way to start: https://choosealicense.com/

I personally prefer MIT.