in app configuration page
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp, docker
- Domain
- full-stack
Research direction
The configuration lives in the Settings.yaml file under config/, which holds immichServerUrl, ApiKey and Albums. Start by finding where that file is read at startup and where the server and frontend are wired together. Done means a /config page can view and save those values, and the container still runs from the same settings after a restart. The issue leaves the design open, so confirm the approach with maintainers before writing code.
Written by the indexing model from the issue text.
Description
Description
Hi,
currently for making immichframe working it's required editing immichframe Settings file for adding the account data.
as you know:
step 1: run immich container > create api key
step 2: create immichframe/config/Settings.yaml with the account items including the immichServerUrl/ApiKey/Albums > run immichframe container
is there a way to make it easier by creating in app easy configuration page instead of this 2 steps?
Use Case
by creating this in app configuration page
i could run both containers on one shot with docker-compose.
and after both up - i can create the apikey and open immichframe configuration UI and add/change the accounts items
even more:
app will be more friendly. by not giving user on the first page:
Details
user can navigate maybe to /config for making changes
Pre-Submission Checklist
-
This is a feature request and not a bug report
-
I have checked for related issues and checked the documentation
- Dominant language
- C#
- Stars
- 2.4k
- Forks
- 121
- Avg merge
- 18d 20h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from immichFrame/ImmichFrame
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
immichFrame/ImmichFrame#735 ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 56/100
immichFrame/ImmichFrame#733 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
immichFrame/ImmichFrame#732 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 22/100
immichFrame/ImmichFrame#731 · 1 reaction ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
immichFrame/ImmichFrame#729 ·
All issues in immichFrame/ImmichFrame
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 74/100
dotnet/EntityFramework.Docs#5521 ·
Maintainers usually reply within 1 day
-
Feature needs response
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Adyen/adyen-dotnet-api-library#1907 ·
Maintainers usually reply within 5 days
-
AwsWrapperDataReader does not forward GetFieldValue<T>, breaking DateTimeOffset/timestamptz readsPossibly taken @kvechkanov claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
dimitar-radenkov/Pointframe#318 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DotHarness/dotcraft#546 ·
Maintainers usually reply within 1 day