librelist archives

« back to archive

Heroku Issues

Heroku Issues

From:
Isaac Rabinovitch
Date:
2013-02-12 @ 08:59
I thought I should move this thread here:

https://twitter.com/nestacms/status/301221597996519424

Here's what happens when you try to cop a free domain:
> [isaac@snark picknit.com]$ heroku domains:add www.picknit.com
> Adding www.picknit.com to picknit... failed
>  !    Dev apps cannot have custom domains.
>  !    Upgrade to Basic or Production: 
> https://dashboard.heroku.com/apps/picknit/resources
> [isaac@snark picknit.com]$
I never managed to get my site uploaded to Heroku, so I can't do much to 
correct your docs. It wasn't a big priority for me, because I was 
planning to use AppFog in any case. (I sometimes do tech writing for 
them.) But I don't have a lot of experience with PAAS, so I thought I'd 
work through your document just so I'd understand things better. When I 
got stuck, it didn't make sense to persevere.

Re: [nesta] Heroku Issues

From:
Glenn @ Ruby Pond Ltd
Date:
2013-02-12 @ 17:35
> Here's what happens when you try to cop a free domain:
>> [isaac@snark picknit.com]$ heroku domains:add www.picknit.com
>> Adding www.picknit.com to picknit... failed
>>  !    Dev apps cannot have custom domains.
>>  !    Upgrade to Basic or Production:
>> https://dashboard.heroku.com/apps/picknit/resources
>> [isaac@snark picknit.com]$

It's as the message indicated, Dev apps are not able to have custom
domains added to them. Your site is accessible via
https://picknit.herokuapp.com

> I never managed to get my site uploaded to Heroku, so I can't do much to
> correct your docs.

A custom domain isn't required to push your site, the rest of the
instructions should work fine.

Hope that helps,

G

Re: [nesta] Heroku Issues

From:
Isaac Rabinovitch
Date:
2013-02-12 @ 19:17
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    It's a domain, and it's customized, but it's not what people usually
    mean by custom domain. That's support for a 2ld. This is not
    difficult to support (you just allow people arbitrary values in
    their domain list) but Heroku has obviously made a business decision
    to reserve this feature for their paying customers. As they have
    every right to do, but the Nesta docs need to make it clear what
    "free hosting" means in this context.<br>
    <br>
    The other instructions do <i>not</i> work as specified. The current
    <tt>heroku </tt>command line syntax is significantly different. I
    probably could have figured it out, but as I said before, this was
    just an educational exercise, not worth extensive head-beating.<br>
    <br>
    <div class="moz-cite-prefix">On 2/12/2013 9:35 AM, Glenn @ Ruby Pond
      Ltd wrote:<br>
    </div>
    <blockquote
cite="mid:CAJVSNSyittR5ZMB4jJjcKp2rgb9tnTehHpKkCEq92CHa7BKtGg@mail.gmail.com"
      type="cite">
      <blockquote type="cite">
        <pre wrap="">Here's what happens when you try to cop a free domain:
</pre>
        <blockquote type="cite">
          <pre wrap="">[isaac@snark picknit.com]$ heroku domains:add <a 
class="moz-txt-link-abbreviated" 
href="http://www.picknit.com">www.picknit.com</a>
Adding <a class="moz-txt-link-abbreviated" 
href="http://www.picknit.com">www.picknit.com</a> to picknit... failed
 !    Dev apps cannot have custom domains.
 !    Upgrade to Basic or Production:
<a class="moz-txt-link-freetext" 
href="https://dashboard.heroku.com/apps/picknit/resources">https://dashboard.heroku.com/apps/picknit/resources</a>
[isaac@snark picknit.com]$
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
It's as the message indicated, Dev apps are not able to have custom
domains added to them. Your site is accessible via
<a class="moz-txt-link-freetext" 
href="https://picknit.herokuapp.com">https://picknit.herokuapp.com</a>

</pre>
      <blockquote type="cite">
        <pre wrap="">I never managed to get my site uploaded to Heroku, so
I can't do much to
correct your docs.
</pre>
      </blockquote>
      <pre wrap="">
A custom domain isn't required to push your site, the rest of the
instructions should work fine.

Hope that helps,

G
</pre>
    </blockquote>
    <br>
  </body>
</html>

Re: [nesta] Heroku Issues

From:
Graham Ashton
Date:
2013-02-19 @ 12:08
On 12 Feb 2013, at 19:17, Isaac Rabinovitch <isaac@picknit.com> wrote:

> The other instructions do not work as specified. The current heroku 
command line syntax is significantly different. I probably could have 
figured it out, but as I said before, this was just an educational 
exercise, not worth extensive head-beating.

I was surprised when you reported this, as I've never noticed a breaking 
change in the commands required to create a Heroku app.

I've just tested the Heroku deployment docs from start to finish, typing 
in what's on the page word for word. It worked without an issue.

For reference, I've got the heroku command installed in /usr/bin/heroku, 
via the Heroku Toolbelt (rather than the old gem - though that shouldn't 
make the slightest difference in this case).

I've updated the paragraph on custom domains to recommend OpenShift and/or
AppFog, on both of which hosting on your own domain is free as far as I 
can tell.

http://nestacms.com/docs/deployment/heroku

-- 
Graham Ashton
Founder, The Agile Planner
http://theagileplanner.com | @agileplanner | @grahamashton

Re: [nesta] Heroku Issues

From:
Graham Ashton
Date:
2013-02-13 @ 11:23
On 12 Feb 2013, at 19:17, Isaac Rabinovitch <isaac@picknit.com> wrote:

> Heroku has obviously made a business decision to reserve this feature 
for their paying customers. As they have every right to do, but the Nesta 
docs need to make it clear what "free hosting" means in this context.

I agree; it clearly isn't as free as it was. My personal sites and 
nestacms.com are still hosted on Heroku for free. The policy change must 
only affect new sites.

We've already got OpenShift deployment documented [1] though I've only 
used it enough to test those docs, and I'm not sure if they support using 
your own domain for free.

[1] http://nestacms.com/docs/deployment/openshift

AppFog are clearly another great candidate, and we should get that documented.

I had always felt that Heroku was really the default platform for hosting 
Nesta, but if the entry fee for running it on a domain of your choosing is
now $9 a month I think the Nesta docs ought to promote free options first.
I've clearly got some re-writing to do.

> The other instructions do not work as specified. The current heroku 
command line syntax is significantly different.

Okay, thanks. I'm not sure which bit, but don't worry - I'll test it from 
scratch and make sure it works.

-- 
Graham Ashton
Founder, The Agile Planner
http://theagileplanner.com | @agileplanner | @grahamashton

Re: [nesta] Heroku Issues

From:
Isaac Rabinovitch
Date:
2013-02-13 @ 17:28
On 2/13/2013 3:23 AM, Graham Ashton wrote:
> AppFog are clearly another great candidate, and we should get that 
> documented.
And deployment is pretty simple. I'll try to write it up for you today 
or tomorrow.
> I had always felt that Heroku was really the default platform for 
> hosting Nesta, but if the entry fee for running it on a domain of your 
> choosing is now $9 a month I think the Nesta docs ought to promote 
> free options first. I've clearly got some re-writing to do. 
Their pricing structure has changed too. A basic-level app (the minimum 
that supports custom domains) costs $15 per month per instance.

A lot of people have made use of Heroku freebies for casual projects. 
Not only do you see them mentioned in the docs for many OS frameworks, 
but MOOCs have begun specifying them as a way to submit projects for 
grading. Must cost them, so of course they're limiting free access.

Note that AppFog lets you have any number of free instances as long as 
you keep the total memory footprint below 2GB. Given the size of Ruby 
apps, that's a lot of instances! Back-end stuff is limited to 8 
instances, and there's no SSL.

Re: [nesta] Heroku Issues

From:
Graham Ashton
Date:
2013-02-12 @ 09:20
On 12 Feb 2013, at 08:59, Isaac Rabinovitch <isaac@picknit.com> wrote:

> Here's what happens when you try to cop a free domain:
>> [isaac@snark picknit.com]$ heroku domains:add www.picknit.com
>> Adding www.picknit.com to picknit... failed
>> !    Dev apps cannot have custom domains.

Okay, thanks Isaac. I'll look into it (if any Heroku staff happen to be 
reading - if we drop Postgres addon might custom domains start working 
again? I know, sounds like a long shot...)