ParadiseSS13 / ParadiseSS13/CoreInfrastructure
Move away from Apache
Open
Nobody has claimed this yet.
Future Plans
Half Done
- Dominant language
- Shell
- Stars
- 1
- Forks
- 1
- Avg merge
- 7h 33m
- Merged PRs (30d)
- 1
Description
If we can the forums, apache can be moved away from.
At the moment, we're kinda beholden to it
- I enjoy .htaccess too much - sue me
- I have a custom apache plugin that restricts access based on forum groups even for proxied sites - and we make heavy use of this for Kibana
However
- I can live without this if I absolutely have to
I can recode this to work as an nginx plugin, maybeNot needed, nginxPM does this natively with authentik
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing the existing Apache and .htaccess setup, including the custom access plugin used for Kibana and proxied sites. Assess the forum migration and the proposed nginxPM/authentik path; done means the core services no longer depend on Apache while retaining the required forum-group access restrictions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- apache, nginx
- Domain
- authentication, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100