Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Add support for Fossil VCS #1865

Open
louis77 opened this issue Aug 30, 2023 · 1 comment
Open

[Feature] Add support for Fossil VCS #1865

louis77 opened this issue Aug 30, 2023 · 1 comment

Comments

@louis77
Copy link

louis77 commented Aug 30, 2023

The Fossil VCS is becoming increasingly popular as a replacement to Git. VSCode also has an excellent extension to fully integrate Fossil into the Source Control management.

I would like the CapRover CLI to add support to deploy Fossil-based repositories when using the caprover deploy command. Thanks to Fossil's Git-export capabilities, this could easily be implemented on top of the existing Git-based workflow.

This is how it could be done:

  1. When caprover deploy is run, it checks if the current directory is a Git repository.
  2. If not, check if it is a Fossil-based working tree, i.e. by calling fossil info
  3. If (2) applies, CapRover can call the fossil git export command, which creates a Git clone of the current Fossil working tree
  4. From there, CapRover can go on and do the usual Git workflow (compressing the repo into a tar etc.).
  5. Since fossil always exports to a Git branch called trunk, Caprover could just use that and omit the usual branch prompt
  6. The exported version of Git repo could stay, next time caprover deploy is run the Fossil export would be even faster

This way, nothing has to be changed on the server side. It would be purely an added feature of the CLI.

An alternative would be to write a shell script that essentially does exactly that:

  1. Do a Fossil->Git export
  2. Run caprover deploy
@khromov
Copy link

khromov commented Sep 3, 2023

Would the most straightforward alternative perhaps be to use a CI tool like Jenkins or CircleCI to handle the Fossil-specific stuff and then run caprover deploy once you have a proper Git repo?

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

No branches or pull requests

3 participants