MySQL SSL connection

Open
#41 12 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
mysql
Domain
documentation

Research direction

Start with the FeedLand server setup instructions and the database section of config.json. Confirm the MySQL connection options described in the linked mysql package documentation, then document the ssl object and rejectUnauthorized setting for SSL-required providers such as PlanetScale. Done means a new installer can find and apply the configuration without searching elsewhere.

Written by the indexing model from the issue text.

Description

I just did a new installation of my FeedLand instance. I'm trying out PlanetScale as my database provider (they seem to have a generous free plan 😃). They require the database connection be made over SSL, and I wasn't sure how to configure that in config.json. I eventually found the answer in the docs for the npm mysql package (used by davesql to connect to the database). I just needed to add an 'ssl' object to the database section of config.json

"database": {
		"host": "aws.connect.psdb.cloud",
		"port": 3306,
                 …
		"ssl": {
			"rejectUnauthorized": true
			}
		},

I'm not sure whether this is worth adding to the docs or not.

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 Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.