Live data from Hacker News

A Docker-inspired Heroku clone in 100 lines of PHP

gist.github.com

21–30 of 34 posts

Re: A Docker-inspired Heroku clone in 100 lines of PHP

#21
post #9

What about dokku...loads of plugins and easily extendable.... https://goo.gl/JzMstI

I have been playing with Dokku lately. I ran into some problems with the Dockerfile mode (creates tags like myapp:latest but then tries to start dokku/myapp:latest) and the CLI not parsing arguments correctly (had to put extra " chars in strange places). Perhaps the Procfile mode is more polished. Would like to know if there are any alternative single-host PaaSes out there to use for side projects.

Did you create github issues for these? Dokku is an active project that gets a lot of attention. IMO this is currently the best solution for small scale projects.

Re: A Docker-inspired Heroku clone in 100 lines of PHP

#23
post #21

Earlier quoted context omitted.

I have been playing with Dokku lately. I ran into some problems with the Dockerfile mode (creates tags like myapp:latest but then tries to start dokku/myapp:latest) and the CLI not parsing arguments correctly (had to put extra " chars in strange places). Perhaps the Procfile mode is more polished. Would like to know if there are any alternative single-host PaaSes out there to use for side projects.

Did you create github issues for these? Dokku is an active project that gets a lot of attention. IMO this is currently the best solution for small scale projects.

+1 As one of the dokku maintainers, I would love to see any random issues fixed. Feel more than free to open an issue on our tracker[1] and I'll be sure to comment.

FWIW space processing in command line args is a bit... difficult given our mode of transport (ssh). This is something we're thinking about fixing somehow, though there isn't a great solution yet.

[1] https://github.com/dokku/dokku/issues

Re: A Docker-inspired Heroku clone in 100 lines of PHP

#24
post #17
post #13

Earlier quoted context omitted.

Nah, requiring Symfony is like requiring Django. Doesn't make much sense.

It's actually Silex. Maybe that makes more sense.

Silex is hardly a "micro framework", it's basically Symfony without the configuration files. So it's a LOT of code. I like it by the way, always hated the Spring like insanity of Symfony, but let's not pretend Silex + all Symfony libs the framework has to import are small.

The irony is that for this very project, Both Silex and Symfony\Process are completely redundant, especially with PHP bloated core APIs.

Re: A Docker-inspired Heroku clone in 100 lines of PHP

#26
post #4

I have never found "X lines of code" to be impressive. Write clean code and polish it and make it readable. Who cares how long it is. Hackers brag about lines, not engineers.

People like to specialize and seek extremes of different metrics. Do you think that the demoscene is not impressive because they could do much more with more than 4k of code?

This comment is an example of the type of negativity that is unhelpful and creates the toxic atmosphere HN is renown for, and I believe you know that considering you posted with a throwaway.

Re: A Docker-inspired Heroku clone in 100 lines of PHP

#28
post #24
post #17

Earlier quoted context omitted.

It's actually Silex. Maybe that makes more sense.

Silex is hardly a "micro framework", it's basically Symfony without the configuration files. So it's a LOT of code. I like it by the way, always hated the Spring like insanity of Symfony, but let's not pretend Silex + all Symfony libs the framework has to import are small. The irony is that for this very project, Both Silex and Symfony\Process are completely redundant, especially with PHP bloated core APIs.

That's not correct. Silex replaces the Symfony DI (or service locator, if you will) component with something much simpler called Pimple. You can read the code within a few minutes.

The only other required libraries for Silex to function are the event dispatcher, routing (which you can swap out for something like nikic/FastRoute), and the request/response stuff. I'm not sure if you think that's a "lot" of code, but if you're rolling your own you'd probably end up using the HTTPFoundation stuff anyway.

Post reply on HN