HECKEN HECK YEA
@Sir_Boops okay! let's check this out
@ashfurrow gl;hf :>
@Sir_Boops I'm having mind-blowing breakthroughs about the implications here
So, like, the servers don't have the source code or git repo /at all/, they just need docker-compose.yml
@ashfurrow Yeeep and if you store assets on remote servers you're entire masto folder will only end up being a few GB + DB size XD
@Sir_Boops oh right, the volumes in docker-compose.yml don't *really* need to point to folders in the source, right? Like they need to be put somewhere, maybe on remote servers eventually, but don't need to point to inside the source repo.
@ashfurrow Ya the public folder does without that masto will really break ;p
@Sir_Boops wait, so I do need to keep the source on the server as well❓
@ashfurrow Nope the image itself should be holding the source for you :3 that was the COPY command in the docker container!
@Sir_Boops RIght, sorry just confused about the public folder I think. You've got it pointed to `./public`, right? and that's just an arbitrary directory?
@Sir_Boops I think my brain is still having a hard time separating the source code from the docker-compose.yml file and from the Dockerfile. They've always been together for me but they're conceptually all different.
@ashfurrow Play around with them some more then they'll start to make sense! :3
DOcker is hard to start with :x
@Sir_Boops good idea, yeah.
@ashfurrow amazing for sharing!
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!