Putting Laravel files to server without git

Hey, firstly you wouldn't need to have a fresh install of Laravel. You're doing twice the work there.

Simple answer is yes, upload all the files, you'll need to run composer install and a few other things but that sums it up, you'll need to make sure that you're uploading your resources and there are other questions to be answered about how you're handling your css, js and other files.

I guess we have to ask what is your experience level, and another question - why aren't you using Git? Are you aware of Forge?

Before refreshing this page, I was literally just thinking "oooh, this is why forge is a thing!". I'm aware of it but didn't think it would be necessary for my project. I only installed a fresh copy of laravel because it was literally a two step process... Just wanted to see that pretty, thin laravel font ;)

To be honest, not using git because I'm running low on cash... Will probably end up going with git.

I'm pretty sure the css/js files will work because they're referenced using elixir. I should also mention that I've come from using homestead (and am aware that env variables need to be updated)

Thanks for you're reply @mstnorris will see how I go!

If you are holding off using Git because you want a don't want to pay for a private repo on GitHub then Bitbucket.org offers private Git repos for free.

This means you can use Git to deploy your app on your DO server without any extra cost and all the conveniences of Git.

@ ldiebold, I second what @robgeorgeuk said. I've used Bitbucket for years, unlimited private Git repos. Every project of mine is stored on Bitbucket.

Subversioning is extremely valuable and you really should get in the habit of using it, even if just locally. Being able to go back to a previous point to see what changed in a file and why has saved me several times when someone reports a bug.

Also, I know that money is tight (it is for me, too), but if you can find a way to use either Forge or Envoyer to deploy code rather than using FTP I really think it will help you in the long run. Before I started deploying with Git I would constantly forget to upload files that were changed locally, leading to massive conflicts in both my dev and production environments. Now, when I deploy using Git and Envoyer, I'm 100% positive that both ends are the same.

Wow, thanks @robgeorgeuk and @opheliadesign, this is exactly the advice I needed. I'll start with bitbucket to test things out (I'm just doing a beta release of my site for now) then switch over to github and look into Forge/Envoyer.

Okay... If $10 a month could have saved me all this time it would have been worth it. It's nice to have some experience setting up servers but envoyer sounds like the holy grail right now.

Just so you know it's an option:

I use Git to manage/deploy my code, and I do not host it on Github or any such service. You can set this up yourself if you want.

Just thought I'd give an update.

I decided to use Laravel forge and it' awesome. It was a useful experience playing around with a DO server because it gives you the chance to put the command line to real use. I did, however, conclude that $10 a month is peanuts considering that it saves you a crap load of time and as we know... time is money anyway!