Debugging the install process

Open
#57 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
devops, documentation

Research direction

Start by reviewing the repository's existing FeedLand server setup instructions and reproducing the installation from a clean environment. Trace the reported feedId-related problems and record each fix or prerequisite in the instructions. Done means a new user can follow the documented process to run their own FeedLand server.

Written by the indexing model from the issue text.

Description

i tried setting up a new feedland, and hit problems that seem to be related to feedId stuff, perhaps other stuff.

i was worried about this, that the changes i was making were being tested only on existing installations.

now i want to be sure people can run their own feedlands, so i'm going to have to get through this and be left with instructions that work.

i'll post notes here as i discover and hopefully fix problems.

Dominant language
HTML
Stars
11
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/feedlandInstall

All issues in scripting/feedlandInstall

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.