-
Website
-
Original page
http://blog.heroku.com/archives/2007/10/30/the_big_kickoff/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
misfo
3 comments · 2 points
-
JeanHuguesRobert
3 comments · 2 points
-
Morten Bagai (Heroku)
9 comments · 1 points
-
adamheroku
9 comments · 3 points
-
justindz
2 comments · 1 points
-
-
Popular Threads
-
Heroku | DJ has evolved into Workers
2 weeks ago · 36 comments
-
Heroku | DJ has evolved into Workers
he barrier between an idea and execution. If you wanted to set up a demo version of an app for a client for instance.
The use cased described are actually exactly things I've encountered so I'm pretty stoked about it.
Ethan
It definitely looks like a nice app and good project you guys have done, but it seems to me that Rails is one of the easiest development environments to get started with; and most rails developers actually like fully controlling their dev environment, no?
Sure some developers like controlling their dev environment - I know we do. But we also recognize that there is a cost to that. Rails is about convention over configuration in your code, so by default you don't have to do anything, and everything just works. We think the hosting/deployment process should be the same way. Of course our solution isn't going to work for everyone, but we want to have solid default conventions so you can just get up and running in one click. We also think there are a lot of benefits to be had by having the editor and the running application integrated tightly together on the same machine. More about this in a later post...
ides playing around a little bit?
l and scalable hardware? if yes, i am quitting my host.
No control panel is necessary, as you don't have to worry about any of the normal details of hosting. We will be adding features like custom domain names, etc.
I wish you guy's the best of luck in getting this project off the ground and into the mainstream.
I think there is definitely some sort of niche out there for this sort of tool. The most obvious would be mobile workers like Joseph.
Good luck!
Your idea is really great. I do totally agree with you : all projects don't need "standard" hosting. Drafts, demos... I have 1000 ideas of "3 clics a day" site (-;
Good luck !!!
* Text editors are often highly optimized for productivity (think vi, emacs, ides, etc.). You have some syntax highlighting but what about other standard features in a text editor. Seems like there would be a lot of development work involved in making a compelling web-based editor. Syntax highlighting and a save button isn't going to cut it for real development
* One of the nice things about rails is that it encourages a controlled method of updating. Usually you develop in a development environment. Implement extensive unit testing to ensure you don't break anything. And then when you are ready to roll a tool like capistrano to do a controlled release. This tool seems to break that model by allowing an immediate edit to a production site. This is nice for quick changes and maybe even ok for internal applications but most applications still need a little of that controlled update process that Rails encourages. So my question is will users have a "development" version of the site they can work on without affecting the production site? Perhaps even multiple development version so they can work on different branches of the same project. Will developers be able to easily run their automated testing (unit, functional and integration)? Will their be tools like Capistrano to manage the deployment from one environment to another? What about tools like SVN to branch a project for refactoring purposes and experimental features? I realized you are trying to keep it simple and start small but do you eventually plan to support a professional-style development environment?
* My final question is on of code access. No matter how snazzy you make your tools some developers will want to use their old tools because that is what they are good with. With a tool like SVN this is ok because they can check the code out in their own environment and develop in their own environment and then commit back into a common repository. But this requires that your system have some tool like SVN where a developer can check out the code, make their changes using their tools and check it back in making their changes available to other developers that are using your tools. So what type of access is there to the code developed. It is easy access with a tool like SVN or a little more pain like a code export/import and merging manually?
Respect!
My first thought was in regards to the text editor. Purple on black is a little hard on the eyes. I tend to like like clean white background like most text editors. I would suggest keeping with the style used on the myapps page, this is clean and easy on the eyes. Just simple esthetics's but if i'm going to spend hours developing in here my eyes won't last as long. maybe the editor style can become customizable in the future.
I like where this is going. As the app becomes more robust, I can see this becoming a great development environement.
No guys.. What about Locomotive? It's very easy to install and its free. And its much easier to develop applications on your local machine. You have everything in your hands and a little bit more. But in WWW you have only interface, which was created with limited features. As for deployment - you are right. Sometimes it is not easy.
I think that you have nice looking project with very nice interface. But isn't it better to use your talents in creating something more usefull for people? Rails is specific and it used by developers and many of them using Vi, EMacs and textmate shortcuts. This guys prefer console (as for me i prefer UI).
Thanks a lot guys!
the generate pop up box works about 20% of the time.
the other 80% it fails without message - just, nothing happens.
in editor, if select a word, and start typing, the text doesn't replace the word, instead it gets inserted wherever the cursor was before selected the word.
Please send us a feedback email with a more detailed description of what you did.