Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by BenBradleySmith on Monday May 19, 2014 @09:34AM
(#7767309)
I think that Taylor mentioned in the keynote that BitBucket support is planned.
Edit: Confirmation of Bitbucket/Gitlab support coming soon: https://twitter.com/laravelphp/statuses/468401873519915008
Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by olssonm on Monday May 19, 2014 @09:35AM
(#7767316)
If so – I'm very glad to hear that! Then there's hope for someone like me too.
Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by robjmills on Monday May 19, 2014 @11:01AM
(#7767717)
Taylor has just mentioned on Twitter that he's going to start looking at Gitlab and Bitbucket tonight.
Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by mskierkowski on Monday May 19, 2014 @10:01AM
(#7767423)
In the mean time you can use https://factor.io/ for "push-to-deploy" with BitBucket or Gitlab.
Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by Kiro on Monday May 19, 2014 @01:17PM
(#7768561)
> so did Appfog (or PHPfog rather)
I never had to use GitHub for PHPFog. What do you mean exactly?
Re:Laravel Forge – PHP Platforms On Linode, DigitalOcean, AW...
by olssonm on Tuesday May 20, 2014 @02:44AM
(#7771476)
My bad – perhaps it was Engineyard? I know that there was one more service that I've tried besides PagodaBox on which you were "forced" to use GitHub to deploy code.
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.