1
0
forked from suse-edge/Factory
Go to file
Marco Chiappero eecd30e90d Update httpd.conf to bind to IPv4 and/or IPv6 sockets
Enable the use of individual IPv4 and IPv6 sockets when the respective
IP is detected and LISTEN_ALL_INTERFACES is not set to true. This allows
to correctly bind to both the IPv4 and IPv6 addresses found and not just
one of them.

Signed-off-by: Marco Chiappero <marco.chiappero@suse.com>
2025-08-04 14:47:42 +00:00
2025-02-20 11:15:35 +01:00
2025-04-30 16:42:54 +02:00
2024-10-22 16:43:48 +02:00
2025-05-07 20:03:45 +03:00
2025-04-30 16:42:54 +02:00
2024-10-22 12:26:29 +02:00
2024-10-22 16:14:46 +02:00
2025-05-15 14:06:32 +02:00
2025-06-10 11:12:08 +02:00
2024-10-22 16:14:46 +02:00
2024-10-22 16:43:48 +02:00
2025-02-24 11:21:52 +01:00
2025-06-09 17:25:39 +03:00
2025-04-30 16:42:54 +02:00
2025-07-29 11:01:52 +02:00
2025-04-30 16:42:54 +02:00
2024-10-17 14:01:57 +02:00
2025-02-24 11:21:52 +01:00
2025-07-24 13:44:12 +02:00
2025-06-09 11:22:25 +03:00
2024-10-22 16:43:48 +02:00
2025-02-24 15:44:23 +01:00

Factory

Contains the definition of the packages built on OBS for the SUSE Edge Solution (WIP)

This repository is linked to an OBS project: https://build.opensuse.org/project/show/isv:SUSE:Edge:Factory Every directory in this repository represents a package in that OBS project, those should be synced automatically from this repository.

Testing a fork or a development branch

You can create a project in your home space in OBS, use the same prjconf as the one of "isv:SUSE:Edge:Factory", and copy the repositories part of the metadata (adjust self references). Then add a scmsync stanza to your metadata like this (adjust repository path and branch):

<scmsync>https://src.opensuse.org/suse-edge/Factory#main</scmsync>

This is done automatically for any PR filed against this repository.

Cutting a release version branch

  1. Do the appropriate git branch command
  2. Change the project path in .obs/common.py file (e.g. from isv:SUSE:Edge:Factory to isv:SUSE:Edge:3.2)
  3. Change the branch reference in .obs/common.py file (e.g. from main to 3.2)
  4. Commit those changes to the new branch and push the new branch
  5. Go take a few cups of coffee/tea/mate/... while waiting for OBS to build everything
  6. Once built do an osc release of the project for it to be copied over in the ToTest section
  7. Hand over to QA to test whatever is in ToTest. (You can continue to work on the base branch if needed meanwhile)
Description
No description provided
Readme 280 MiB
Languages
Dockerfile 30.2%
Smarty 24.5%
Shell 23.3%
Jinja 17%
Python 3.2%
Other 1.8%