-
Notifications
You must be signed in to change notification settings - Fork 358
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
Add guix-forge #226
Comments
Regarding the demo being on the Internet Archive that's just a video, could you consider moving it to an actual demo of the software on your website? If that's not feasible, then that's fine. other then that, I looked through and couldn't seem to find a stable release. only the repository itself has a release nor there's a web ui, only CLI. Is there a stable tag, etc for the user to use instead of having to pull from the main branch everytime? Considering these questions, i shall await a response. Thanks |
Hi there! I am the maintainer of the guix-forge project. Thanks, @jgarte, for contributing it to awesome-selfhosted! I could embed the Internet Archive video in the guix-forge home page. Would that help? About releases: guix-forge is a channel for GNU Guix. See https://guix.gnu.org/manual/en/html_node/Channels.html Guix channels don't usually have releases or tags, and it is customary for users to pull from the main branch everytime using guix pull. |
Also, guix-forge is a CLI tool. It is meant to install and maintain (on your self-hosted server) other tools such as laminar CI, cgit, etc. that come with a web UI. |
@nodiscc what do you think of this? |
I meant, is there a plan to create a demo like laminar CI, cgit, etc for people to try out before installing on their own devices? sorta like other FOSS software that's time based or limited in functionality. |
I cant remember where the source is however demos should be interactive. Not videos. Therefore the video demo should be removed. |
😕 terrible practice for multiple reasons (no warning for breaking changes, software changing behavior on upgrades without admin approval, etc). The first commit dates back to 2021 but there is no way to know which version is the first "usable/working" one. I think the best course of action, is to tag the current version as
This is correct, we used to have this guideline written down in https://github.com/awesome-selfhosted/awesome-selfhosted but I can't find it here. https://github.com/awesome-selfhosted/awesome-selfhosted/blob/ae5aa43f54f46e75ed522a065d3133401ed736b2/.github/PULL_REQUEST_TEMPLATE.md
If someone wants to take the time to add it back to https://github.com/awesome-selfhosted/awesome-selfhosted-data/blob/master/.github/PULL_REQUEST_TEMPLATE.md it would be appreciated. |
😕 terrible practice for multiple reasons (no warning for
breaking changes, software changing behavior on upgrades without admin
approval, etc).
The first commit dates back to 2021 but there is no way to know which
version is the first "usable/working" one. I think the best course of
action, is to tag the current version as `1.0.0` and wait for 4 months
before submitting it.
Your point is well taken. But, guix-forge is a Guix channel, not regular
software with tagged releases and release tarballs. Users of Guix
channels don't usually download specific tagged releases. They run a
`guix pull` and expect to get the latest.
Nevertheless, I see your point. Some users may benefit from having more
stable tagged releases. So, I have now started using them. To start
with, here's a v0.1.0 tag:
https://git.systemreboot.net/guix-forge/tag/?h=v0.1.0
> demos should be interactive.
As of this moment, guix-forge does not have any demo instances with
dummy data. But, there are two real world instances of guix-forge:
systemreboot.net:
- https://ci.systemreboot.net/
- https://git.systemreboot.net/
genenetwork.org:
- https://ci.genenetwork.org/
- https://git.genenetwork.org/
The above laminar and cgit instances are managed by guix-forge. But, it
is hard/impossible to tell simply by looking at these pages. There is no
branding or landing page as such. Perhaps in the future.
|
To be revisited: |
To ensure your issue is dealt with swiftly, please check the following (check the boxes
[x]
):The text was updated successfully, but these errors were encountered: