bulletin-board | Bulletin Board acts as a platform

In your DiscussionsController add this line at the use section.

Have you try in Python with with Scrapy and Selenium for example.

try to create a spyder to open de serveral links or import the from tabs, your choise,

and selectors to filter the data.

use the configurations to define the periodicity of each request/job...

You're trying to access a paid icon. You will have to use the free pencil icon:

import { FaPencilAlt } from 'react-icons/fa';

and then use it like so

You can find a list of icons you can use here: https://fontawesome.com/icons?d=gallery&q=Pencil

Anything marked as PRO will not be available.

Your app was made with create-react-app. Here are the docs for adding / referencing environment variables: https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#adding-custom-environment-variables

Create a file in the root folder called .env with the contents:

REACT_APP_XREFS_BACK_URL=put_whatever_here

Then access this variable in your JavaScript via:

process.env.REACT_APP_XREFS_BACK_URL

I'm pretty sure (but needs confirmation) that your reloadBoardContent() is updating the div where this is located.

I believe there are 2 problems both having to do with your sort. These problems come straight from the documentations but if you would comment I'll help explain (and might possibly learn something myself)

The first and biggest problem is that you must sort in the order given by the index. From docs:

You can specify a sort on all the keys of the index or on a subset; however, the sort keys must be listed in the same order as they appear in the index. For example, an index key pattern { a: 1, b: 1 } can support a sort on { a: 1, b: 1 } but not on { b: 1, a: 1 }.

This means that you must sort in the order given by your winning plan: category, _id, sticky, lastPostAt (or any prefix of that order such as category, _id, sticky or category _id). If not mongodb will identify the 772 docs which are indexed using your winning plan, but will then have to comb through each key in order to assess values and provide the desired sort order. If you want to sort by the order you are curenttly querying must provide a index in that order:

The second problem is that you must sort in the direction that you provided by the index (or the inverse direction).

For a query to use a compound index for a sort, the specified sort direction for all keys in the cursor.sort() document must match the index key pattern or match the inverse of the index key pattern. For example, an index key pattern { a: 1, b: -1 } can support a sort on { a: 1, b: -1 } and { a: -1, b: 1 } but not on { a: -1, b: -1 } or {a: 1, b: 1}.

Because your indexes are all in ascending order, you would have to either sort in ascending order for all indexes, or descending order for all indexes. If not we run into the same problem in which mongo finds all the relevant docs, but has to comb through them to provide the desired order.

I believe you would get imporved functionality by providing an additional index of:

You can create your own tab bar, hook it up to the navigator and to redux.