Skip to content

Conversation

tomczakdominik
Copy link

@tomczakdominik tomczakdominik commented Jul 23, 2023

…detected

I have a Rails app which has a dockerfile named Dockerfile in a main directory and still fly launch was trying to build it as a ruby app, hence I propose adding this hint.

…detected

I have a Rails app which has a dockerfile named `Dockerfile` in a main directory and still `fly launch` was still trying to build it as a ruby app, hence I'm adding this hint.
@@ -31,7 +31,7 @@ Wrote config file fly.toml
? Would you like to deploy now?
```

Let `fly launch` generate an app name for you or pick your own.
Let `fly launch` generate an app name for you or pick your own. You may need to explicitily specify Dockerfile path using `--dockerile` flag if fly doesn't detect Dockerfile automatically.
Copy link
Contributor

Choose a reason for hiding this comment

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

There are two typos in that one sentence.

@@ -31,7 +31,7 @@ Wrote config file fly.toml
? Would you like to deploy now?
```

Let `fly launch` generate an app name for you or pick your own.
Let `fly launch` generate an app name for you or pick your own. You may need to explicitily specify Dockerfile path using `--dockerile` flag if fly doesn't detect Dockerfile automatically.
Copy link
Contributor

Choose a reason for hiding this comment

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

The issue isn't that fly doesn't detect the Dockerfile automatically, successfully launching a Rails application typically requires the setting of at least one secret (RAILS_MASTER_KEY), and either the deployment of a database or the creation of a volume. That's why the scanner for Rails is run before the Dockerfile scanner.

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.

2 participants