forgejo/docs
32
58
Fork
You've already forked docs
250

updated installation-docker.md file with Podman instructions #820

Merged
fnetX merged 2 commits from j-dominguez9/docs:next into next 2024年09月05日 01:07:14 +02:00
Contributor
Copy link

In my local build, I omitted the localtime and timezone volumes, as those directories didn't exist in my server (Alma Linux), but I left them in the documentation as I wanted to match the yaml file. Obviously feel free to remove/edit any of the elements. Alternatively, please let me know if there's anything else you'd like for me to add. I only added the essentials, but would be happy to add more if it would make sense to do so.

In my local build, I omitted the localtime and timezone volumes, as those directories didn't exist in my server (Alma Linux), but I left them in the documentation as I wanted to match the yaml file. Obviously feel free to remove/edit any of the elements. Alternatively, please let me know if there's anything else you'd like for me to add. I only added the essentials, but would be happy to add more if it would make sense to do so.
Contributor
Copy link

This is a very useful addition

Could you provide a shell script that verify it works as it should, assuming it runs on a freshly installed Debian GNU/Linux bookworm? I'll take care of adding this script to the CI so it verifies it keeps working.

This is a very useful addition ✨ Could you provide a shell script that verify it works as it should, assuming it runs on a freshly installed Debian GNU/Linux bookworm? I'll take care of adding this script to the CI so it verifies it keeps working.

Bookworm is on v4.3.1, which still uses systemd generator.
Quadlet support is from v4.4 - so it's a no go for a script on bookworm.

Also I'm not sure if that's needed... Do we test if docker-compose files work? Because that's basically the same thing.

[Bookworm is on v4.3.1](https://packages.debian.org/bookworm/podman), which still uses systemd generator. [Quadlet support is from v4.4](https://www.redhat.com/sysadmin/quadlet-podman) - so it's a no go for a script on bookworm. Also I'm not sure if that's needed... Do we test if docker-compose files work? Because that's basically the same thing.
Contributor
Copy link

In that case it does not seem possible to have an automated test. @j-dominguez9 can you add the Operating System / podman requirements in this section?

In that case it does not seem possible to have an automated test. @j-dominguez9 can you add the Operating System / podman requirements in this section?
Author
Contributor
Copy link

@earl-warren yes, of course. Will do that today! I can test it on Fedora Workstation, Fedora silverblue, and Alma/Rocky Linux to verify it works, but don't have access to a debian-based distro right now. And I don't know if testing it on a deb container would make sense, since weird stuff starts happening when you run a container inside a container.

@earl-warren yes, of course. Will do that today! I can test it on Fedora Workstation, Fedora silverblue, and Alma/Rocky Linux to verify it works, but don't have access to a debian-based distro right now. And I don't know if testing it on a deb container would make sense, since weird stuff starts happening when you run a container inside a container.
Author
Contributor
Copy link

I did have to remove the timezone and localtime volumes for it to work on rpm-based setups. Don't know if that will remain the case for deb-based setups, as well. Also, added a mention of SSH testing, as I struggled with that when setting mine up (still haven't fully figured out how to point git to a different port), but happy to remove it, if you think it adds unnecessary information.

I did have to remove the timezone and localtime volumes for it to work on rpm-based setups. Don't know if that will remain the case for deb-based setups, as well. Also, added a mention of SSH testing, as I struggled with that when setting mine up (still haven't fully figured out how to point git to a different port), but happy to remove it, if you think it adds unnecessary information.
Contributor
Copy link

@thefox I'll leave the review to you as I don't know podman myself.

@thefox I'll leave the review to you as I don't know podman myself.
Ghost approved these changes 2024年08月26日 12:24:32 +02:00
Ghost left a comment
Copy link

Looks good, Just the CI fix is required

Looks good, Just the CI fix is required
Contributor
Copy link

@j-dominguez9 could you please fix the lint issues so it can be merged?

@j-dominguez9 could you please fix the lint issues so it can be merged?
fnetX force-pushed next from 71807a980b
Some checks failed
pr / preview (pull_request) Failing after 22s
to 0037803cca
All checks were successful
pr / preview (pull_request) Successful in 1m0s
backport / backport (pull_request) Successful in 1s
2024年09月05日 01:02:42 +02:00
Compare
fnetX force-pushed next from 0037803cca
All checks were successful
pr / preview (pull_request) Successful in 1m0s
backport / backport (pull_request) Successful in 1s
to 5ffaadde9a
Some checks failed
pr / preview (pull_request) Failing after 23s
2024年09月05日 01:03:24 +02:00
Compare
Owner
Copy link

Sorry for the noise ... Compare the actual change

Sorry for the noise ... [Compare the actual change](https://codeberg.org/forgejo/docs/compare/71807a980bb992be76c1047c286cb8e3be5a2516..5ffaadde9a02a6a5f0ec9644cf25e30c3ef73898)
fnetX force-pushed next from 5ffaadde9a
Some checks failed
pr / preview (pull_request) Failing after 23s
to 3383d08f02
All checks were successful
pr / preview (pull_request) Successful in 59s
backport / backport (pull_request) Successful in 1s
2024年09月05日 01:05:06 +02:00
Compare
fnetX scheduled this pull request to auto merge when all checks succeed 2024年09月05日 01:06:02 +02:00
Collaborator
Copy link
Preview ready: https://forgejo.codeberg.page/@docs_pull_820/
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404
Broken links or missing content
backport/v1.19
Changes which should be backported to the v1.19 docs

Archived

backport/v1.20
Changes which should be backported to the v1.20 docs

Archived

backport/v1.21
Changes which should be backported to the v1.21 docs

Archived

backport/v10.0
Automated backport to v10.0

Archived

backport/v11.0
Automated backport to v11.0
backport/v12.0
Automated backport to v12.0

Archived

backport/v13.0
Automated backport to v13.0

Archived

backport/v14.0
Automated backport to v14.0

Archived

backport/v15.0
Automated backport to v15.0
backport/v16.0
Automated backport to v16.0
backport/v7.0
Automated backport to the v7.0 docs

Archived

backport/v8.0
Automated backport to the v8.0 docs

Archived

backport/v9.0
Automated backport to the v9.0 docs

Archived

good first issue
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta
Tooling and processes for maintaining the docs
new docs
Content to be added to the documentation

Archived

User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/docs!820
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "j-dominguez9/docs:next"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?