Add Docker Compose setup

[subhayand10]

So, I was trying to get my hands on this application, and I noticed few things which is kind of a problem for other contributors.

->Currently the backend URL is a public link, and user needs to be verified to access the application which is not ideal for other contributors.
->There's no config.json in the repository which provides the Postgres dB URL (which I know is ideal).

So, my solution is to dockerize the whole backend (and also the Postgres dB) and self-host, after that we can also change the verified column default value to be true, so that for testing purpose user can access the application from local.

All these changes would only be meant for local development for other contributors and would not be merged in the main branch.

Let me know if this is valid and I would like to work on it. 😇

[retrixe]

Since this was mainly a personal project (I'm surprised it's garnering attention tbh), I haven't written much documentation about getting the software running

I'm not sure if a docker container makes the most sense since it sounds overkill, but if you are still interested in writing a docker container, I can definitely look at pulling the Dockerfile upstream

Otherwise, I feel this is mostly an issue with the lack of documentation. I can write a setup guide sometime today in the readme to explain how to get the backend, frontend and postgres working

Additionally, I'll disable the verification system for now until I write email verification working sometime in the future, so the public instance at https://concinnity.retrixe.xyz should be accessible to everyone after that (^⁠^) For people exclusively contributing to the frontend, they should be able to set https://concinnityserver.retrixe.xyz as the backend URL to use the public instance once I do that

Let me know if you're still interested in the dockerisation, else I'll close this issue once I've published a complete setup guide and disabled the verification system

[subhayand10]

Well you're correct dockerizing the whole backend is an overkill(currently) so that's why I'm suggesting it should be in a separate branch.In future when the application grows and also the dependencies, we can add on to our existing docker files and add it in the main branch.
Yes I would like to work on this if feasible for future use.🫡

[retrixe]

FWIW if you are going to make a docker container, I feel it would be better to dockerise both frontend and backend in the container, because the backend is just a single binary which is honestly not worth building an entire container for

[subhayand10]

Sure will work on dockerizing the whole application then.

…

On Thu, 16 Jan, 2025, 2:18 pm Ibrahim Ansari, ***@***.***> wrote: FWIW if you are going to make a docker container, I feel it would be better to dockerise both frontend and backend in the container, because the backend is just a single binary which is honestly not worth building an entire container for — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANXIJMP5EYFKYXEMJNASAUD2K5W65AVCNFSM6AAAAABVHIRTLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJUHEYDIOBRGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>