Skip to content

Conversation

@jodal
Copy link
Owner

@jodal jodal commented Jan 23, 2022

No description provided.

@jodal jodal self-assigned this Jan 23, 2022
@codecov
Copy link

codecov bot commented Jan 23, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.88%. Comparing base (ec6ad29) to head (91dadde).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #373   +/-   ##
=======================================
  Coverage   61.88%   61.88%           
=======================================
  Files          53       53           
  Lines        2167     2167           
=======================================
  Hits         1341     1341           
  Misses        826      826           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jodal jodal force-pushed the docker branch 2 times, most recently from 6f8853d to 88555ab Compare June 25, 2024 00:01
@jodal jodal force-pushed the docker branch 8 times, most recently from c420c18 to befa81f Compare December 29, 2024 20:42
@jodal jodal force-pushed the docker branch 2 times, most recently from 18f1668 to b756f6d Compare February 17, 2025 11:57
@fuzzy76
Copy link

fuzzy76 commented Oct 31, 2025

Is there anything in particular holding this up?

@jodal
Copy link
Owner Author

jodal commented Nov 2, 2025

No, not really. comics development happens quite sporadically for me these days, and so far I've been happy with modernizing/getting closer to run it as a container. I still run it the good old way with nginx in front and systemd keeping gunicorn alive.

Do you run a comics instance yourself?

@fuzzy76
Copy link

fuzzy76 commented Nov 3, 2025

I do not, as I use comics.io. But running it through Docker would make it easier for me to contribute new parsers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants