Skip to content

Remove docker compose build instruction and add more compose info - #341

Merged
sim51 merged 1 commit into
gephi:mainfrom
abitrolly:compose-ux
Sep 14, 2026
Merged

sim51 merged 1 commit into
gephi:mainfrom
abitrolly:compose-ux

Conversation

@abitrolly

Copy link
Copy Markdown
Contributor

README.md mentions docker compose build command that doesn't function.

$ docker compose build
WARN[0000] No services to build

The PR removes it and adds a link to http://localhost:5173/gephi-lite/ where dev instance would be available after the app is up.

Pull request type

Check the type of change your PR introduces:

  • Bugfix
  • Feature
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • Documentation content changes
  • Other (please describe):

NOTE: Try to limit your pull request to one type, submit multiple pull requests if needed.

What is the current behavior?

Issue Number: N/A

NOTE: Describe the current behavior that you are modifying, or link to a relevant issue.

What is the new behavior?

NOTE: Describe the behavior or changes that are being added by this PR.

Other information

NOTE: Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

    $ docker compose build
    WARN[0000] No services to build
@sim51
sim51 merged commit a3ebce5 into gephi:main Sep 14, 2026
@abitrolly

abitrolly commented Sep 14, 2026

Copy link
Copy Markdown
Contributor Author

@sim51 thanks!

I thought the repo is not active, but it is not true main...dev 😁

I would definitely do PR against dev if I knew about it. What do you think about making dev the default branch? And let people use tags if they want stable versions?

@abitrolly
abitrolly deleted the compose-ux branch September 14, 2026 15:29
@sim51

sim51 commented Sep 14, 2026

Copy link
Copy Markdown
Collaborator

The repo is still active and under development.
But we have a feature that still requires refinement (in dev & design) which block the release...
Moreover, the dev of Sigma v4 has also taken big effort from one of team member

About the dev vs main branch, I saw the issue when I wanted to merge your PR.
Will ask the team to see if there is a problem to change the default branch on GH.

@abitrolly

Copy link
Copy Markdown
Contributor Author

Moreover, the dev of Sigma v4 has also taken big effort from one of team member

Wow, https://v4.sigmajs.org/ is nice pointer!

May help with https://discussion.fedoraproject.org/t/interactive-package-dependency-tree/201981

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.

2 participants