Skip to content

Feat Req: Add Support For Pychrubile & Docker #4

@JeelDobariya38

Description

@JeelDobariya38

Overview

We look for make it convenient for user to install this server and use it. We provide multiple ways such that user can use the way that suits them. like Home Labs user can use docker and non tech use one can use pychrubile ways. Also add a CI-CD support.

Tasks

  • Add Support for Docker.
  • Add Support for Pychrubile.
  • Add Support for CI-CD.

Docker Support.

For docker, make a docker image with python-slim 3.13 (i-guess). that can run the fastapi api server. push & commit docker file. try add compose file also

I am not sure wether to add nginx for proxy or not. I mean that would something that require for handle https i guess. i am not sure wether to let use configure nginx or give it based config and add it in docker compose.

we use gchr.io (github) to host container image. we will try out best to based off our organisation mostly to github. and not use other platforms.

Pychrubile Support.

For pychrubile, add support and provide nice good enough config. and push it to github. if possible try add support for auto update or let use post when update is available. also we neee provide pychrubile support for multiple platform I mean windows, macos and linux.. i am not so concerned about macos. but we need sure provide support for windows as it mostly use world wide by users and linux as cloud like aws run it.

CI-CD Support

For ci-cd, make a one workflow, that has two trigger (when release is published not just created and it the workflow can trigger manually).

We are not run it on each push as we are free org on github, and github has limits on run workflow.

Also see this workflow as a building stuff remotely and not as automation.

the workflow should "chrubile up" and "containerise" the app. and upload the necessary asset as artficats. then this assets are manually move to release with developer assistants if need i guess....

Steps.

  • tell me you like work on this issue by comment on this issue.
  • for organization members no need fork repo you directly create a branch [yourname]-dev and push changes directly to this repo. & then submit pr to main
  • cordinate this changes in small piece if possible like in multiple commits.
  • 2 or 3 seperate prs one for docker, one for pychrubile & ci-cd.

Metadata

Metadata

Labels

documentationImprovements or additions to documentationenhancementNew feature or request

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions