• Members 8 posts
    July 11, 2020, 5:53 p.m.

    I'm working on customizing a clone of Misago main repo & installing it with misago_docker by making these changes to misago_docker/misago/requirements.txt :

    markdown==2.6.11          # via misago
    # misago==0.27.0            # via -r requirements.in
    git+https://github.com/<user>/misago.git#egg=misago
    more-itertools==8.3.0     # via misago, pytest
    

    Questions :
    1- Is this a bad idea ? Any suggestions ?
    2- Could a similar functionality be added to misago_docker ? Although misago_docker uses pip-compile --output-file=requirements.txt requirements.in & apparently, pip installing from repo + pip-compile wouldn't work on all pip versions until this issue is fixed.

  • Members 3 posts
    July 11, 2020, 6:33 p.m.

    Hi hrod,

    I'm trying to customize the code as well, but the way it's set up with docker is not the easiest. I'd like to fully customize it and add other apps to it, but I don't like doing it using the app manager. Ideally, I'd like to treat the project like a normal django project. What's the easiest way?

  • Members 8 posts
    July 11, 2020, 7:23 p.m.

    Warning : this is completely unnecessary for most cases, as misago_docker provide easier functionality to customize it.

    This is what I'm doing, but open to any suggestion :

    1- clone Misago main repo
    2- use the development functionality to customize it
    3- run gulp build
    4- push to a github repo (so that it can be pip installed from misago_docker)
    5- clone misago_docker
    6- edit misago_docker/misago/requirements.txt as explained above.
    7- push to github repo
    8- Follow same setup but using your misago_docker repo. For example : git clone https://github.com/<myusername>/misago_docker.git --depth=1

    misago_docker will install as intended, the only difference is that instead of pip installing Misago, it will install your customized Misago directly from your github repo.

    I'm probably doing something wrong, any suggestion would be appreciated. Not sure if this approach would make future maintenance difficult.

    Again, this is not necessary for most cases. In my case, I'm experimenting with integrating many functionalities, that would essentially turn it into a different kind of site.