0

I'm trying to push a Laravel installation from development to a live-environment on a Laravel Forge-server. When pushing, I'm getting an error, that I'm not getting on my local environment.

I can't figure out, how I connect directly to the provisioned server (through FTP or SFTP), to change single files manually (to debug).

Which means that in order to try something, then I need to make a new commit and an entirely new deployment, for every thing I want to test. Quite tedious and it clutters my git history!

... I can't even do a commit --amend, since that gives me the error:

fatal: refusing to merge unrelated histories

Attempt 1) I can't find anything about it in the Forge knowledge base.

Attempt 2) I've found several articles talking about a good guide, but that guide gives an error 404: It's this one: https://freek.dev/2016/03/let-your-clients-use-sftp-on-a-forge-provisioned-server/

Am I missing something obvious? Or is the commit-n-push really the way to go? Is this normal for automated deployment systems?

Zeth
  • 2,273
  • 4
  • 43
  • 91

1 Answers1

0

For others who find this question, then Forge-support got back to me really quickly and linked to this blogpost, explaining how to get sftp-access to a Forge-provisioned server

What I did wrong, was that I didn't use the username: forge (I was using my email).

Zeth
  • 2,273
  • 4
  • 43
  • 91