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

Multiple fixes to make Podman work and simplify the setup #577

Merged
merged 11 commits into from
Sep 21, 2023

Conversation

aparcar
Copy link
Member

@aparcar aparcar commented Sep 20, 2023

This PR touches multiples areas, at its core it should make running an instance easier. Let's see how it goes.

Initially I thought it'd be smart to have both separated, however there
was never a real reason why. Merge both into PUBLIC_PATH.

Signed-off-by: Paul Spooren <mail@aparcar.org>
Signed-off-by: Paul Spooren <mail@aparcar.org>
Signed-off-by: Paul Spooren <mail@aparcar.org>
While at it, cleanup older releases

Signed-off-by: Paul Spooren <mail@aparcar.org>
The default path is different on most machines and I didn't find a
reliable way yet to set it automatically. User need to set
`CONTAINER_HOST` to make things work.

Signed-off-by: Paul Spooren <mail@aparcar.org>
Signed-off-by: Paul Spooren <mail@aparcar.org>
This surprisingly never came up since most profiles are different from
one another, however this would cause issues where multiple target use
i.e. "generic" as profile.

Signed-off-by: Paul Spooren <mail@aparcar.org>
Instead of exporting anything, you may just run `flask run`

Signed-off-by: Paul Spooren <mail@aparcar.org>
Previously it was REDIS_CONN which would store the actual connection,
now just store the connection string.

Signed-off-by: Paul Spooren <mail@aparcar.org>
By setting `CONTAINER_SOCK` prior to running `podman-compose up` the
socket path is passed into the worker container and `CONTAINER_HOST` is
automatically set. The workers then use `podman` to build images instead
of running it *bare metal*. One should set `PUBLIC_PATH`, too, which
points to the place where to store images and json files.

Signed-off-by: Paul Spooren <mail@aparcar.org>
@codecov
Copy link

codecov bot commented Sep 20, 2023

Codecov Report

Patch coverage: 85.18% and project coverage change: +0.15% 🎉

Comparison is base (3ef4757) 86.53% compared to head (97a5d12) 86.69%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #577      +/-   ##
==========================================
+ Coverage   86.53%   86.69%   +0.15%     
==========================================
  Files          13       13              
  Lines         936      932       -4     
==========================================
- Hits          810      808       -2     
+ Misses        126      124       -2     
Files Changed Coverage Δ
asu/common.py 94.73% <ø> (ø)
tests/conftest.py 94.52% <ø> (ø)
asu/asu.py 81.53% <50.00%> (ø)
asu/api.py 67.72% <66.66%> (ø)
asu/build.py 81.65% <81.81%> (+0.74%) ⬆️
asu/janitor.py 70.47% <100.00%> (+0.28%) ⬆️
tests/test_api.py 100.00% <100.00%> (ø)
tests/test_common.py 100.00% <100.00%> (+1.72%) ⬆️
tests/test_factory.py 100.00% <100.00%> (ø)
tests/test_janitor.py 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

A webserver should be deployed outside the rootless docker compose file.
For testing files are server via Python anyway.

Signed-off-by: Paul Spooren <mail@aparcar.org>
@aparcar aparcar merged commit b994d15 into openwrt:main Sep 21, 2023
4 of 5 checks passed
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.

1 participant