24 |
27 |
32 |
33 |
34 |
--------------------------------------------------------------------------------
/code/pingserver.js:
--------------------------------------------------------------------------------
1 | /* This script handles requests that come into ping.1999.io
2 | It maintains a JSON file in the same directory as the script that counts updates
3 | for each RSS file maintained by each of the participating 1999 servers.
4 |
5 | It's designed to be run by the PagePark web server, but could be modified to be run
6 | in any web server that can run JS scripts.
7 |
8 | 4/4/16; 10:45:25 AM by DW
9 | */
10 | var urlFeed = parsedUrl.query.urlFeed;
11 | if (urlFeed !== undefined) {
12 | var now = new Date (), fname = "domains/ping.1999.io/pingers.json";
13 | fs.readFile (fname, function (err, data) {
14 | var jstruct = new Object ();
15 | if (!err) {
16 | jstruct = JSON.parse (data.toString ());
17 | }
18 | if (jstruct [urlFeed] === undefined) {
19 | jstruct [urlFeed] = {
20 | ct: 1,
21 | when: now
22 | }
23 | }
24 | else {
25 | jstruct [urlFeed].ct++;
26 | jstruct [urlFeed].when = now
27 | }
28 | fs.writeFile (fname, JSON.stringify (jstruct, undefined, 4));
29 | });
30 | }
31 | "Thanks for the ping!";
32 |
--------------------------------------------------------------------------------
/code/readchatlog.js:
--------------------------------------------------------------------------------
1 | var myProductName = "Read ChatLog", myVerion = "0.40a";
2 |
3 | /* This script reads a chatLog.json file
4 | We write the titles of each of the posts to the console.
5 | Each line begins with the ID of the post, followed by the title, followed by the date and time it was posted.
6 | The only point here is to prime the pump a little, to get people thinking of apps they might build off the chatLog.json files.
7 |
8 | 4/16/16 by DW
9 | */
10 |
11 | var urlMyChatLog = "http://friends.farm/users/davewiner/chatLog.json";
12 | var request = require ("request");
13 |
14 | function getTitle (item) {
15 | if ((item.payload !== undefined) && (item.payload.title !== undefined)) {
16 | return (item.payload.title);
17 | }
18 | return ("");
19 | }
20 | function getUrlRendering (item) {
21 | if ((item.payload !== undefined) && (item.payload.urlRendering !== undefined)) {
22 | return (item.payload.urlRendering);
23 | }
24 | return ("");
25 | }
26 | function getImage (item) {
27 | if ((item.payload !== undefined) && (item.payload.image !== undefined)) {
28 | return ("[%title%]
25 | [%bodytext%]
26 |
130 |
136 |
141 |
142 |
143 |
--------------------------------------------------------------------------------
/code/websocketdemo.html:
--------------------------------------------------------------------------------
1 |
2 |
3 | Template editor for 1999.io
131 |
132 |
133 |
134 |
135 |
218 |
219 |
220 |
221 |
237 |
242 |
243 |
244 |
--------------------------------------------------------------------------------
/defaults/menubar.html:
--------------------------------------------------------------------------------
1 |
6 |
39 |
--------------------------------------------------------------------------------
/defaults/menubar.opml:
--------------------------------------------------------------------------------
1 |
2 | WebSocket client for 1999.io
222 |This app hooks up with the 1999.io server using WebSockets.
223 |Every time a message is created or updated in the chatlog, the socket returns with the content of that message.
224 |For more info, see this blog post. And the source is available, of course, on GitHub.
225 |Here's some real-time data about the server.
226 |Number of items in myChatlogCopy: . 227 |
Number of messages received from server: 0. 228 |
We have been waiting seconds for an update.. 229 |
230 |
235 |
236 | How long we waited for the last update: 0 secs. 231 |
The text returned from the last call:
232 |233 |234 |
37 |
38 |
45 |
50 |
51 |
52 |
--------------------------------------------------------------------------------
/defaults/template.opml:
--------------------------------------------------------------------------------
1 |
2 | [%title%]
39 |
40 | [%text%]
41 |
42 |
44 | sudo docker run -p 80:1999 -p 2000:2000 --name nodestorage -d --restart=unless-stopped \ 28 | 29 | -e "myDomain=oakland.myserver.com" \ 30 | 31 | -e "twitterConsumerKey=12345" \ 32 | 33 | -e "twitterConsumerSecret=67890" \ 34 | 35 | davew/nodestorage:latest 36 | 37 |38 | 39 | After running the command you should be able to access your server through http://oakland.myserver.com/. 40 | 41 | #### Frequent commands 42 | 43 | sudo docker images -- list all the images you have installed on this machine 44 | 45 | sudo docker ps -- list the containers 46 | 47 | sudo docker stop nodestorage -- stop the nodestorage container 48 | 49 | sudo docker rm nodestorage -- remove the nodestorage container 50 | 51 | #### Pointers 52 | 53 | Amazon has a Docker service. 54 | 55 | Here's a cheat sheet website for Docker commands. 56 | 57 | CoreOS is a Linux distribution built around containers. 58 | 59 | #### Where's the source? 60 | 61 | Here's the repository for the Docker version. 62 | 63 | The JavaScript files are the same as the main project. 64 | 65 | The only difference is there's a Dockerfile in the top level of the repo, and a docker folder with scripts and data. 66 | 67 | The two projects are kept in sync by my build system. 68 | 69 | #### Questions 70 | 71 | Get help on the 1999-server mail list. 72 | 73 | -------------------------------------------------------------------------------- /docs/domains.md: -------------------------------------------------------------------------------- 1 | ## Mapping a domain to a blog 2 | 3 | You can set up a server, through config.json, to map domains to blogs. 4 | 5 | #### Example 6 | 7 | Here's an example config.json set up to map trump.1999.io and blog.1999.io to their respective sites. 8 | 9 | #### How to 10 | 11 | Add a new top-level object in config.json called domains. It contains strings. 12 | 13 | The name of each string is a domain to be mapped. 14 | 15 | The value of each string is the path to the public file the domain points to. 16 | 17 | #### How it works 18 | 19 | The conversion happens in both directions. When a client requests a page using the domain name, we fetch the content at the location indicated by the value. 20 | 21 | And if there's a reference to a page that's accessible through the domain map, we redirect to the short version. 22 | 23 | -------------------------------------------------------------------------------- /docs/ec2.md: -------------------------------------------------------------------------------- 1 | ## EC2 machine image for 1999 server 2 | 3 | Now you can launch a 1999.io server from an Amazon AMI. 4 | 5 | It's even easier than the basic Ubuntu setup, because I've done most of the installation for you. It just needs a few bits and you're ready to go. 6 | 7 | Note: These are not poet-level instructions, they're for people with a little experience setting up an AMI and DNS. 8 | 9 | #### How to 10 | 11 | The AMI is ami-abcd2fc6. It's public. 12 | 13 | It can be a micro instance. And it should qualify for the free tier, meaning if you're new to AWS you can run it for free for a year. 14 | 15 | These ports should be open -- 22, 80, 81, 1999, 2000. 16 | 17 | You should assign a domain to the IP address allocated for the server. That will be the value for myDomain in config.json. 18 | 19 | Once the instance is running, edit config.json, as explained in the howto, change myDomain, twitterConsumerKey and twitterConsumerSecret as explained in the setup howto. (You don't have to create it, it's already there.) 20 | 21 | Map port 80 to port 1999. Here's the magic incantation that does that: 22 | 23 |
sudo iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 199924 | 25 | -------------------------------------------------------------------------------- /docs/homepage.md: -------------------------------------------------------------------------------- 1 | ## How to customize the editor 2 | 3 | If you run your own 1999 server you can customize the experience for people using the 1999 editor by adding an object to your config.json file. 4 | 5 | These customizations are totally optional. 6 | 7 | #### An example 8 | 9 | Here's an example config.json that contains a homePage object. 10 | 11 | Two items are specified in that object, productnameForDisplay and urlPageTemplate. 12 | 13 | #### productnameForDisplay 14 | 15 | This sets the string that appears in the upper left corner of the editor. 16 | 17 | I've set it to BloatWare for my test server. Here's a screen shot showing what that looks like. 18 | 19 | If you're hosting blogs for other people, you might want to change that to the name of your organization. 20 | 21 | #### urlPageTemplate 22 | 23 | This sets the address of the default template used for rendering pages. 24 | 25 | It must be the address of a plain text file containing the HTML code with macros for the template file. 26 | 27 | It can be a local URL on your server, as shown in the example. I put the file in publicFiles/data/mytemplate.html. 28 | 29 | But you don't have to put it on your server, you can put it anywhere that's publicly accessible by your users' machines. 30 | 31 | If the user designs their own template it overrides this choice. It's only used when the user has not customized their template, or we can't read the user's template. 32 | 33 | #### How to test 34 | 35 | If you want to experiment with the urlPageTemplate feature, and have already edited the template using the outliner, and you're running your own server... 36 | 37 | 1. Open your sub-folder of the publicFiles folder on the server. 38 | 39 | 2. Delete template.opml. 40 | 41 | Here's a screen shot showing the location of template.opml in my server folder. 42 | 43 | Now when 1999.io renders your pages it will use the default template as specified in your homePage object. 44 | 45 | #### googleAnalyticsAccount 46 | 47 | Sets the default Google Analytics account for blogs hosted on your server. 48 | 49 | Here's an example config.json that illustrates. 50 | 51 | The feature is fully explained in a post on the 1999.io blog. 52 | 53 | #### urlHomePageIntroText 54 | 55 | When the user accesses the home page of your site, without being logged in, a message is displayed that says "Please sign on to Twitter to access your stuff." 56 | 57 | You may want to say more. This option lets you control the text and the layout of the text that the user sees. 58 | 59 | Here's an example config.json that illustrates, and this is what it looks like when you visit. 60 | 61 | Do a view-source on the page we link to from the urlHomePageIntroText value. You can see that we put the text inside the same div that the default text is in, and we center it, as the default text is centered. You can lay it out any way you want, or stay with this way of formatting. 62 | 63 | If you have more to say and want to link to other pages, you probably should come up with a better layout for text reading. 64 | 65 | -------------------------------------------------------------------------------- /docs/macros.md: -------------------------------------------------------------------------------- 1 | ## Macros 2 | 3 | When 1999 renders a page, as part of the process, it passes the text through the pagetable. 4 | 5 | The pagetable is a JavaScript object with names and values. For example, pagetable.title might have the value Test post or pagetable.authorFacebookAccount might be bull.mancuso. 6 | 7 | As the page is rendered, [%title%] would be replaced with Test post, and [%authorFacebookAccount%] would be replaced with bull.mancuso. 8 | 9 | Here's a snapshot of the pagetable for a page I rendered on my test server. Any of those values could be used in the template for the page. 10 | 11 | #### Where the values come from 12 | 13 | The pagetable is built from a variety of sources. Some of them come from the server, like the name of the product, and the address of the API server and WebSocket server. Some of the values are stats kept by the editor, such as ctStartups, or prefs such as flAutoSave. Most of these wouldn't be too useful in a template. 14 | 15 | Some of the values come from Twitter, when we authenticate. For example, personName and profileImageUrl. 16 | 17 | #### The pagetable at runtime 18 | 19 | The pagetable is also available to JavaScript code running in the rendered page. It's a global called pagetable. 20 | 21 | This is the information the default page code uses to put up the prev and next arrows, and the elements in the footer. 22 | 23 | If you open up the JavaScript console you can inspect it. Or you can type viewPagetable () to get a JSONified rendering of the table. 24 | 25 | You'll see that there's more information accessible here, because the pagetable contains objects. Information about the prev and next story pages. All the information about the item behind the rendering as an object. 26 | 27 | Here's a snapshot of the runtime version of the pagetable for the example page. 28 | 29 | #### Historic note 30 | 31 | The pagetable has been in all my web CMSes going back to 1996 and the first website framework. 32 | 33 | It works beautifully as a way for values to be passed from the editor through the rendering process and into the page at runtime. 34 | 35 | I haven't ever come up with a better way to do it. ;-) 36 | 37 | -------------------------------------------------------------------------------- /docs/plugins.md: -------------------------------------------------------------------------------- 1 | ## Editor plugins 2 | 3 | I want to make it easy for people to add their own editors to 1999.io, playing various roles. 4 | 5 | The plugins described here appear in the new PlugIns menu in 1999.io. When you choose one of the plugins a new page opens. What's on that page is entirely up to the plugin author. The first plugin I'm releasing is a simple lightweight template editor. 6 | 7 | Plugins talk to the server via the JavaScript API. The user does not have to log in to the plugin because they have access to the same credentials 1999.io has since they run in the same domain. The data is stored in localStorage, but you don't have to worry about that, because you access the server through the API, they already know what to do with the localStorage values. 8 | 9 | Obviously, sysops have to be careful about the plugins they run. 10 | 11 | Key point: The plugins can do anything 1999.io does. It would be possible to write a whole new editor for 1999.io websites. Or write specialized tools that do things that 1999.io does not do. The hope is that, over time, many such plugins will be written. 12 | 13 | #### How to configure 14 | 15 | There's a new top-level section in config.json, plugIns, for configuring the pluglins. Here's an example config.json that has a plugIns section. 16 | 17 | Each plugin has an identifier, which is the name of the sub-object, a value called name, which is what's displayed in the PlugIns menu in 1999.io, and url which is the address of the HTML page for the plugin. 18 | 19 | #### How the plugins are accessed 20 | 21 | Suppose you have a plugin whose identifier is imageEdit, and your server is running on designshop.com. 22 | 23 | Then the address of the plugin would be http://designshop.com/plugin?name=imageEdit 24 | 25 | #### The templateEdit plugin 26 | 27 | The only plugin I'm releasing along with the plugins feature is templateEdit. 28 | 29 | When you choose it from the PlugIns menu, a new page opens with the text of template in the edit box. 30 | 31 | When you click the Update button, the template is saved. This means that all future page builds on this site will flow through this version of the template. 32 | 33 | This is not reversible. You will no longer be able to edit the template using the outline editor in the Main menu in 1999.io. This is a very important point. 34 | 35 | However there is an escape clause. If you have access to the server, you can reverse it by deleting misc/template.html in the user's public folder. 36 | 37 | #### Writing your own plugin 38 | 39 | The source code for the templateEdit plugin is in the code folder in this repo. It's meant to serve as example code for the kinds of things plugins do. 40 | 41 | #### Using plugins in the editor 42 | 43 | Here's a blog post on the 1999 user blog, showing how to access the PlugIns menu in the 1999.io editor. 44 | 45 | #### The Editors menu in 1999.io 46 | 47 | Here's a video that demos the Editors menu in 1999.io. 48 | 49 | This is how you get an editor to appear in that menu, on the server. 50 | 51 | Here's an example config.json that adds one item to the menu, the HTML source editor. 52 | 53 | A few facts about the Editors menu. 54 | 55 | 0. The user must enable the Editors menu in the Misc panel of the Settings dialog. 56 | 57 | 1. They are only activated when the user is editing a post. 58 | 59 | 2. When the command is chosen, the editor, which is just an HTML page, is loaded, and it's provided with parameters about the item through localStorage. 60 | 61 | 3. The user edits the text of the item in the editor, and when they save, it is then sent to the server via the nodeStorage API. Since the editor is served through the same domain as 1999.io, it has access to the Twitter credentials. Obviously you should be careful about installing editors written by other people. 62 | 63 | 4. I've written an example HTML editor, do a view source on this page to see how it works. 64 | 65 | -------------------------------------------------------------------------------- /docs/publicfiles.md: -------------------------------------------------------------------------------- 1 | ## You can put your public files anywhere 2 | 3 | There's a value in config.json called publicFiles that specifies where the server keeps the public files for each user. 4 | 5 | It defaults to publicFiles/ which stores the files in the same folder as the storage.js app, but you can put the files anywhere that can be reached through the file system. 6 | 7 | For example, I set up the server to store the public files on an external hard disk called Broadway in a 1999 folder, in this config.json file. 8 | 9 | A common use-case for this is to store the public files in a folder that's served by a web server like nginx or Apache. Note that you don't have to do this because nodeStorage is also a web server and can serve the files it generates. But there are also good reasons to use different server software. 10 | 11 | If you're moving the files from an existing installation, be sure to copy the files from the original folder to the new place. 12 | 13 | -------------------------------------------------------------------------------- /docs/s3.md: -------------------------------------------------------------------------------- 1 | ## Using Amazon S3 to store data 2 | 3 | You can easily configure the server to store data on Amazon S3. You just have to set up config.json to indicate that you're not using the local filesystem and tell it where on S3 you want to store the public files and the private files. 4 | 5 | #### Your AWS credentials 6 | 7 | You have to set it up so that the AWS library routines can find your credentials. 8 | 9 | Here's a page on the AWS docs site that explains the options. 10 | 11 | #### How to 12 | 13 | Here's a config.json that's set up to work with S3 storage. 14 | 15 | Your account must have the ability to read and write from the locations you're using. 16 | 17 | For the private files it's a good idea to use a bucket that is not accessible over the web, but nodeStorage will work with whatever space you give it, public or private. 18 | 19 | -------------------------------------------------------------------------------- /docs/setup.md: -------------------------------------------------------------------------------- 1 | ## How to set up a 1999.io server on Ubuntu 2 | 3 | 1999.io is a new blogging environment that's fast and easy, and has lots of features no other blogging software has. This doc shows you how to set up a 1999.io server on Ubuntu. 4 | 5 | 6 | 7 | #### Overview 8 | 9 | 0. These instructions are for Ubuntu. Other versions of Linux or Windows or Mac OS will require you to figure out how to install Node.js yourself. 10 | 11 | 1. 1999's server is special configuration of nodeStorage, which can be used to run other software. 12 | 13 | 2. It's written in JavaScript and runs under Node.js. 14 | 15 | 3. We use Twitter for identity, so creating a connection to Twitter is part of the setup process. 16 | 17 | 4. If you want to try out the software before installing you can create a test site on my.1999.io. The usual caveats apply. I can't run these test sites forever, but I have no immediate plans to take it down. The safest bet if you plan to use 1999.io to blog for real is to run your own server. 18 | 19 | 5. There's an Amazon EC2 machine image. If you're setting up a server on EC2, using the image does a bunch of the work for you. 20 | 21 | Dave Winer, May 2016 22 | 23 | #### Install Node.js 24 | 25 |
sudo apt-get update 26 | 27 | sudo apt-get install nodejs 28 | 29 | sudo apt-get install npm 30 | 31 | sudo apt-get install nodejs-legacy32 | 33 | We also install npm, a requirement to run Node apps. 34 | 35 | nodejs-legacy makes it possible to run apps by saying node app.js instead of having to use nodejs, an oddity of Ubuntu. 36 | 37 | #### Install git 38 | 39 |
sudo apt-get install git40 | 41 | I like to install git, because it makes it easy to install nodeStorage from GitHub. 42 | 43 | It's also required for the server to be able to install updates, which it does with git. 44 | 45 | #### Download nodeStorage 46 | 47 | nodeStorage is the name of the 1999 server software. It can be used for other apps. This doc shows you how to set it up for running 1999. 48 | 49 |
git clone https://github.com/scripting/nodestorage.git50 | 51 | #### Install it 52 | 53 | Change into the nodestorage directory you created in the previous step. 54 | 55 |
cd nodestorage 56 | 57 | npm install58 | 59 | #### Create config.json 60 | 61 | Launch your favorite Unix editor. I like nano because I'm a newbie, and it has a nice menu at the bottom of the screen if you don't know the commands. 62 | 63 |
nano config.json64 | 65 | Here's a template for config.json, copy the text, and paste it into nano in your terminal window. 66 | 67 | Now I'm going to go through all the elements step by step, explaining what you have to do to set their values. 68 | 69 | 1. myPort -- enter the number of the port you want to use. Make sure that this port is open in your firewall, if you have one on this server. 70 | 71 | 2. websocketPort -- we use a technology called WebSockets to push updates back to the editing app, and to pages that people are reading. So you must specify a port for the WS server to run on, and as with the main HTTP port, above, it must be open in your firewall. 72 | 73 | 3. myDomain -- enter a domain name that points to this server. If you don't have one, you can enter the IP address of the machine, it will work as well as the domain name. Be sure to include the port you're using in the domain, as shown in the example. 74 | 75 | 4. where -- leave it as-is. It will store the public and private files in sub-folders of the nodestorage folder. 76 | 77 | 6. twitterConsumerKey and twitterConsumerSecret -- I'll explain how to set this up in the next section. For now, leave them as set in the example. The strings are nonsense, just placeholders. 78 | 79 | Save the file by typing Control-O, then exit with Control-X. 80 | 81 | #### Set up your Twitter app 82 | 83 | 1. Go to apps.twitter.com and click Create New App in the upper-right corner. A page with a form appears, asking for details of your app. 84 | 85 | 2. Give your app a name. If it's for your book club, you could call it The Hometown Book Club Blogs. If the name is already being used by someone, choose a different name. For my example I used "My test editor 2789". It was available. ;-) 86 | 87 | 3. The website URL will be the value for myDomain specified in your config.json file, as an HTTP url. From the example, it would be http://1999.bullmancuso.io:1999/ 88 | 89 | 4. The callback URL for nodeStorage instances is the url of the app, as specified in the previous step, followed by "callbackFromTwitter" (don't include the quotes). 90 | 91 | 5. Here's a screen shot of a filled-out Twitter app page. 92 | 93 | 6. If it all worked, you should have a Twitter app set up. Click on the Test OAuth button in the upper-right corner of the page, and it will show you two values, consumer key and consumer secret. 94 | 95 | 7. Open config.json in your editor, and replace the placeholder values for twitterConsumerKey and twitterConsumerSecret with these values and save the file. 96 | 97 | #### Launch nodeStorage 98 | 99 |
node storage.js100 | 101 | #### Test your setup 102 | 103 | 1. Go to the home page of your server. In the example above it would be http://1999.bullmancuso.io:1999/. 104 | 105 | 1. You should see a page a menu on the right edge of the menu bar entitled Sign on here. 106 | 107 | 2. From that menu choose Sign on Twitter... 108 | 109 | 5. You should get the Twitter authorization page. Authorize your app. 110 | 111 | 6. It should send you back to your home page, where you should see an edit box at the top and a few menus. Type some text in the box and click the Post button. 112 | 113 | 7. If it worked, you should see a new post below that. If you click on the wedge you'll see a menu of options for the post. If you click on the Eye icon next to the menu you should see a rendering of the page. 114 | 115 | 9. Pat yourself on the back. You are now a DevOps dudess or duderino. On your way to being a Full Stack Developer. ;-) 116 | 117 | #### Where to go from here 118 | 119 | There are lots of ways to get apps to launch in the background, I like forever because it keeps the app running even if it crashes. 120 | 121 |
sudo npm install forever -g122 | 123 | -------------------------------------------------------------------------------- /docs/updating.md: -------------------------------------------------------------------------------- 1 | ## How updating works 2 | 3 | The server automatically checks for updates every fifteen minutes. This is of course, configurable. That's what this document explains. 4 | 5 | The update server is GitHub. The nodeStorage repo as the official release version. 6 | 7 | When there's a new version your server will automatically update itself, unless you've configured it not to. However it will not automatically restart. You can set it up so it does. See the section below. 8 | 9 | #### How to configure updates 10 | 11 | You can configure the updates through config.json by specifying a top-level object named updates. It has three optional elements, enabled, fnameStorageJs and ctMinutesBetwChecks. 12 | 13 | If enabled is false, it won't check for updates. 14 | 15 | If you've changed the name of storage.js, set fnameStorageJs to the name of the file (that's the file it will update). I like to change the name so if I'm running more than one instance of the storage server on a system I can tell which is which when looking at a forever list. 16 | 17 | Change ctMinutesBetwChecks if you want it to check more or less frequently. 18 | 19 | #### Automatic restart on change 20 | 21 | You can set it so that your server automatically quits when there's been a change to a file you can specify. If you're running a utility like forever, it can then relaunch the server. 22 | 23 | Turn the feature on with flWatchAppDateChange. And specify the file it should watch with fnameApp. 24 | 25 | #### Example 26 | 27 | Here's an example of a config.json that has an updates object and automatically restarts when there's a change to the main JavaScript file. 28 | 29 | -------------------------------------------------------------------------------- /docs/whitelist.md: -------------------------------------------------------------------------------- 1 | ## Setting up a whitelist 2 | 3 | If you want your 1999 server to be open for anyone to create a blog there, then you don't need to specify a whitelist. However if you want to limit who can set up a blog, you need a whitelist. 4 | 5 | #### What is a whitelist? 6 | 7 | It's an array of Twitter screen names named userWhitelist that you add to your config.json file. 8 | 9 | An example of a config.json with a userWhitelist specified. 10 | 11 | #### You can also put it in a separate file 12 | 13 | If you want more flexibility in editing your whitelist, you can put it in a separate file accessible over HTTP. Here's an example of such a file. 14 | 15 | Instead of putting the array directly in your config.json file, you would point to it using the urlUserWhitelist value. 16 | 17 | The server reads the whitelist file once a minute, so you can change the whitelist without restarting the server. config.json is only read when the server starts up. 18 | 19 | Here's an example of a config.json file that specifies a remote whitelist file. 20 | 21 | -------------------------------------------------------------------------------- /misc/about.opml: -------------------------------------------------------------------------------- 1 | 2 |