New feature: the config.js option, new daveappserver release

Open
#9 12 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

The issue discusses loading config.js instead of config.json from feedland.js and updating daveappserver to v0.6.10, but it names no target change or test. Start by reading the configuration-loading entry point and the account, login, and identity-related operations mentioned in the report. Done would require a concrete requested change and tests or reproducible checks, which this issue does not define.

Written by the indexing model from the issue text.

Description

Good morning feedlandinstallers! ;-)

I made a change to FeedLand today to create another option for configuring FeedLand at startup.

The config.js option

Now, if you place a config.js file in the same folder as feedland.js, we will load that instead of config.json, via a JavaScript require call.

That means you can have code run to create the object, which allows it to be part of a more complex hosting environment.

So for example, config.js could contain this code:

module.exports = {
   myName: "Bull Mancuso",
   myMotto: "Not on your life."
   }

Then after feedland.js loads config will have two new values -- myName and myMotto.

Obviously you can have any code generate that object. You could get it from a file you access over the net or get info from a database or the web server, or OS, or where ever. It's more power than config.json, and more complexity.

For small installations however, config.json is the way to go.

New daveappserver

As you may know I've been working this week on creating a new version of Drummer that does not depend on Twitter identity and uses HTTPS.

In doing this work, I had to make changes to daveappserver, which FeedLand also uses. So there is a chance of breakage here. Please update your feedland installation to get the new daveappserver, v0.6.10, and report any problems.

If present, I would expect them to be in creating new accounts, logging on to existing accounts, and any operation that involves identity (subscribing to a feed, for example).

I'm going back to work on Drummer today, but will keep my eye on this repo as well.

I feel things are winding up nicely now. And thanks for your help with FeedLand. 😄

Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
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 Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.