Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jamesheroku
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
High-Performance Graph Applications for Every Developer
(memgraph.com)
5 points
by
jamesheroku
5y ago
|
0 comments
2.
▲
Do you disambiguate between authentication and authorization?
(blog.aserto.com)
1 points
by
jamesheroku
5y ago
|
1 comments
3.
▲
Netlify, a sevice for quickly rolling out static websites, raises $2.1M
(techcrunch.com)
56 points
by
jamesheroku
10y ago
|
25 comments
4.
▲
OSS Tracing Is Broken: “Towards Turnkey Distributed Tracing”
(medium.com)
2 points
by
jamesheroku
10y ago
|
0 comments
5.
▲
Citus Unforks from PostgreSQL, Goes Open Source
(citusdata.com)
763 points
by
jamesheroku
10y ago
|
153 comments
6.
▲
Third Party Tools as a Marketing Tactic
(heavybit.com)
3 points
by
jamesheroku
12y ago
|
0 comments
7.
▲
Styling APIs: Apiary launches an enterprise API design product
(blog.apiary.io)
15 points
by
jamesheroku
12y ago
|
0 comments
8.
▲
Heavybit and Heroku Founder on YC's RFS for Dev Tools
(venturebeat.com)
14 points
by
jamesheroku
12y ago
|
1 comments
9.
▲
Ask HN: What would you like me to talk about at Startup School? (Heroku)
10 points
by
jamesheroku
15y ago
|
8 comments
10.
▲
Matz (creator of Ruby) joins Heroku
(blog.heroku.com)
578 points
by
jamesheroku
15y ago
|
75 comments
11.
▲
Official Heroku Blog: Major New Platform Version
(blog.heroku.com)
50 points
by
jamesheroku
15y ago
|
1 comments
12.
▲
by
jamesheroku
16y ago
Heroku IPs are 75.101.163.44, 75.101.145.87, and 174.129.212.2, if you want to update the script to make the distinction from raw Amazon EC2.
13.
▲
by
jamesheroku
16y ago
18 now. ;-)
14.
▲
by
jamesheroku
17y ago
For sub-hour scheduled or recurring tasks, most users prefer a scheduled background task with DJ, rather than old-school cron. There are a bunch of ways to do this, for example: Delayed::Job.enqueue(work, 0, Time.now + 5.minutes) D
15.
▲
by
jamesheroku
17y ago
This article contains quite a bit of inaccurate information. Despite the size of 22 double-XL instances, they were a small portion of our overall footprint in EC2; it takes well over that kind of capacity to run the platform. Those instance
16.
▲
by
jamesheroku
17y ago
We aren't planning to provide any additional types of file storage, as we don't believe that the local file system should be used at all in a scalable app, as it creates state at the app server. We do provide access to /tmp if you need scra
17.
▲
by
jamesheroku
17y ago
Transfer between S3 and your Heroku app (which lives inside EC2) is free.
18.
▲
by
jamesheroku
17y ago
We've seen a ton of Couch and Mongo apps lately - works very well with Heroku. Check out http://www.mongohq.com .
19.
▲
by
jamesheroku
17y ago
Storage limits are for database data only, they don't apply to assets like uploads. Assets should be stored in an asset store, like S3.
20.
▲
by
jamesheroku
17y ago
Correct, the editor is no longer supported. We hope to bring it back sometime in the future.
21.
▲
by
jamesheroku
17y ago
Exactly. Most people use DelayedJob to do image processing in the background - also the correct/scalable way to do it. More here: http://docs.heroku.com/background-jobs http://docs.heroku.com/delayed-job
22.
▲
by
jamesheroku
17y ago
Thanks for the feedback. === ImageMagick We have a couple thousand apps using ImageMagick/RMagick, and haven't had any reports of missing functions. We are running ImageMagick 6.2.4 (will be updated to 6.3 sometime soon), so you might chec
23.
▲
by
jamesheroku
17y ago
Awesome, we look forward to it. I just created a quick Rack app that uses curb and deployed it to Heroku, no problem: http://gist.github.com/108315 If you keep having trouble with your app, please shoot me an email or open a support ticke
24.
▲
by
jamesheroku
17y ago
Hey Nir, it's James from Heroku. Sorry to hear you had trouble with Heroku. I'd like to address some of your concerns: 1. Gems We completely support all types of gems, including gems with native bindings (which get compiled automatically
25.
▲
by
jamesheroku
17y ago
Thanks Marcos. We were running db:migrate on push a long time ago for a while, but we ended that practice when serious production applications started moving on to the platform. We found that running db migrations explicitly is very import
26.
▲
by
jamesheroku
17y ago
We currently have 11, plus some contractors.
27.
▲
by
jamesheroku
17y ago
That's interesting feedback, thanks. Sounds like two different issues: 1. Database pricing. We aren't trying to sell storage space, that's not the value you're getting with a Heroku db plan. We would argue that the value is the instant,
28.
▲
by
jamesheroku
18y ago
Nice work Peter. I wrapped this in two lines of Sinatra and deployed it to Heroku, so anyone can get an RSS feed for their username: http://hackernews.heroku.com/username Code is here: http://github.com/jnl/hackernews-thread-rss
29.
▲
by
jamesheroku
18y ago
Wow, that's silly. Fixed - thanks.
30.
▲
by
jamesheroku
18y ago
Ah, bingo. Yes, "it just works" and "it glides" are exactly what we're going for. Our version of the magic deploy button is "git push". We've got some great detailed posts coming up about this. The thing that we've discovered is that ins
More ›