Move docker directory to it's own repository #17034
Replies: 4 comments 1 reply
|
Yeah i agree, having something as a standalone compose file with some empty directories serving as volumes could be okay for starters. It is sometimes PITA to clone the whole project since im most of the time just doing But i guess its easier for them this way to keep everything in one monorepo. I could create a repo like that for you cus i've been doing it couple times now already |
|
https://github.com/Madjarx/supabase-docker here you go until supabase guys make something! : D |
|
this is mostly for us to stay organized tbh - moving it to another repo means that someone in the team need to monitor another repo and manage issues/comments For now, i'm going to make this a Discussion - I really like the idea, but we need to consider whether it's worth it compared to some other alternatives:
|
|
You can do a Pulling from this StackOverflow answer: git clone -n --depth=1 --filter=tree:0 https://github.com/supabase/supabase
cd supabase
git sparse-checkout set --no-cone docker
git checkoutThen, you can pull the latest updates with a |

Uh oh!
There was an error while loading. Please reload this page.
Chore
Describe the chore
Move
dockerdirectory (needed for docker setup) to it's own repositoryAdditional context
This is a very large repository and if someone wants to try out self-hosted docker set up, they need to clone it entirely. Cloning with
--depth 1, I managed to let it download about ~400MBs before giving up and manually saving the files for docker set-up.This is also a pain point for server deployments where users may not want to store the entire supabase source tree. Updating supabase also means pulling all the source changes since the last update, which is also undesirable, especially in a case if an automation script is polling for updates.
All reactions