* API wrapper for many platforms
* SSH-key only access (password access disabled)
* Firewall management
* CRON management
* Sets up server dependencies and manages SSH keys
* Handles private networking between servers and firewalls to open ports between them
* Push to deploy (via Github)
* Handles spinning up more queue workers (beanstalkd + supervisord) by clicking a button
* Allows you to enter in "recipes" to run scripts (bash, php, others as well) on your servers
* Allows you to "archive" servers - which means Forge will "forget" your server,
eliminating the ability for Forge to access the server at all.
To re-enable the server from within Forge, you need to add in a
new ssh public key which Forge will re-generate for you.
* Server management (if your server goes down, you contact the hosting, not Forge)
While Forge is an advanced deployment tool similar to PuPHPet (https://puphpet.com/), ServerPilot is a modern alternative to cPanel for developers using their own servers.
> ServerPilot is a modern alternative to cPanel
Makes me want to kill it with fire. Lots of fire.
I suppose there are some lasting damage for becoming a sysadmin first and a developer second... ;-)
If someone looking to start using a framework asked me which they should pick, I would recommend Laravel in a heartbeat. It has a friendly, active community, amazing resources to learn from (Laracasts and many books/articles) and now with Homestead and Forge it should allow a new user to get up and running in a matter of minutes.
Really easy and powerful tool – BUT (this is a big one), why lock someone in with GitHub? Sure, GitHub is great. But what if I use BitBucket? Or even my own solution for my private projects?
This has killed many other services before for me, Pagoda Box (if I recall correctly) also forced someone to use GitHub, so did Appfog (or PHPfog rather).
I like Fortrabbits solution, where you at least can push your own code.
Edit: Confirmation of Bitbucket/Gitlab support coming soon:
I never had to use GitHub for PHPFog. What do you mean exactly?
You could try something like Dokku, Docker powered mini-Heroku https://github.com/progrium/dokku
If I am not wrong, DigitalOcean has dokku-installed images which you can just use within a few minutes.
Even if you are just running 2 sites, I really do think this is a great value for money ($10). If they only (as I wrote in my other comment) allowed for alternative ways to push your code.
Every time there was a different bug. Either something didn't install, or the config files weren't being loaded etc. I ended up learning Puppet because of it, so I guess some good has come of it ..
Slowly making it more and more stable, though.
If you now know puppet, maybe a PR or two would be on the horizon?
I have one built in Ansible for our Python webapp and the entire configuration is encoded in the playbooks, rolling up the application into a source distribution, pip installing it, and also installing the dependencies...
Very easy, dependable, and extremely flexible.
"Just another" is a really easy thing to say when it's someone else's creation. And more importantly trademarks are not indicators of quality or innovation. He's the owner and he chose to put it in the footer. This doesn't seem like a big deal.
I guess it gives you a nice web front-end, and maybe a bit of confidence that the configuration was designed by a professional?
overcast digitalocean create my-app
overcast run my-app install/core install/php install/apache install/mysql
I have a mockup in Balsamiq of how I want this to look. I also have a test query from PHP showing that I can connect to AWS Redshift. What I don't have is the PHP to render the user interface. Again, we are talking one text field, one three-way button and that's about it.
Anyone able to help point me in the right direction?
It's only $9 a month which imo is great value. I'd take a look through the free lessons and if you like what you see sign up for a month or 2 and start building.
In addition to this Dayle Rees has an excellent book which can be found at https://leanpub.com/codebright which takes you through all the basic stuff and more. I personally prefer Laracasts as I am more video inclined and Jeffrey is an incredible teacher but they are both great resources.
On top of which Jeffrey is just an all round nice guy (he does a bunch for the PHP community as well as some nice open source packages).
Rendering HTML isn't the highlight of Laravel (altho the template language is pretty nice)
I'm not sure what your idea is, exactly, but once you get Laravel up and running it's fairly easy to do what it sounds like you're saying. Create a Model to interact with the database, create a controller for your routing, and then a couple of views for your form/success page/etc.
- POST route to a controller which calls a model which handles the database stuff, then redirects to..
- the GET route which calls a controller which calls a model which pulls from the database and returns a View which parses the result of the query into a template.
Although you could do it all inside the route closures as well if you wanted... I don't know how much extra overhead there is doing it one way versus the other.
If you want to use Laravel I might suggest picking up one of the starters you can find on github or reading up on MVC, it's really not that hard although it can seem complicated because Laravel puts so much effort into trying to cover every possible model.
Although, given what you're describing, Slim Framework with Twig and a simple class for SQL might be easier.
I would (arbitrarily) reduce your choices to those two :
- Your project is not public and/or not likely to evolve much beyond the initial requirements : get Bootstrap and use a "basic" PHP script. You can already do a lot with raw PHP with the SPL (autoloader etc), filters (http://www.php.net/manual/en/book.filter.php), etc.
- If you need more, use a microframework like Silex or Flight. The learning curve will be steeper, but you'll also get more feature out of the box, if you need them.
Forge is essentially a platform that makes it very easy to provision a Laravel-ready server (though it states it works with other frameworks too). It's a replication of Laravel Homestead (http://laravel.com/docs/homestead) on a server, so you can have the same development and production environments.
This is going to make a big difference. For many, the setting up and launching part is a boring routine that they go through so often. I think the flat pricing model is the best part.
The upside is you found a service that saves you at least two hours per month. The downside is you're out $10.
Don't even get me started on the ubiquitous, ridiculously verbose, unhelpful, and intelligence-insulting comments. It's this kind of thing that makes me want to take up shooting sprees.
Ending it with "It's this kind of thing that makes me want to take up shooting spree" definitely confirmed that it was a pretty off-base and at least mildly inappropriate commentary.