btw
my whole daem time is being consumed in fixing this shit ;-;
yeah i don't know why i do it either. nothing better to do i guess.
...
And there is an issue tracker. https://github.com/divSelector/divchan/issues
I haven't really written a CONTRIBUTING file yet but if you're interested in adding something post an issue.
I wrote a build guide for people who want to contribute to the working on the source code of this site. https://github.com/divSelector/divchan?tab=readme-ov-file#build-guide
Here are some visual aids for Windows users.
Notice here I am right clicking in the folder and selecting, "Open in Terminal"
It's going to download Docker images and do a lot of crazy stuff and it's eventually going to tell you "Be Patient, This Takes Awhile" as it is generating fake content for the site.
Just wait.
When it finally says "celery@2397whatever ready", that it is when it is ready to open in the browser.
One thing I noticed is that Docker Desktop for Windows does not seem to broadcast on 0.0.0.0 but you can still access the link at http://localhost:8000
When you're done working on the development site you can do CTRL + C in the terminal window to close down divchan or you can click the Stop button in Docker Desktop
If we want to put the development server back up, we don't want to generate fake content a second time since it is rather time consuming. set FAKE_CONTENT=False in the .env file.
Then the next time you do docker compose up --build, it will not take as long.
Keep in mind when you modify the code, the changes will not update on the localhost site until you bring the docker containers down and rebuild. This means you can't just hit Play in Docker Desktop.
If you have questions, lmk.
fuck it!