4 ms·
The current state of deployments (and dev environments in general) are a hot mess, especially for people who are not active developers, and just ocassional prog
by boplicity 6y ago
The current state of deployments (and dev environments in general) are a hot mess, especially for people who are not active developers, and just ocassional programmers. I update a few different web apps every year (or two), and each time, it is a nightmare. Unless, of course, I'm doing a simple drag and drop into Filezilla. In that case, it's effortless. The difference? The ridiculous tools I need to use just to get the code compiled and ready to deploy, much less somehow figure out how to actually connect to the server. This can make the absolute most simple changes not worth it, because I don't want to lose a day to debugging the inevitable problems that happen when I try to get the dev environment started. And yes, sadly, they are inevitable. Especially after letting things sit for a year.
- clintonb 6y agoI have found that investing in writing a README saves a lot of time when revisiting of projects. Pinned dependencies ensure I rarely have to deal with returning to a broken, or non-reproducible, development environment.
- folkrav 6y agoThe Filezilla/(s)FTP approach still works just fine for simple usecases such as yours. For anything else remotely mission critical... I seriously cannot long for the days of figuring out the hard way that someone, sometime, nobody knows when, fixed something straight in prod over FTP and I just overwrote it by just pushing the last file in repo. I've been burned by this crap way too often compared to how young my career is...
- regularfry 6y agoThe wonderful thing is that all the tools that worked 10 years ago largely still do. It's still absolutely fine to stand up a rails site behind nginx on a single host and expand from there when you need to (or, more accurately, when you can, because redundancy always was a thing).