Skip to content

Commit 2ceb10a

Browse files
committed
Added a section about picking a name for the Heroku app
Thanks to pozorvlak for the feedback and original proposal.
1 parent edc4c5a commit 2ceb10a

File tree

1 file changed

+20
-4
lines changed

1 file changed

+20
-4
lines changed

deploy/README.md

Lines changed: 20 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -150,17 +150,33 @@ Next, we’ll create a new git repository and save our changes. Go to your conso
150150
create mode 100644 requirements.txt
151151
create mode 100644 runtime.txt
152152

153-
## Deploy to Heroku!
153+
## Pick an application name
154154

155-
That was a lot of configuration and installing, right? But you only need to do that once! Now you can deploy!
155+
We'll be making your blog available on the Web at `[your blog's name].herokuapp.com`, so we need to choose a name that nobody else has taken. This name doesn't need to be related to the Django `blog` app or to `mysite` or anything we've created so far. The name can be anything you want, but Heroku is quite strict as to what characters you can use: you're only allowed to use simple lowercase letters (no capital letters or accents), numbers, and dashes (`-`).
156156

157-
It's as simple as running this command, replacing `djangogirlsblog` with your own application name:
157+
Once you've thought of a name (maybe something with your name or nickname in it), run this command, replacing `djangogirlsblog` with your own application name:
158158

159159
$ heroku create djangogirlsblog
160160

161161
> __Note__: Remember to replace `djangogirlsblog` with the name of your application on Heroku.
162162
163-
This automatically added the Heroku remote for our app to our repository. Now we can do a simple git push to deploy our application:
163+
If you can't think of a name, you can instead run
164+
165+
$ heroku create
166+
167+
and Heroku will pick an unused name for you (probably something like `enigmatic-cove-2527`).
168+
169+
If you ever feel like changing the name of your Heroku application, you can do so at any time with this command (replace `the-new-name` with the new name you want to use):
170+
171+
$ heroku apps:rename the-new-name
172+
173+
> __Note__: Remember that after you change your application's name, you'll need to visit `[the new name].herokuapp.com` to see your site.
174+
175+
## Deploy to Heroku!
176+
177+
That was a lot of configuration and installing, right? But you only need to do that once! Now you can deploy!
178+
179+
When you ran `heroku create`, it automatically added the Heroku remote for our app to our repository. Now we can do a simple git push to deploy our application:
164180

165181
$ git push heroku master
166182

0 commit comments

Comments
 (0)